I'm setting up a website hosted on Firebase. Currently, I'm using the Mautic for email automation which is currently going to Spam. My technical resource told me it was because I needed to set up rDNS records.
Does anyone know if Firebase supports this? I couldn't find any answers on here or Google.
Firebase Hosting doesn't do any DNS hosting at all. You'll need to use some other DNS provider, which can often be the registrar of your domain.
Related
I am looking to host multiple sites using firebase but have read something that could cause problems.
Each custom domain is limited to having 20 subdomains per apex domain, due to SSL certificate minting limits.
https://cloud.google.com/storage/docs/hosting-static-website
I was hoping to use subdomains, e.g. a.example.com, b.example.com ...etc.
This limit of 20 domains seems quite restrictive and I have some questions
If I create separate projects for each subdomain does this limit still apply? e.g. have 1 firebase project with a hosting site for a.example.com and have a entirely separate firebase project for hosting b.example.com.
I have also read you can hosting using cloud storage and a load balancer. https://cloud.google.com/storage/docs/hosting-static-website. Does this provide an automatic certificate or is it manual?
Does the limit of 20 subdomains apply only to firebase hosting or does it also apply to hosting via cloud storage and a load balancer?
Thanks
This limit is per project, so if you put different domains on different projects they are not affected by it.
The documentation seems to describe the process pretty well: https://cloud.google.com/storage/docs/hosting-static-website#lb-ssl
This limit applies to Firebase Hosting only. Other products may have their own limits of course, but those would be listed in the documentation for that product.
I know many ppl asked this question before. But they are answer years ago. Now it's 2020. Not sure if Firebase supports subdomain for each client now. Can anyone can give an update?
Link to the old question:
Firebase - Subdomain for each client
Wildcard domains (e.g. *.mydomain.com) are not yet supported by Firebase Hosting, and due to limitations of our Certificate Authority (Let's Encrypt), there are relatively low limits on the number of subdomains of a given domain that can have certificates minted in a given time period.
For now, the answer remains that this is not a use case that is supported well on Firebase Hosting, and we don't recommend using Firebase Hosting for massively multi-tenant custom domains at this time.
Sorry for my english...
I'm using firebase authentication for first the first time.
I discovered that I cannot create/connect to accounts if my network automatically selects dns and does not use google dns(8.8.8)
I do not understand how my application will work (just I think that not everyone uses this DNS).
Is there any way to fix this so it works for everyone?or is it work correctly?
without google dns
with google dns
Please check any that applies to you,
Is your ISP is blocking DNS queries to Google Authentication servers,
Are you using a proxy, if yes try disabling it, and then try again,
Check the error returned in auth callback when you are requesting authentication,
Check stack trace in LogCat of Android Studio.
I am trying to host my website on firebase through a domain I purchase through 1and1. 1and1 only gives me an option to have one A record though I need two to verify through firebase.
It is the same issue as Firebase hosting with only ONE A record , but I am not able to use this solution.
Unfortunately both A records are needed to verify with Firebase Hosting. One possibility, if it's not an apex domain (e.g. this will work for www.mydomain.com but not mydomain.com), is to use a CNAME pointed to <yourapp>.firebaseapp.com.
If it's an apex domain, you'll need to switch to a DNS provider that supports multiple A records.
I'm trying to setup a very simple Azure deployment that consists of a few Web Apps and an API Management Gateway through which all traffic is directed. The problem I currently have is that I am unsure as to the best way of blocking traffic from going direct to the Web Apps and bypassing the gateway. Is there a 'best practice' mechanism for ensuring only traffic from the Gateway is allowed through?
I've seen suggestions for IP range blocking and 'secret key' implementations, however I wonder whether there is a better way?
Thanks
There are a few options:
1. IP whitelisting
2. Secret key
3. Basic auth
4. Mutual cert auth
IMO #4 is the best way. You can find out more information on how to enable the feature in API Management and Web Apps here:
https://azure.microsoft.com/en-us/blog/enabling-client-certificate-authentication-for-an-azure-web-app/
https://azure.microsoft.com/en-us/documentation/articles/api-management-howto-mutual-certificates/
I should I would add my own answer as I found that the new portal now has an 'API App' which allows access to API though internal only, e.g. through the gateway.
This seems to meet what I was trying to do exactly!
https://azure.microsoft.com/en-gb/documentation/articles/app-service-api-apps-why-best-platform/