Subj : letsyncrypt issue
To   : Dumas Walker
From : Digital Man
Date : Fri Feb 13 2026 02:40 pm

  Re: letsyncrypt issue
  By: Dumas Walker to DIGITAL MAN on 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?

No, but I'd rerun letsyncrypt.js with some of the command-line options I pointed out (using jsexec) and see what it says.
-- 
                                            digital man (rob)

Synchronet "Real Fact" #97:
Synchronet v3.13a was released in September of 2005 (9 months after v3.12a)
Norco, CA WX: 67.3øF, 52.0% humidity, 13 mph WNW wind, 0.00 inches rain/24hrs

.