Codeanywhere Automatic SSL not working?

Hi all - I’m using Let’s Encrypt through CodeAnywhere, and contacted them multiple times to no reply.

My domain is: 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.

My CNAME Record is on a host of www, and the value is as the documentation says. The URL Redirect Record is @ and unmasked.

If there’s any question to the instructions I used:

Would appreciate any help here!

Hi @komiomi

checking your domain there is a new certificate ( ):
expires in 87 days - 1 entry

And you use it - your www - version is secure.

Domainname Http-Status redirect Sec. G 302 0.357 D 200 0.493 H -14 10.030 T
Timeout - The operation has timed out 200 1.960 B

Only problem: The certificate doesn't have the non-www domain name, so your non www isn't secure.

But I don't know what that client is doing. So I don't know if it is possible (using this client) to create a certificate with both domain names.

Perhaps use another Letsencrypt client.

Thanks @JuergenAuer - I made some progress.

At this point is functioning correctly.

But, all of these fail (probably due to incorrect DNS configuration)

I don’t have root access on CodeAnywhere, is there a way to get them all to point to ?

I have no idea how that codeanywhere works. And why you need a CNAME with your www domain:

Host T IP-Address is auth. ∑ Queries ∑ Timeout A Phoenix/Arizona/United States (US) - Namecheap No Hostname found yes 1 0
AAAA yes C yes 1 0
A San Francisco/California/United States (US) - DigitalOcean, LLC Hostname: 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.

Hi @komiomi rewrites to - This is good. rewrites to - This is also good.

Before you attempt to configure redirects to “www”, needs to show a CNAME as @JuergenAuer points out .

After you accomplish this, you could take the next step and configure a redirect to your preferred host (www).

Hope this helps.

I applied a similar concept here and got all domains working:

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.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.