CODEWITHSUNDEEP
firebasednshostingfirebase-hostingnamecheap
blue
blue

Reputation: 7385

DNS - Firebase connect to Namecheap still says Needs setup?

Ok, it has been less than 24 hrs but more than 10, and I find it odd that I am still getting a status of Needs setup in Firebase just trying to redirect to a custom domain, bought with Namecheap. I don't know what Im doing wrong but I still get the "insecure connection" error trying to access my site.

Here are the records specified in Firebase to be added to my Namecheap records:

enter image description here

Namecheap is in accordance:

enter image description here

I used @ for the same host as specified by Namecheap - is something wrong? How long should this take if not?

Upvotes: 41

Views: 26081

Answers (7)

BrysonW
BrysonW

Reputation: 11

In Namecheap, replace the host value provided by Firebase in the instructions/examples with @ when entering it into Namecheap

Upvotes: 0

DSquires
DSquires

Reputation: 51

2024 Update

I've configured a lot of site DNS over the years, and this one was the most annoying ever. I think I tried every published answer on the internet to solve it - waited some period of time - no love. Finally, I deleted the custom domain config in firebase, re-added it... it spun for a long time - and then came back with green checks right away. :|

Also - you'll see lots of answers which include extra DNS entries that Firebase used to give and no longer do, don't be confused by that. As of 2024 - it suggested 1 single A Record and one single TXT record.

So - full process that ended up working for me:

  1. Go into Namecheap advanced DNS and delete everything... even the TXT record hidden down at the bottom of the page.

  2. Add these settings (replacing with your own values) - and if they don't work after 24 hours... maybe delete your stupid custom domain in firebase and re-add it (without changing namecheap config!):

DNS Settings Example

Upvotes: 5

Kim Skogsmo
Kim Skogsmo

Reputation: 479

My issue was that I simply accidentally put "*" instead of "@" as the host. Otherwise, my DNS settings look just like Fakeer's, also on namecheap. Worked like a charm.

Upvotes: 0

Fakeer
Fakeer

Reputation: 1044

First delete all existing default records. Then you only need 5 records. No CNAME records are required.

DNS records for Firebase custom domains

Subdomains are just as simple. Just replace www with whatever you want (e.g. admin). DNS records for Firebase custom subdomain

Add the custom subdomain under Firebase hosting and the SSL certificate will be automatically provisioned if you wait about 5-10mins.

PS : Take a moment to appreciate that - with Firebase you will never have to to buy, sign and install SSL certs again. Even multi-domain, wildcard SSL certs are automatically taken care of.

Upvotes: 13

Davis
Davis

Reputation: 3017

Yes, as stated on firebase docs

https://firebase.google.com/docs/hosting/custom-domain#dns-records-namecheap

enter image description here

Upvotes: 3

madeyejm
madeyejm

Reputation: 502

Expanding on Devin's answer which helped immensely... Here are the steps that worked for me.

  1. Go to the Firebase console and click 'connect domain', and add your domain
  2. Remove all DNS records in Namecheap
  3. Add the TXT record that Google/Firebase suggests
  4. Go back to the Firebase console and click 'connect domain'
  5. Verify the domain ownership
  6. Add in the A records that Google/Firebase suggests
  7. Add a CNAME record pointing to the default Firebase URL, and any A records that Google/Firebase suggests for a site redirect, if you have one.

Upvotes: 21

Devin Riegle
Devin Riegle

Reputation: 593

You need to change the CNAME record to your firebase app URL:
example-app.firebaseapp.com. (Make sure to include the dot at the end) and you should also change the TTL on both A records to Automatic.

Then, delete the URL Redirect record. That should fix your problem. I'd wait up to an hour after these changes for the changes to take effect.

This is what my namecheap DNS setup looks like
I added the www A records because I have a redirect in my Firebase console, but you don't need those.

Upvotes: 57

Related Questions