One of my web apps was working just fine for months and suddenly today I am getting a not secured error/warning message. See screenshots
Looks like the SSL certificate expired….
Did anyone experience this issue before?
How do I get a new certificate? This has got nothing to do with the code itself and the Agent could not really do much because this is more a Replit hosting issue.
Any ideas?
Also, I’m wondering if Replit automatically renews SSL certificates for hosted web apps.
A different app’s certificate is set to expire soon, which is pretty concerning….
Will a new one be issued automatically, or do I need to take action?
So is quotes.notesabout.life pointing to a Replit site? If so then 2 choices:
Why Replit have forgotten to renew it is anybody’s guess. But I hope it is a one off bug, and we don’t all have to go through this everytime our domain SSLs expire.
Why did I write all of the above before checking if the domain was now ok. It is ok 
So seems they may have resolved it!!
Steve is right, delete deployment, re-deploy, reattach domain, re-add DNS records and you should be good to go.
yeah but I hope @kody-replit sees this.
Not great user experience…..so I have to do this every 3 months hoping it works?
This is like re-opening a new bank account with your current bank just because your access to your own account expires every 3 month 
I’ve never had it happen before, and have 20+ apps deployed, many for over a year. I don’t believe it to be systemic.
This just has happened with one of my apps and custom domains. I’m currently waiting to hear back from support and reluctant to delete the custom domain to re-add it, but that may be better than waiting for support. I’ve been waiting for 24 hours now, and it’s been crickets.
Delete and re-add, as it only takes about an hour round trip for you to be back up and running.
Thanks. It took about 15 mins. Hoping this won’t keep happening. You said “20+ apps deployed, many for over a year”. Anything else I should know about this level of investment in the hosting UX?
Not really, it’s been solid for me. No deployment issues that weren’t self inflicted
Same thing happened to me. Had to delete my domain connection and reconnect right away. This whole process took around 10 min to make the domain back.
