Getting ssl for for domain in caddy .

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. |, so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:

It produced this output:

My web server is (include version):caddy

The operating system my web server runs on is (include version): ubuntu 22

My hosting provider, if applicable, is:digital ocean

I can login to a root shell on my machine (yes or no, or I don't know): yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

so i want to automatic https to https i am using caddy server from hatchbox they provide auto ssl on 1 domain but not subdomain

Hello @barber007, welcome to the Let's Encrypt community. :slightly_smiling_face:

Using this online tool here is a list of issued certificates |, the latest being 2023-01-03 from C=AT, O=ZeroSSL, CN=ZeroSSL ECC Domain Secure Site CA
and the one before that was on 2022-12-30 from Let's Encrypt.

Using this online tool SSL Server Test (Powered by Qualys SSL Labs) has these results SSL Server Test: (Powered by Qualys SSL Labs)

Using this online tool show an issue with http results are here Hardenize Report:

1 Like

There's something wrong with your web server:

curl -Ii
curl: (35) error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error

curl -Ii
HTTP/2 200

curl -Iik
HTTP/2 200

Even the IP address "works".
But the base domain fails hard.


I see that has been corrected:

curl -Ii
HTTP/2 200

Although it still doesn't redirect to "www".


I am seeing an A for both, they each have their own certificate.


I think this is what caddy does if you request a domain that doesn't have a certificate issues.


It looks like and both redirect to https, and both have valid certificates. Is your problem resolved now?


But the desire was:

[for all to end-up @ https://www...]


Should just be: {
} {

What is your Caddy config?


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