Try use the dns and tla-apln, it’s all good.
Do you do backup’s of the virtual server, bit of a last resort.
Backup the that domain (virtualserver), then delete it and them restore from backup, that should reset settings I hope, unless it just restores the error.
Yeah already did it twice, the problem remains
right, instead of restore, if you just create a new virtual server with the domain name does it still happen?
Yeah, every new virtual server will have ERR_SSL_PROTOCOL_ERROR
I noticed all traffic is being forced to ssl, like I can’t view the site using port 80.
https://hencointerior.com/ it get sent to https://hencointerior.com/
Lets encrypts need to access port 80
How have you done that redirect?
Although ignore seems to be working http://hencointerior.com/.well-known
Your a pro user, you might be better raising a ticket on this one and staff can take a look.
this is all LE needs to access on port 80. and this is correct setup. anything else other than .well-known , redirect to https.
can you post the full vhost .conf? or send in private if you don’t want it public.
and also try apache2 stop + start if everything looks fine.. (not restart or reload/graceful).
(if you haven’t already tried multiple times).
I believe letsencyrt will also work over https, but I don’t know if there needs to be a valid cert first.