BBS:      TELESC.NET.BR
Assunto:  letsyncrypt issue
De:       Digital Man
Data:     Fri, 13 Feb 2026 14:40:00 -0800
-----------------------------------------------------------
  hbRenb: hcletsyncrypt issue
  bBynb: hcDumas Walker bto cDIGITAL MAN bon cFri Feb 13 2026 09:14 amn

 > > 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.
-- 
                                            HYdigital man n(rob)

Synchronet "Real Fact" #97:
Synchronet v3.13a was released in September of 2005 (9 months after v3.12a)
Norco, CA WX: 67.3F, 52.0% humidity, 13 mph WNW wind, 0.00 inches rain/24hrs
n---
  mSynchronetn  hgVertrauen n hHome of Synchronet n gh[vert/cvs/bbs].synchro.net

-----------------------------------------------------------
[Voltar]