• Error in Syncrypt?

    From Wang Bu@VERT to All on Thu Aug 27 08:31:12 2026
    Hi,

    I'm suddenly having a problem with Syncrypt, such that my node is no longer accessible via its domain.

    I just noticed it today, but now, when the letsyncrypt.js runs, it shows an "Uncaught exception: No challenges fulfilled!", or a "http.js line 147: Error: Unable to read status".

    In the Terminal Server thread, I am also receiving a "1016 TLS ERROR 'Requested item not found in object' (-43 getting remote certificate)" error.

    It seems that the Let's Encrypt script is no longer working somehow, since I did not change anything.

    Anyone knows about this? Or experiencing the same?

    Need help guys. Thank you!

    Regards,
    Wang Bu

    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From Digital Man@VERT to Wang Bu on Thu Aug 27 14:49:07 2026
    Re: Error in Syncrypt?
    By: Wang Bu to All on Thu Aug 27 2026 08:31 am

    I'm suddenly having a problem with Syncrypt, such that my node is no longer accessible via its domain.

    I just noticed it today, but now, when the letsyncrypt.js runs, it shows an "Uncaught exception: No challenges fulfilled!", or a "http.js line 147: Error: Unable to read status".

    Get the latest exec/letsyncrypt.js and load/http.js from gitlab (or vert) and try again. Usually there's more details available somewhere (e.g. via debug log output or whatever) - try running via 'jsexec -Ldebug' to see (and copy/paste) all the possible log output that should indicate the cause.
    --
    digital man (rob)

    Steven Wright quote #13:
    How do you tell when you're out of invisible ink?
    Norco, CA WX: 93.3°F, 46.0% humidity, 12 mph WNW wind, 0.00 inches rain/24hrs ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From Wang Bu@VERT to Digital Man on Thu Aug 27 18:20:17 2026
    Re: Error in Syncrypt?
    By: Digital Man to Wang Bu on Thu Aug 27 2026 02:49 pm

    Get the latest exec/letsyncrypt.js and load/http.js from gitlab (or vert) and try again. Usually there's more details available somewhere (e.g. via debug log output or whatever) - try running via 'jsexec -Ldebug' to see (and copy/paste) all the possible log output that should indicate the cause.

    Hi Digital Man,

    Thanks for the advise! I will try to download the latest letsyncrypt.js and http.js in a while, but thanks for the debug option so I could see the details of what's happening when I run the script.

    Here's the debug log when I enabled the debug mode:

    JSexec v3.21e-Win32 master/dba8d48f1 - Execute Synchronet JavaScript Module Compiled Mar 17 2026 01:22 with MSC 1944

    Loading configuration files from C:\sbbs\ctrl
    JavaScript-C 1.8.5 2011-03-31
    JavaScript: Creating runtime: 167772160 bytes

    Reading script from C:\sbbs\exec\letsyncrypt.js
    C:\sbbs\exec\letsyncrypt.js compiled in 0.00 seconds
    Getting directory.
    Calling newOrder.
    Location: https://acme-v02.api.letsencrypt.org/acme/order/2610049187/550205124915
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    Getting authorization.
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    Creating /sbbs/webv4/root\.well-known/acme-challenge/QotsiC_rvYM8TCcXbt2Fovi9QSoU7IEQwAipDUqHCR8
    Accepting challenge.
    Location: https://acme-v02.api.letsencrypt.org/acme/chall/2610049187/768144688935/0Gwqxw
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    Link: <https://acme-v02.api.letsencrypt.org/acme/authz/2610049187/768144688935>;rel="up"
    Polling authorization.
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    Polling authorization.
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    Polling authorization.
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    Polling authorization.
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index" {"type":"http-01","url":"https://acme-v02.api.letsencrypt.org/acme/chall/2610049187/768144688935/0Gwqxw","status":"invalid","validated":"2026-08-28T01:17:22Z","error":{"type":"urn:ietf:params:acme:error:connection","detail":"103.55.10.7: Fetching http://bbs.jacobcat.app/.well-known/acme-challenge/QotsiC_rvYM8TCcXbt2Fovi9QSoU7IEQwAipDUqHCR8: Timeout during connect (likely firewall problem)","status":400},"token":"QotsiC_rvYM8TCcXbt2Fovi9QSoU7IEQwAipDUqHCR8","validationRecord":[{"url":"http://bbs.jacobcat.app/.well-known/acme-challenge/QotsiC_rvYM8TCcXbt2Fovi9QSoU7IEQwAipDUqHCR8","hostname":"bbs.jacobcat.app","port":"80","addressesResolved":["103.55.10.7"],"addressUsed":"103.55.10.7"}]}
    !JavaScript : uncaught exception: No challenges fulfilled! C:\sbbs\exec\letsyncrypt.js executed in 29.54 seconds
    !Module (letsyncrypt.js) set exit_code: 1

    JavaScript: Destroying context
    JavaScript: Destroying runtime

    Returning error code: 1

    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From Wang Bu@VERT/JACOBCAT to Digital Man on Fri Aug 28 16:03:11 2026
    Re: Error in Syncrypt?
    By: Digital Man to Wang Bu on Thu Aug 27 2026 02:49 pm

    Get the latest exec/letsyncrypt.js and load/http.js from gitlab (or vert) and try again. Usually there's more details available somewhere (e.g. via debug log output or whatever) - try running via 'jsexec -Ldebug' to see (and copy/paste) all the possible log output that should indicate the cause.

    Thanks for the debug logs... I found out that it's my VPN connection no longer port forwarding to my servers in my PC, which after so much troubleshooting, was caused by a recent update to the Windows Insider builds.

    After trying to isolate the problem, ultimately I had to roll back to the previous Insider build. Then it started working again. :)

    I guess I have something to report to Windows Feedback regarding this. ^_^

    Regards,
    Wang Bu

    ---
    ■ Synchronet ■ Jacob's Hideout BBS - bbs.jacobcat.app