TZUTC: -0800   
   MSGID: 55901.sync@1:103/705 2df860ab   
   REPLY: 74915.sync@723:320/1 2df83f2b   
   PID: Synchronet 3.21b-Linux master/a3797f107 Feb 15 2026 GCC 12.2.0   
   TID: SBBSecho 3.37-Linux master/a3797f107 Feb 15 2026 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   FORMAT: flowed   
   NOTE: FSEditor.js v1.105   
     Re: Installing manually obtai   
     By: Dumas Walker to DIGITAL MAN on Sun Feb 15 2026 10:21 am   
      
    > > ../../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!);   
      
   letsyncrypt doesn't re-request a signed-certificate every time you run it. It   
   has built-in expiration for the cert and will do *nothing* if you just run it   
   without any options, until the cert times out or you specify an option to   
   force it do something. That's not a "BUG!".   
      
    > (3) by the time the cert expired, evidence of whatever problem letsyncypt   
    > had (assuming it reported it to begin with) was long gone;   
      
   Did you check your web server log output like I already suggested? It should   
   explain what's happening when it's requesting the challenge file that   
   letsyncrypt.js creates (but couldn't be retreived by the Let's Encrypt ACME   
   service or whatever it is)?   
   --    
                                               digital man (rob)   
      
   Breaking Bad quote #16:   
   Thinking Operation Breath Mint evertime you and me are on a stakeout together.   
   Norco, CA WX: 59.8øF, 58.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: 10/0 1 102/401 103/1 17 705 105/81 106/201 124/5016 128/187   
   SEEN-BY: 129/14 153/7715 154/110 218/0 1 215 601 700 840 860 880 226/30   
   SEEN-BY: 227/114 229/110 112 134 206 317 400 426 428 470 700 705 266/512   
   SEEN-BY: 280/464 291/111 301/1 320/219 322/757 342/200 396/45 460/58   
   SEEN-BY: 633/280 712/848 902/26 5075/35   
   PATH: 103/705 218/700 229/426