home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   SYNCHRONET      Rob Swindell fetishistic worship forum      43,341 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 43,267 of 43,341   
   Digital Man to Dumas Walker   
   letsyncrypt issue   
   12 Feb 26 14:11:33   
   
   TZUTC: -0800   
   MSGID: 55864.sync@1:103/705 2df4604d   
   REPLY: 74882.sync@723:320/1 2df437cf   
   PID: Synchronet 3.21b-Win32 master/8409089bb Feb 12 2026 MSC 1944   
   TID: SBBSecho 3.37-Linux master/8409089bb Feb 12 2026 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   FORMAT: flowed   
   NOTE: FSEditor.js v1.105   
     Re: letsyncrypt issue   
     By: Dumas Walker to All on Thu Feb 12 2026 09:01 am   
      
    > This week, I have started having certificate issues.  letsyncrypt is   
    > enabled, running, and I have not touched the configs for it.   
    >   
    > Firefox users are getting a security warning which, on further inspection,   
    > is complaining about a self signed cert.  Here is what appears on the BBS   
    > side during such a connection:   
    >   
    > 2/12 08:46:38 web  0062 TLS WARNING 'Received TLS alert message: Bad   
    > certificate' (-26) popping data   
    >   
    > Chrome also throws a security warning.  Locally:   
    >   
    > 2/12 08:48:49 web  0057 TLS WARNING 'Received TLS alert message: Certificate   
    > unknown' (-26) setting session active   
    >   
    > Running the event, or running letsyncrypt from cli, don't offer any clues of   
    > a potential issue:   
    >   
    > 2/12 08:50:02 evnt BBS Events Semaphore signaled for Timed Event: SYNCRYPT   
    > 2/12 08:50:02 evnt SYNCRYPT Running native timed event: ?letsyncrypt.js   
    > 2/12 08:50:02 evnt SYNCRYPT Timed event: '?letsyncrypt.js' returned 0   
    >   
    > Running from cli produces no clues:   
    >   
    > $ ./jsexec letsyncrypt.js   
      
   letencrypt.js support command-line options too:   
   https://wiki.synchro.net/module:letsyncrypt   
      
    > The contents of my ini file:   
    >   
    > ; $Id: letsyncrypt.ini,v 1.1 2019/07/24 22:32:54 rswindell Exp $   
    > ; For use with exec/letsyncrypt.js   
    > ; See http://wiki.synchro.net/module:letsyncrypt for details   
    >   
    > 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   
    >   
    > Is anyone else having issues?   
      
   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   
   it also reports a self-signed cert. So it definitely seems like the   
   certificate being sent out doesn't match your letsyncrypt.cfg.   
      
   One thing you can do is disable self-signed cert generation by setting   
   SCFG->System->Security->Create Self-signed Certificate to "No".   
   --    
                                               digital man (rob)   
      
   Synchronet "Real Fact" #130:   
   Synchronet v3.20b was released on January 3, 2025 (3 years after v3.19b)   
   Norco, CA WX: 65.7øF, 49.0% humidity, 6 mph WNW wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.37-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 1/19 100 16/0 19/37 40 103/705 105/81 106/201 123/130 124/5016   
   SEEN-BY: 128/187 129/14 142/104 153/757 7715 154/10 30 110 203/0 218/700   
   SEEN-BY: 221/0 1 6 226/30 227/114 229/110 112 134 206 317 400 426   
   SEEN-BY: 229/428 470 700 705 240/1120 5832 263/1 266/512 280/464 5003   
   SEEN-BY: 280/5006 291/111 292/8125 301/1 310/31 320/119 219 319 2119   
   SEEN-BY: 322/757 762 326/101 341/66 234 342/200 396/45 423/81 120   
   SEEN-BY: 460/58 633/280 712/848 770/1 902/26 5020/400 5075/35   
   PATH: 103/705 280/464 221/1 320/219 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca