After updating sbbs I tried to run jsexec letsencrypt.js and the response it this:

Reading script from /sbbs/exec/letsyncrypt.js
/sbbs/exec/letsyncrypt.js compiled in 0.00 seconds
Getting directory.
TLS ERROR 'Received TLS alert message: Bad record MAC' (-33) setting attribute 6001
0006 TLS ERROR 'Received TLS alert message: Bad record MAC' (-33) setting session active
Getting directory.
TLS ERROR 'Received TLS alert message: Bad record MAC' (-33) setting attribute 6001
0006 TLS ERROR 'Received TLS alert message: Bad record MAC' (-33) setting session active
!JavaScript : uncaught exception: Unable to read status /sbbs/exec/letsyncrypt.js executed in 1.81 seconds
!Module (letsyncrypt.js) set exit_code: 1

JavaScript: Destroying context
JavaScript: Destroying runtime

---
þ Synchronet þ Havens BBS havens.synchro.net
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: letsencrypt error
By: HusTler to All on Mon Aug 12 2019 02:54 pm

After updating sbbs I tried to run jsexec letsencrypt.js and the response it this:

Reading script from /sbbs/exec/letsyncrypt.js
/sbbs/exec/letsyncrypt.js compiled in 0.00 seconds
Getting directory.
TLS ERROR 'Received TLS alert message: Bad record MAC' (-33) setting attribute 6001
0006 TLS ERROR 'Received TLS alert message: Bad record MAC' (-33) setting session active
Getting directory.
TLS ERROR 'Received TLS alert message: Bad record MAC' (-33) setting attribute 6001
0006 TLS ERROR 'Received TLS alert message: Bad record MAC' (-33) setting session active
!JavaScript : uncaught exception: Unable to read status /sbbs/exec/letsyncrypt.js executed in 1.81 seconds
!Module (letsyncrypt.js) set exit_code: 1

That sounds like maybe a problem with values in letsyncrypt.ini or letsyncrypt.key.

digital man

Synchronet "Real Fact" #81:
Vertrauen has had the FidoNet node number 1:103/705 since 1992.
Norco, CA WX: 83.0øF, 46.0% humidity, 2 mph NNE wind, 0.00 inches rain/24hrs --- SBBSecho 3.08-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)