Why this is showing in firebase hosting that my Go daddy domain name may be connected with another project.
I have not connected my domain name with any project.
Now when my i am trying to connect my Ho daddy domain name with the hosting of firebase. It's not getting connected.
Please somebody help me.
Related
Firebase provide 2 free domains per project, but is it possible to upload DNS records?
I want to enable Firebase Dynamic Links. Then I need to upload DNS records but I can'T find how to do it.
Anybody knows?
Firebase does not provide DNS service. You must bring your own DNS provider.
Once you have your own DNS, you can connect it to Dynamic Links using the instructions in the documentation.
If you are using Firebase Hosting, you can connect it to Firebase Hosting using the instructions provided in the documentation.
DNS services are normally provided by your domain registrar, so the company where you registered your domain. Firebase doesn't offer domain registration services, so it doesn't allow you to manage DNS records either. Check with the place where you registered your domain for how to manage the DNS for that domain too.
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 know this question has been asked numerous times here but I still don't get the solution, sorry about that.
I deployed a wordpress multi site VM on my Azure account and purchased a domain name "https://jobinwrites.com" from Azure DNS service. I followed the instructions here to map an "A record" to the IP address of this Azure VM:
And this is how the overview of the Azure VM looks like:
When I hit the IP address of the machine or the jobinwrites.westus.cloudapp.azure.com domain, I correctly hit the service. However, when I try jobinwrites.com, the browser returns a DNS address not found exception. What am I doing wrong here? Thanks in advance.
According to your description, you want to map a custom domain name to your Azure VM, we should buy this custom domain name first.
Azure DNS is not the domain registrar.
We should login your 3rd party domain register configure page.
Each registrar has their own DNS management tools to change the name server records for a domain. In the registrar's DNS management page, add a new A record, like this:
Host type value
xxxxx A 104.42.230.37
If you want to add a CNAME record, please refer to this answer.
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.
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.