TZUTC: -0700   
   MSGID: 58413.sync_sys@1:103/705 2cfa158e   
   PID: Synchronet 3.21a-Linux master/6d0371950 Jul 15 2025 GCC 12.2.0   
   TID: SBBSecho 3.29-Linux master/7c07d600a Aug 02 2025 GCC 12.2.0   
   BBSID: VERT   
   CHRS: ASCII 1   
   FORMAT: flowed   
   https://gitlab.synchro.net/main/sbbs/-/issues/960#note_7480   
      
   I think the problem is that there seems to be a bit of a issue.   
   It seems he cannot get letsencrypt to create a cert unless ssl.cert already   
   exists   
   for ssl.cert to exist it has to be created as a self-signed cert   
   Which means this has to be enabled in scfg   
   and then you have to connect to the https port   
   and then you'll have to go info scfg and turn off self-signed certs   
   then you'd have to run letsyncript   
      
   Unless, as sduensin appears to have done, an empty ssl.cert is sufficient,   
   which case letsyncript.js should probably either create it itself, or just   
   continue if there isn't one.    
      
   Of course, he was also able to find his account number in the firewall log so   
   it may have been successful at some point but wouldn't renew for some reason.   
   I think it would take deeper debugging.   
   --- SBBSecho 3.29-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/13 705 105/81 106/201 124/5016 128/187 129/14 153/757   
   SEEN-BY: 153/7715 154/10 30 110 203/0 218/700 221/0 226/30 227/114   
   SEEN-BY: 229/110 206 317 400 426 428 550 700 705 240/1120 5832 263/1   
   SEEN-BY: 266/512 280/464 5003 5006 291/111 292/8125 301/1 320/219   
   SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124   
   SEEN-BY: 467/888 633/280 712/848 770/1 902/26 5020/400 8912 5054/30   
   SEEN-BY: 5075/35   
   PATH: 103/705 280/464 460/58 229/426