TZUTC: -0500   
   MSGID: 74915.sync@723:320/1 2df83f2b   
   REPLY: 55896.sync@1:103/705 2df7471d   
   PID: Synchronet 3.21a-Linux master/123f2d28a Jul 12 2025 GCC 12.2.0   
   TID: SBBSecho 3.37-Linux master/a3797f107 Feb 15 2026 GCC 12.2.0   
   BBSID: CAPCITY2   
   CHRS: CP437 2   
   FORMAT: flowed   
   > ../../3rdp_src/cl/cryptlib.h:#define CRYPT_ERROR_NOTFOUND       ( -43 ) /*   
   > Requested item not found in object */   
      
   > Most likely, it just doesn't support the format of the .pem file.   
      
   > I think the --import option expects a pkcs7 certificate, while   
   > the --import-pkcs12 option expects a pkcs12 certificate.   
      
   > The utility works for those that know how to work it.   
      
   I might know how to work it if the docs were more clear about what needs to   
   be done.  I suspect that fullchain.pem and privkey.pem need to be cat/tee'd   
   together, in that order, to make it work.   
      
   Back to the letsyncrypt bug... after reading up on how Let's Encrypt works, I   
   can figure out the following:   
      
   (1) at some point, letsyncrypt hit an error that it either reported or   
   didn't know what to do with;   
   (2) after that, it kept reporting '0' even though it was *not* working   
   (BUG!);   
   (3) by the time the cert expired, evidence of whatever problem letsyncypt had   
   (assuming it reported it to begin with) was long gone;   
   (4) the other two or three options on the wiki were getting errors because   
   they likely require a valid cert to already be in place on the web server   
   end. Since letsyncypt had stopped working a while back, there wasn't one.   
      
   While researching Let's Encrypt, I found a lot of good resources regarding   
   using their certs with haproxy.  As I am already using haproxy for something   
   else so I put those good resources to use.  I was able to install the cert into   
   haproxy, set up new front and back ends for web traffic, and had a working   
   website again in < 30 minutes.   
      
   I started seeing some SMTPS errors so I put the self-signed cert back into   
   place in /ctrl and that seemed to fix those.   
      
      
    * SLMR 2.1a * Anything good is either illegal, immoral or fattening.   
   ---   
    þ Synchronet þ CAPCITY2 * Capitol City Online   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 129/14 153/757 7715   
   SEEN-BY: 154/10 30 110 203/0 218/700 221/0 226/30 227/114 229/110   
   SEEN-BY: 229/112 134 206 317 400 426 428 470 700 705 240/1120 5832   
   SEEN-BY: 263/1 266/512 280/464 5003 5006 291/111 292/8125 301/1 310/31   
   SEEN-BY: 320/219 322/757 341/66 234 342/200 396/45 423/120 460/58   
   SEEN-BY: 460/256 1124 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