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,314 of 43,341   
   Digital Man to Dumas Walker   
   Installing manually obtai   
   16 Feb 26 13:43:28   
   
   TZUTC: -0800   
   MSGID: 55913.sync@1:103/705 2df99fe9   
   REPLY: 74924.sync@723:320/1 2df983f7   
   PID: Synchronet 3.21b-Win32 master/021fd13d4 Feb 15 2026 MSC 1944   
   TID: SBBSecho 3.37-Linux master/160d568ce Feb 16 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 Mon Feb 16 2026 09:27 am   
      
    > >  > 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.   
      
   There was self-signed certificate.   
      
    > 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!   
      
   Perhaps. I wouldn't be so sure until the problem is actually root-cause. But   
   you sure seem sure.   
      
    > 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.   
      
   So I guess we'll never know if there was a BUG! or not. Great. Thanks so much.   
   --    
                                               digital man (rob)   
      
   Steven Wright quote #27:   
   Experience is something you don't get until just after you need it.   
   Norco, CA WX: 50.3øF, 92.0% humidity, 8 mph WSW wind, 0.12 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