I had my website hosted in amplify for 2 years. I had everything working perfectly but now suddenly the certificate is expired. According to amazon it should renew automatically but it is not happening...
I have tried to reach amazon to fix the issue but they charge you to open a case about the mistakes they do so I have no idea how to fix it...
Any idea?
Deleting the domain and then adding it again solved this issue for me.
Hopefully, this will help.
In my case, I have cleaned up some of my DNS records for the domain, and apparently some of them is for AWS ACM domain verification, and the renewal failed.
What worked for me was to remove the domain in Amplify and add it again.
Related
Anyone familiar with firebase, or just wordpress tech in general, willing to help me with an error I created?
Experimented with adding firebase to one of my sites, mainly trying to get a good 301 redirect going. Didn't pan out, tried deleting everything but for a while now I get this error when trying to load my domain.
I tried reinstalling a new ssl cert in my host, but that didnt do anything. Dunno where else to look to delete or edit files.
Your connection is not private
This server could not prove that it is kylebeckerconstruction.com; its security certificate is from firebaseapp.com. This may be caused by a misconfiguration or an attacker intercepting your connection.
You should look at the DNS records for your domain, as it appears they are likely still pointing to Firebase. You can use the dig tool (Linux/macOS) for this:
dig +short mydomain.com
If the resulting records look like:
151.101.65.195
151.101.1.195
then you are still pointed at Firebase Hosting and should change your DNS records with your domain provider.
The goal is to have free ssl from cloudflare. So I moved dns records to cloudflare and is showing me - Certificate is Active. When I go to 'Analytics tab' it shows me traffic that is coming to the website. But when I enter the site https://www.zampadebattista.com I'm getting 'Your connection is not private'. It look that virtualmin is using his own self-signed certificate that I didn't setup. Do I need change something in virtualmin?
Thanks for your help
Try to see if the same key and Certificate that is in the Directory is the same as the CloudFlare.
Clean Your Cookies ...
Enter the site with the Browser in Anonimo
Here it is working perfectly!
If you have solved, clarify the solution you found ...
So I was using Google cloud buckets to host my site, I figured out SSL Is impossible doing that so I tried app engine and that just got really complicated really fast so I tried firebase and it seems the best, however I have my main site (https://example.com) and my development build of the site with an auth login for me and my devs (https://staging.example.com). I have 2 different firebase projects one for the main site and another for the subdomain, however I first connected the subdomain one and it got an SSL cert and said connected in like 2 seconds, however I did the same for my main site and it's been stuck on pending all day now. I read somewhere that it can't do a subdomain and a normal site because of some SNI thing but if you can't enable SSL on a domain and a subdomain that's a pretty bad system imo. I use Google Domains for my domain and there are A records for the normal domain and subdomain pointing to firebase.
Thanks to anyone with any clarification.
Turns out I just had to wait for the certificate to be made, I was just confused as to why one domain took seconds to make it and the subdomain took almost a day so I thought something was wrong.
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.
I wanted to get help on this issue of mine.
Openshift is using https by default on its free applications,
whereas Heroku is using http
Whenever a visitor visits my website, he is presented with an Unsecure Connection warning.
How can we get rid of this warning or https altogether once and for all.
I am fine with http alone as
I am not willing to upgrade to silver for SSL thing only.
Nor do i have an SSL cert with me, am not planning on buying one.
Any thoughts?
strange thing I am also deploying my applications on openshift and they all are on http server. What ate the cartridges you are using??
OpenShift does not use https by default, we allow both http & https for free accounts and paid accounts. it may be something in your framework that you are using that is causing the redirect to https, it could also be that you visited the app before it was completely setup, and got redirected to https://app-domain.rhcloud.com/app, and now your browser is stuck on the https redirect. Try clearing your cache, test with another browser, or check the framework you are using to make sure it's not redirecting to https.