I have my client's domain registered via 1and1.com
To connect the domain to the Firebase hosting, Firebase asks me to add TWO A records with 2 IPs. In 1and1 we can only add ONE A record. Yesterday Firebase sent me this message by mail
Please re-verify ownership of www.*******.com on
*******-website. The previous verification for this domain has
been invalidated. You have 1 day to re-verify ownership of
www.*******.com before it is removed from Firebase Hosting,
which will stop all content from being served from the domain. Please
visit the Firebase Hosting Panel to start the re-verification process.
Today the website was disconnected.
I reconnected the domain to the Firebase hosting through the Firebase control panel and got the website up again. But the Firebase control panel says it still needs setup
I am sure it will disconnect it again soon. How to solve that? (I already called 1and1 and they told me no way I would be able to add another A record.)
I set up in the same way a website (https://lasi17.snola.es/) and it seems to work with only one A record pointing out to the Firebase IP.
In my case, I just changed the option in Hosting -> Domains -> Your custom domain (in my case lasi17.snola.es) -> Process traffic in this domain ("Edit" under the kebab menu). After that, the domain works as usual with only one A record configured.
Related
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.
I am building a website that has both an app and a control panel. I want the app to live at someurl.com and the control panel to be at controlpanel.someurl.com.
I have the someurl.com app setup, however the sub domain has confused me. From what I gather, the subdomain needs to be setup using the host of “controlpanel” and that it should point at a URL (e.g 115.110.145). My question is, what url should the subdomain point at, as firebase only gives me one URL.
All domains that are connected to Firebase Hosting utilize the same anycast IP addresses -- the Firebase Hosting serving infrastructure looks at the hostname of incoming requests to match to verified domains.
I'd recommend just following the steps in the docs and would reach out to Firebase support if you get stuck in a specific place.
In setting up our own subdomain to handle Firebase Dynamic Links using these docs, the wizard says to put the A records at example.com in our DNS. I'm getting pushback from our network administrators who are wary of creating an A record at the root of our domain, which is a large e-commerce web site.
A couple of concerns/questions about this:
The IP addresses required (151.101.1.195 and 151.101.65.195) point to non-Google servers (looks like Fastly), which is a bit alarming - it seems strange that Google would outsource their deep link hosting.
We don't want all of our e-commerce traffic (coming through example.com) to be subject to these A records. Is it possible to put the A records at link.example.com instead?
The Firebase documentation on using a custom domain for dynamic links has this note:
To use a custom domain for Dynamic Links, the domain must point to Firebase Hosting. If you have a domain you want to use with Dynamic Links and the domain points to a different host, you can either move to Firebase Hosting or create a subdomain hosted by Firebase, which you can use for Dynamic Links.
So you can indeed use a subdomain for the dynamic links. In that case, just set up the subdomain in Firebase hosting. You'll need the same TXT record as normal, to prove that you have access to the domain, but then just map the subdomain (e.g. links) for the A record.
Here is the answer I received from Firebase support about these my two concerns/questions:
Regarding Fastly, Firebase uses this subprocessor to deliver content and managed services on Firebase Hosting. For more details you could check the list of Subprocessors used by Firebase on this doc.
It's possible to use a subdomain as your Firebase project's FDL domain. You'd need to create a subdomain (link.example.com) on your domain's DNS provider and connect it to Firebase Hosting. You could check out this guide for more details.
Suppose my domain is mydomain.com, and subdomain subdomain.mydomain.com. I got it from Godaddy.
What I want
I want to run different websites on each.
mydomain.com -> Website 1
subdomain.mydomain.com -> Website 2
How I setup so far
Website 1 is hosted on Firebase project 1 and accessible via default URL firebase-projectid.firebaseapp.com.
Website 2 is hosted on Firebase project 2 and accessible via default URL.
Both Firebase projects are on same Google account.
What I have done successfully so far
I started with mydomain.com -> Website 1
Verified domain by adding TXT record provided by Firebase project 1.
Added couple of A records to point domain to Firebase project 1 hosting.
So far so good, and mydomain.com is working fine.
What is not working
Now I want to host subdomain.mydomain.com -> Website 2 with Firebase project 2.
I started with custom subdomain, added subdomain.mydomain.com. Firebase had already verified domain and directly provided me ip address for A records. I added both A records on my domain registrar.
As far as I understand, these are only steps needed. But subdomain.mydomain.com is not working and Firebase still shows status of subdomain as Needs Setup.
Observations
Two things I observed seems strange to me.
IP address provided by Firebase for both projects mydomain.com and subdomain.mydomain.com are same. Not sure if this is normal or not.
subdomain.mydomain.com with A records, is not propagating when checked on https://dnschecker.org/. However, if subdomain is added via Godaddy Forwarding option, then it start propagating in few minutes.
Questions
BTW, is it really possible to host domain and its subdomain on Firebase running different websites?
If yes, then is there any other step which I am missing?
Any idea why subdomain.mydomain.com is not propagating. I checked just after 10 mins. May be I need to wait longer?
Anything wrong I am doing to setup subdomain.
I tried exploring other threads but couldn't understand what I am doing wrong. Any help will be appreciated.
After scratching my head for few more hours I found issue at Godaddy side. While adding subdomain A record, I was providing host as subdomain.mydomain.com, which was wrong.
Instead of subdomain.mydomain.com host should have been subdomain only. After updating host it started propagating in few seconds, and status on Firebase is Pending. After a minute, subdomain.mydomain.com is working fine.
So firebase seems cool! i would love to build my angular webapp and use firebase to host it. Pushing it to firebase with my terminal seems like a dream.
I bought my custom domain on Siteground.com
When starting out with firebase it asked me to change the DNS records on siteground to direct my custom domain to firebase.
Which i did and seems to be working correctly.
My question now is, do i still need my siteground.com hosting? Maybe a newb qeustion.
But i am seriously confused now.
Cause when i want to buy a domain mostly it comes together with a hosting plan like on siteground. I dont see an option on firebase to get custom domains with firebase hosting, thats why i am wondering how this all works together.
Thanks in advance,
There are typically two services that, together, make up "web hosting".
The first is a DNS Provider. Your DNS provider is what tells computers that try to load yourdomain.com that it needs to talk to a server at IP address X.X.X.X.
The second is a Web Host (e.g. Firebase Hosting). This is what actually serves up the content for your website from an IP address.
You'll need both for your domain to work correctly, but many providers offer both services together. Firebase Hosting is a web host, but it is not a DNS provider. Typically your domain registrar is also your DNS provider and provides DNS configuration for free when you purchase a domain.
Hope that helps!