Subj : letsyncrypt issue
To   : DIGITAL MAN
From : Dumas Walker
Date : Fri Feb 13 2026 09:14 am

> I'm not having issues. When I check your domain with this tool:
> https://www.ssllabs.com/ssltest/analyze.html?d=capitolcityonline.net
> it reports that you have a Certificate name mismatch, clicking ignore/continue
> it then reports that it's self-signed.

> If I try https://www.ssllabs.com/ssltest/analyze.html?d=capcity2.synchro.net i
> also reports a self-signed cert. So it definitely seems like the certificate
> being sent out doesn't match your letsyncrypt.cfg.

Based on my config (requoted below), do you see anything that would cause a
name mismatch or a cert that doesn't match my config?

> One thing you can do is disable self-signed cert generation by setting
> SCFG->System->Security->Create Self-signed Certificate to "No".

OK I have changed that and will see what happens.

Config file contents:

>  > Host = acme-v02.api.letsencrypt.org
>  > Directory = /directory
>  > TOSAgreed = true
>  > GroupReadableKeyFile = false

>  > [Domains]
>  > capitolcityonline.net = /sbbs/webv4/root
>  > capcity2.synchro.net = /sbbs/webv4/root
>  > classic.capitolcityonline.net =
>  > /sbbs/webv4/root/classic.capitolcityonline.net

>  > [key_id]
>  > acme-v02.api.letsencrypt.org=https://acme-v02.api.letsencrypt.org/acme
>  > /acct/108002992

>  > [State]
>  > DomainHash= (redacted)
>  > Host=acme-v02.api.letsencrypt.org


 * SLMR 2.1a * OS/2 VirusScan - "Windows found: Remove it? [Y/y]"
---
 þ Synchronet þ moe's tavern * 1-5028758938 * moetiki.ddns.net:27

.