I haven't made any changes to the code, but now my site (http://www.tagalogreader.com/) says "Welcome to Firebase Hosting".
Have I been hacked? What should I do?
This is the page you get when you create a firebase website, but have not hosted any content.
If you are using Firebase go here to host your content.
If not go to your domain provider and check your records, if you see anything with firebase in it get rid of it and update it to what it should be
It seems like you( or your client has changed the nameservers ) of you domain...
Your website is no more linked to the nameserver it used to query earlier...
If that doesn't help check out your A and CNAME records... They might be pointing to firebase servers.
And that is probably the servers default page you are seeing, so doesn't look like it's hacked :)
Related
I want to let users sign-up for a sub-domain on my app's main domain. Unfortunately Firebase Hosting doesn't support wildcard subdomains (yet?), but I think I have an almost-automated way to do this.
I'll lay out my plan, but I'd really appreciate any feedback or improvements of how else I should solve this problem.
Steps:
Gather a user's intention to create a subdomain
Automate Firebase CLI to create another site, get DNS settings and add them into a Firestore doc (that I will then show the user)
Upload a simple HTML page with <object> and their site app.website/username
Cry because <objects> doesn't change the URL in the browser
Each user has a public profile on the main domain, like this: app.website/username, but I want to also host this page at username.app.website so they can point their domain (or subdomain) to their app.
Is there a way to do this efficiently?
From the documentation on connecting to Firebase Hosting:
Each custom domain is limited to having 20 subdomains per apex domain, due to SSL certificate minting limits.
So you can't have more than 20 subdomains. As long as you stay within that limit, you approach could work. But it won't allow you to go over the limit.
I started a Google Cloud Account. Setup a Wordpress site. All was good. I changed the URL in the backend of Wordpress to match the new domain. Was not setup right. So I changed the URL back again to the IP address. However, I am locked out. Nothing works. How can I access the Wordpress account to update the URL in case I did it wrong or entered the wrong IP address?
The only way would be to access the MYSQL database and manually change it from there, that is if you have access to the database through PHPmyadmin or putty to the server directly.
your problem is not an easy fix sorry, I would recommend burning it down and restore from a backup.
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.
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!
I’m having a lot of trouble configuring my custom domain. Currently, if you go to my site www.mydomain.com it redirects to the default somecrazyname.firebase.com. In my google domains, I just have both www.mydomain.com and mydomain.com redirecting to the mycrazyname.firebase.com just for the sake of having something live until I can figure this out. My question is, how do I make it so when you go to www.mydomain.com it stays on www.mydomain.com while showing my amazing content and not somecrazyname.firebase.com.
Everything is configured correctly with firebase as far as my custom url goes(verification, etc.). However, the url firebase gave me is https mydomain.com (where if you go there it says the site can't be displayed) where my domain on Google domains is http. I've tried to configure redirects within my firebase json as well as my synthetic records in Google domains, but have had no such luck and am out of ideas. I've also looked at the firebase hosting custom domains documentation and am just not getting it.
Here are some visuals....
My redirects as seen on Google domains
I'm sure it's just a matter of putting things in the right places, but I have been trying this for a few hours and have not had any luck.
It was the synthetic records that was causing the issue for me. I was using CName records which, by the direction of the firebase support team is good only for subdomain redirects. Below is part of an email from the firebase support team. This is her answer to this as well as some helpful explanations.
Firebase uses TXT records for the verification of your custom domain.
On the other hand, CNAME and/or A records are used for redirection. Please take note of the following:
If you have a subdomain, CNAME records are recommended
Note that the host name with "*" indicates a wildcard. Any subdomains typed before your custom domain will redirect you to your
hosted custom domain.
Otherwise, if you have a custom domain without a subdomain, A records are recommended.
Note that adding both A records will increase redirection performance
Also, kindly remove other A records that are not from Firebase to prevent redirection issues
That's about it. Firebase Static Hosting only needs three records
(TXT, CNAME, A). Other than that, you wouldn't have the need to
implement domain forwarding such as your Synthetic records. Moving
forward though, I would suggest you to remove your Synthetic records
and add the A records I have provided on my previous email.
You should NOT be using a redirect (301 or 302) record for your domain. Instead, you should set a CNAME record. Here's how to fix it:
Delete the second redirect in your screenshot (the one that redirects to Firebase).
Go to the DNS tab of your Google Domains control panel, scroll down to the Custom resource records section, and add a record that looks like this:
www | CNAME | _____ | portfolio-6f15b.firebaseapp.com