Using new Caddy but old Caddyfile from past success, but now my sites are not SSL secured

[EagleDTW (Daniel Witkin)]

That’s working with access (http only currently), I’m wondering if it because I didn’t have a zerossl account until now. Would that cause issues?

[matt (Matt Holt)]

I have to admit I haven’t read all 21 posts in this thread. What is the exact problem now? Is it this?

@EagleDTW

I moved the pi-hole to 1080, just to be sure. I had a more tech savvy friend curl the site and it says curl: (35) error:1400410B: SSL routines:CONNECT_CR_SRVR_HELLO:wrong version number

He’s saying it is issuing a TLS cert that is version 1.1 instead of 1.2 or higher.

If that’s the case, then it sounds like curl isn’t even trying to connect to Caddy. You can enable debug logs and if it is reaching Caddy, then you’ll see an error. If not, then something isn’t configured right with your network or DNS.

[EagleDTW (Daniel Witkin)]

Hi Matt,

The issue appears to be that TLS version in use is 1.1 and Caddy is not able to forward the http to https:

Above is the error 35 no tls 1.2 or 1.3.

Thank you,
Daniel

[matt (Matt Holt)]

Before we continue troubleshooting, we’ll need evidence (from your Caddy logs) that the connection attempt you’re screenshotting is in fact with Caddy and not something else.

[EagleDTW (Daniel Witkin)]

Hi Matt,

This is Caddy 2 Home assistant addon. Using caddy v2.4.3 and a separate Caddyfile, logs below:

[EagleDTW (Daniel Witkin)]

Example cert file:

[EagleDTW (Daniel Witkin)]

Port config issue!! Fixed it! External port XXXX to Internal port XXXX, I had internal port of YYYY instead. My bad, it had been awhile since I had the port forwarding all entered and configured from the past setup I had done. Thank you Matt and Francis!