Below is the scenarios I have done and facing difficulties in proceeding further.
Firebase deployed - deployed to firebaseapp.com
Created custom domain in firebase,named subdomain.mydomain.com
copied the TXT from the advanced Setting
I have domain in google. named domain.com
In domains.google.com under Custom resource records pasted the TXT text and wrote sub-domain at the place of #.
Below are my doubts
How to make firebase deploy to subdomain.mydomain.com, now
it is deploying to firebase.app.com
What else should I do to make subdomain.mydomain.com to live and show my page
Note: I just brought the domain, only basic setting like enabling security has been done.
Update the question with screenshots
1.Firebase
2.GoogleDomains verification
Thanks Mr. #FrankVanPuffelen,
I spoke with the domains.google.com support team and understood the mistake I have done.
Follow below to avoid mistakes
WARNING: Don't disturb by making any change in setting. wait for atleast 12hours(works max at 6 hours)
If it is not working don't hesitate, contact the support team and talk with them
contact me for any help if you still have an issue 😃
Related
I have decided to switch my customer base over to email link sign in with Firebase rather than Google/Email/Apple that I was previously doing.
I got everything set up, tested, and all was working well. Since I have now released customer wide I am starting to run into issues.
Some customers, including gmail users are getting a Suspicious email alert due to having a firebaseapp.com link in it. Today, I created a brand new project for a customer and went to log in for the first time, Gmail as all good, but now Chrome is giving me a "Deceptive site ahead" error page saying this website does phishing (the subdomain is about 6 hours old).
Can anyone think of an appropriate solution for this, or will I have to do some URL rewriting?
It is frustrating the firebase URLs are so blacklisted across the internet(I have had to omit storage url links for pictures and make custom emails altogether since the domain is banned by Exchange), I would think this should be much easier than it is being made out to be.
When I first ran into the Gmail issue the only thing Firebase support gave me as a solution is to build my own custom email handler. In following that, I assume I would either need to rewrite the domain after generating the sign in link, which I am a bit hesitant to do in case there are domain changes in the future or I wondered if updating my email template domain will solve the problem. When I started this process I realized I needed to update my DNS records for this. The problem here is that I whitelabel apps and have 150 projects or so and each customer gets their own project. The management of this is really not feasible.
I have dynamic links enabled for all projects and use the projectid.page.link domain for them if there is some way I can get that to work as well.
I have a firebase project that serves live users through a custom domain. I need to move the custom domain to the new version of application that is running in a different firebase project. If I delete the custom domain and add it in another firebase project, how much time will it take to reflect the change? How do I minimize the downtime?
Checked with Firebase support. This can be done without downtime. Here are their instructions:
To delete your custom domain from the project, follow these steps:
Go to the Firebase Hosting console for your project, you will see
your domain.
Hover over your domain.
There's an overflow menu (three vertical dots) on the right. From the overflow menu, select "Delete Domain"
When you delete a domain, we don't immediately remove the domain from
our backend. This is because most of the time developers are moving
their domains from one project to another, and this feature allows us
to re-provisioned the SSL certificate quicker.
I was able to delete and add the domain to another project without any downtime. Thanks to the firebase team for being so thoughtful.
If it is just about moving the custom domain (no user sessions), and making a couple of other assumptions, like: the account used to verify the custom domain belongs to both Firebase projects, and that same account will move the domain, the change should be almost immediate, close to zero downtime. You should give it a try with a test domain, it's pretty straightforward.
If the goal is to have zero downtime, better ask Firebase Support to see if it's doable and how to do it.
I'm relatively new to Firebase Hosting. I have a web app that I'm working on and I have 2 Firebase Projects setup: 1 for my Production environment and 1for my Staging environments.
Ideally, I would want my Staging environment to NOT be indexed by Google.
Does anybody know if Google crawls Firebase hosted sites by default? If so, is the best way to prevent that to add a robots.txt that disallows all?
Any information would be much appreciated.
I don't think Google treats a web app hosted on firebase any differently than a web app hosted anywhere else; Google automatically indexes everything it can find. Officially, Google finds websites by looking for links and sitemaps. So, if your staging environnement is not linked to anywhere and you don't submit a sitemap directly to Google, in theory you shouldn't get indexed.
But, I wouldn't just count on the fact that you're not putting links out there. Links might find themselves online for some reason at some point in the future.
You could add a robots.txt to your staging site with this value:
User-agent: *
Disallow: /
But in my experience, an even better solution is to make your staging site unaccessible without a username/password. That way, Google's bot won't be able to index anything else than a login form. And if people do find your staging URL, they won't be able to see what's going on there.
Most people actually try hard to be indexed very high and it's not that simple. Since your goal is to NOT rank high, should be very easy. It's like trying to not win a game.
I'm doing marketing for a client.
I'm helping them move their WordPress site from one host to another (from ventraip to siteground). Their domain is also currently with ventraip. I've already set up hosting with siteground (haven't cancelled ventraip just yet).
The question being, is there a way to make adjustments and preview the website on siteground before pointing the nameservers/changing DNS? I've seen a few tutorials but they are for other hosting companies and there is nothing I can see in siteground's knowledge base.
If anyone knows a general format or a better way, would love to hear your input. Thanks!
I think a nice solution would be to modify your local hosts file in order to preview your website using the current URL (which only on your machine will point to the new hsoting).
You can follow this guide by Kinsta, which works for every hosting: https://kinsta.com/knowledgebase/edit-hosts-file/
This is what I do and I am pretty sure it works :)
Here is also a tutorial specific to SiteGround which uses a temporary url: https://iamnickdavis.com/temporary-url-siteground-migration/ but I never tested it.
Hope it helps, cheers!
I am in the process of creating a staging site for my woocommerce shop.
Wanting to protect access to it, I put it behind an HTTP Authorisation.
However, this means that PayPal IPN will not work.
This site is only for my testing usage. I do not want people creating accounts on it.
However, as it is supposed to be using exactly the same code base as production I cannot envisage disabling the signup code.
This is my dilemma.
What can be done to protect this site from unwanted access, still leaving it as a correct copy of production code ?
What I would do is to create a new site under another domain name or subdomain without making the DNS pointers. You would then need to set the pointer in you local hosts file. The site would then work like normal for you but without the entry in the host file you would not be able to access the website(at least not in a normal way without manipulating the requests). As you probably guessed, this is not super safe if you really don't want anyone else to access the staging site, but usually that is not a big deal. No one will end up there by misstake.
Secondly I would create a script sync the production environment to the staging environment. This can be done quite easily using WP-CLI (wp db export db-dump.sql + wp db import db-dump.sql + wp search-replace domain.com stage.domain.com).
I have the impression that there is no ideal solution to this question.
This is my solution - others may have better or alternative answers though.
I created a special sub-domain under a different domain.
I then installed all necessary code and setup the site as if it were a production site. Then I created my test accounts and disactivated all account sign-up links.
I have been able to setup paypal sandbox as well.
This gives me a staging site using the same code base as production where in I can test all changes and updates before applying them to production, without having the risk of using existing client data.
This meets my needs. I hope it may be useful for others.