I purchased a domain from domain.com and am trying to connect my firebase project to it. I have copy pasted the TXT record as instructed by Firebase, but it still cannot verify my ownersip of the domain. This is a copy of all of the DNS records on domain.com
This is the error given by firebase
I don't recall where the A address came from. Any ideas on how to confirm the verification?
Related
Here is what I completed
my website is deployed to firebase with URL https://lizart-io.web.app/
I purchased a custom domain https://lizart.io on domain.com
followed the steps from firebase documentation to set it up, these instructions were provided here: https://firebase.google.com/docs/hosting/custom-domain
verified ownership of the domain by adding two TXT records to Domain.com
Now the Error/Issue I encountered: Firebase says that my custom domain Needs Setup.
Firebase Dashboard Status
Firebase Dashboard
Domain.com DNS settings
How do I complete the last setup? Where did I miss a step?
Thank you very much in advance all!
I had completed setup firebase hosting custom domain after verifying TXT records and A records with IP addresses. and today I tried to add another domain to redirect www.mysite.com to mysite.com. in the process I deleted previous A records and re-added new records and firebase hosting stopped working soon after. I'm very new to firebase and I have no idea what happened. My domain is purchased from namecheap.com. I also re-added A records hoping it will fix the issue but it didn't.
it says mysite.com is connected but when I try to access it I get following error.
It started working again automatically a few minutes after resetting A records. But firebase support told me that there should only be A records with IP address in DNS configurations.
My current project setup for a react - firebase web app is as follows.
Domain bought from godaddy
Cloudflare DNS
React web app deployed on google compute vm
Firebase for DB , Auth and functions.
I have the following entry on cloudflare DNS
A record sub.mydomain.com pointing to google cloud vm ip.
A record mydomain.com pointing to another vm ip hosting public site on google cloud compute vm.
When i use google login, the sign in page shows the myapp.firebase.com which i supposed is because my firebase configuration has authDomain=myapp.firebase.com
If i want authDomain to be my custom domain firebase asks to add another A record for mydomain.com pointing to a firebase ip.
I cannot have duplicate records pointing to different ip. Is the DNS entry required to change the authDomain or just the TXT entry (from step 2 of custom domain on firebase) is sufficient.
I do not intend to use firebase hosting.
I am able to complete the connect to custom domain step successfully and https://example.com is correctly loading my static file app which is hosted on Firebase.
However, browser is warning about the site's SSL certificate is not matching example.com. I looked at the certificate and it is of firebase.com, not example.com.
This certificate is provided by Firebase for example.com (my custom domain name) and I expect it to be matching it. Is this expected?
I know the other solution is to get my own certificate for example.com. However, it seems that Firebase won't let me deploy my own cert.
Update
I retried it some time back and it is fixed. And the whole suite of Firebase db/functions and corresponding sdk/cli are working really well. Great for small dev team.
Solution: Don't have to do anything about it other than just wait.
Faced the same problem when connecting to my custom domain on Firebase Hosting. However, it will only be insecure when the status is pending. The status can be found on your Firebase Hosting Dashboard.
My connection turned secured with a green lock after around 3 hours, and the status reflected in the dashboard changed to connected.
This error message called domain name mismatch warning that occurs because of the domain is pointed to a shared IP addresses.
You need to confirm that your hosting provider supports SNI technology which allows install different certificates on the same IP. Please ensure that the certificate is installed correctly on your desired server and enable SNI. If your hosting provider doesn’t support SNI technology, you should have to dedicated IP to host your SSL.
In the add custom domain menu, check by changing the setup mode to advanced and complete the provide token on existing domain task by copying the TXT value to your dns records according to the instruction.
This solved my problem.
Custom domain is currently setup with A record pointing to the IP of the firebase AND wildcard CNAME record pointing to the same app.
dig +short mydomain.com
151.101.65.75
151.101.1.75
dig +short abc.mydomain.com
myapp.firebaseapp.com.
app-cert.firebaseapp.com.
151.101.65.75
151.101.1.75
The problem is that "abc.mydomain.com" is redirecting to "mydomain.com" with a 301 response.
Is the problem in how the domain is setup or on the firebase end?
EDIT reply from the firebase support is:
"Unfortunately, since you've already connected your domain mydomain.com your firebase app, all redirects will go through that URL. and not to your firebase app.
"
This reply is so confusing and makes no sense IMO.
Update 2020-03-30
For several years now it's actually been entirely possible to have a subdomain pointing to a different Firebase Hosting site than the apex domain. This answer has been out of date. Happy Hosting!
Firebase Hosting presently only allows one canonical domain for your project -- if you specified mydomain.com and then point abc.mydomain.com to Firebase Hosting, it will redirect, as you saw.
We're considering some improvements in this area for the future, but at present all non-canonical domains will redirect.