Firebase hosting: Needs Setup

2019-02-04 13:16发布

I am trying to set custom domain for my firebase app

Firebase hosted url : https://inventory-app-726af.firebaseapp.com/ Custom Domain: inv.agsft.com

I have followed all instructions as part of setting custom domain but after verification step when I click on finish button, status will always be "Needs Setup".

I am managing DNS through cloudflare (https://www.cloudflare.com/) and I am following Quick setup option.

Any pointers to resolve it?

Many Thanks Pari

8条回答
女痞
2楼-- · 2019-02-04 13:53

I had the same issue. Here's how I fixed it:

1) Cick the View button on the problematic domain (in the Hosting section next to where it says Needs Setup).

2) Change the 'Setup mode' from Quick Setup to Advanced and follow the 3 steps

  • 2a) Open your domain provider's settings (I'm using Google Domains) and add the TXT record it's giving you.
  • 2b) Wait about 4-12 hours for verification
  • 2c) Add the provided A records into your domain provider's settings

This is not a quick process, but it should be working about 5 minutes after you complete step 2c.

查看更多
【Aperson】
3楼-- · 2019-02-04 13:56

When I change my setting like below, it started to work again. Redirect loop fixed:

enter image description here

查看更多
家丑人穷心不美
4楼-- · 2019-02-04 13:58

In my case I did the same that Brennen did:

  • toggling the DNS Status on cloudflare from DNS and HTTP Proxy (CDN) to just DNS on the two A records.

But just start working when I:

  • Delete the domain from firebase. (click on the : points select delete domain)
  • refresh the firebase site
  • Added again in Quick Setup. I already had the A record added in Cloudflare so I didn't added again.

After that automatically the status added was connected.

Remember: Before testing, clean you browser cache.

查看更多
神经病院院长
5楼-- · 2019-02-04 14:01

I had the same problem, I was able to resolve it by toggling the DNS Status on cloudflare from DNS and HTTP Proxy (CDN) to just DNS on the two A records

enter image description here

It started working right away. Hope that helps!

查看更多
对你真心纯属浪费
6楼-- · 2019-02-04 14:02

When I run dig -t txt +noall +answer inv.agsft.com there are no TXT records showing. Since those are required to verify your ownership of the domain, Firebase Hosting will not continue the setup beyond step one.

Update: since the next step requires you to map A records to the IP addresses of Firebase hosting, I ran the relevant dig too:

$ dig -t a +noall +answer inv.agsft.com
inv.agsft.com.      299 IN  A   104.18.56.240
inv.agsft.com.      299 IN  A   104.18.57.240

Those are not the addresses I'd expect for Firebase Hosting, so it looks like either you haven't correctly entered the A records, or they have't propagated yet.

查看更多
smile是对你的礼貌
7楼-- · 2019-02-04 14:03

The proper solution, ie without disabling Cloudflare for the site, is to use Full SSL for your domain/subdomain.

You can either choose Full SSL for all your domain entries, or set up a Page Rule for a specific subdomain, in your case, use "inv.agsft.com/*"

Source: https://community.cloudflare.com/t/flexible-ssl-redirect-loop-with-google-firebase/2063/3, which in turn points to https://support.cloudflare.com/hc/en-us/articles/115000219871-Why-does-Flexible-SSL-cause-a-redirect-loop-

Had the same issue and this solved the redirect issue. Firebase will however still report the domain as "Needs setup", for that I have no solution, but it does not affect the functionality of the hosting.

查看更多
登录 后发表回答