Hi all - I’m using Let’s Encrypt through CodeAnywhere, and contacted them multiple times to no reply.
My domain is: www.komikomi.style and I’m using their custom domain setup. I have it set to my container and internal port, and the external port set to 443. However, it just never finds the domain on 443. It works perfectly fine on 80, but when I try to use the Let’s Encrypt port for my free SSL certificate, it fails everytime.
I’m running a container that isn’t always on, just a starter, but it’s an MEN setup on Ubuntu. I can login to root if I need to do anything on my own server.
162.243.142.234 San Francisco/California/United States (US) - DigitalOcean, LLC Hostname: sfo5.codeanyproxy.com
yes
The normal and typical setup:
Non-www and www have the same ip address, same webspace, same vHost. Then it's easy to create a certificate with both domain names and use that with this vHost.
So if you use that client -> you may have some limitations.
With the http’s being unsecure and the https’s being secure.
However, I’m surprised to hear (maybe at one point in testing?) those were both going to https. Is there any possibility of browser cache or Https Everywhere doing that automatically? I’ve been trying to figure out how to make it auto-redirect to https, but I think there is a structural limitation here.