TZUTC: -0500   
   MSGID: 74924.sync@723:320/1 2df983f7   
   REPLY: 55901.sync@1:103/705 2df860ab   
   PID: Synchronet 3.21a-Linux master/123f2d28a Jul 12 2025 GCC 12.2.0   
   TID: SBBSecho 3.37-Linux master/160d568ce Feb 16 2026 GCC 12.2.0   
   BBSID: CAPCITY2   
   CHRS: CP437 2   
   FORMAT: flowed   
   >  > 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   
   forc   
   > it do something. That's not a "BUG!".   
      
   What you are saying here assumes there was a signed cert in place with an   
   expiration.  The problem is that there wasn't one because letsyncrypt   
   at some point failed to get one.   
      
   No signed-certificate = no expiration date = "doing *nothing*" = BUG!   
      
   It should keep trying to get one until it is successful.  If it isn't = 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)?   
      
   See my "long gone" comment above.  Whenever letsyncrypt dropped its deuce,   
   it wasn't initially noticed and whatever logs its oopsie got written in   
   are no longer here.   
      
   I provided the output of what some of the more recent attempts, with   
   command lines, did.   
      
   There is no reason for me to bother with it now. haproxy saved the day and,   
   because it reads the pem files directly instead of requiring them to be   
   converted into some nonsense format (that can only be generated by buggy   
   letsyncrypt), it is easier to use and figure out.   
      
      
    * SLMR 2.1a * Docs? Why look at the Docs? Nurses are better.   
   ---   
    þ Synchronet þ CAPCITY2 * Capitol City Online   
    * 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