I'm having some issues with the letsyncrypt.js. It's throwing errors I don't understand. The output is below.

JSexec v3.17c-Linux (rev 1.211) - Execute Synchronet JavaScript Module
Compiled Mar 27 2020 16:26:53 with GCC 9.2.1

Loading configuration files from /sbbs/ctrl
JavaScript-C 1.8.5 2011-03-31
JavaScript: Creating runtime: 8388608 bytes
JavaScript: Initializing context (stack: 16384 bytes)

Reading script from /home/sbbs/sbbs/exec/letsyncrypt.js /home/sbbs/sbbs/exec/letsyncrypt.js compiled in 0.00 seconds
Getting directory.
Calling newOrder.
0008 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
0008 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
Location: https://acme-v02.api.letsencrypt.org/acme/order/81774718/2816976381 Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
Getting authorization.
0008 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
Getting authorization.
0008 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
Creating ../web/root/.well-known/acme-challenge/r0vTA1pQep4C-eGFh_w9jzZXH4jqlhHEe5v5k8ly6jw
Creating /sbbs/web/root/.well-known/acme-challenge/r0vTA1pQep4C-eGFh_w9jzZXH4jqlhHEe5v5k8ly6jw
Accepting challenge.
0008 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
Location: https://acme-v02.api.letsencrypt.org/acme/chall-v3/3627568420/r8VCMw Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
Link: <https://acme-v02.api.letsencrypt.org/acme/authz-v3/3627568420>;rel="up" Polling authorization.
0008 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
Polling authorization.
0008 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index" {"type":"http-01","status":"invalid","error":{"type":"urn:ietf:params:acme:error:dns","detail":"DNS problem: NXDOMAIN looking up A for bbs.nakedweasels.com - check that a DNS record exists for this domain","status":400},"url":"https://acme-v02.api.letsencrypt.org/acme/chall-v3/3627568420/r8VCMw","token":"r0vTA1pQep4C-eGFh_w9jzZXH4jqlhHEe5v5k8ly6jw"}
!JavaScript : uncaught exception: Authorization failed... https://acme-v02.api.letsencrypt.org/acme/authz-v3/3627568420 /home/sbbs/sbbs/exec/letsyncrypt.js executed in 3.49 seconds
!Module (letsyncrypt.js) set exit_code: 1

JavaScript: Destroying context
JavaScript: Destroying runtime

Returning error code: 1

I tried adding a CNAME for bbs.nakedweasels.com to my DNS that just points to nakedweasels.com, but that only removed the NXDOMAIN error.

Thanks for the help.

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

Re: LetSynCrypt Issues
By: Prime to All on Sun Mar 29 2020 05:56 am

I'm having some issues with the letsyncrypt.js. It's throwing errors I don't understand. The output is below.

Reach-out to Deuce in #synchronet at irc.synchro.net, that's his baby.

digital man

This Is Spinal Tap quote #33:
Nigel Tufnel: Well, so what? What's wrong with bein' sexy?
Norco, CA WX: 47.7oF, 86.0% humidity, 0 mph S wind, 0.00 inches rain/24hrs
--- SBBSecho 3.10-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)