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

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 ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Installing manually obtai
By: Digital Man to Dumas Walker on Mon Feb 16 2026 01:43 pm

Steven Wright quote #27:
Experience is something you don't get until just after you need it.

Some time ago, I saw a quote that said "Good judgment comes from experience. And experience, well, that comes from bad judgment."

Nightfox

---
þ Synchronet þ Digital Distortion: digitaldistortionbbs.com

Re: Installing manually obtai
By: Dumas Walker to DIGITAL MAN on Mon Feb 16 2026 09:27 am

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.

if you backed up you could check your backups.
it's not that hard.

only be generated by buggy letsyncrypt), it is easier to use and
figure out.

setting up letsyncrypt with datastream was amazingly easy to do.
i was surprised.


--
"Before using Wildcat....This Company did not have a convenient way of
looking after some of the richest clients in the world...Now we do!"
---
þ Synchronet þ ::: BBSES.info - free BBS services :::