1. Forum
  2. DOVE-Net
  3. Synchronet Discussion

  • Error in Syncrypt?

    From Wang Bu@VERT to All on Thursday, August 27, 2026 08:31:12
    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 Thursday, August 27, 2026 14:49:07
    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 to Digital Man on Friday, August 28, 2026 16:03:11
    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
  • From bbsing@VERT/LUNAROUT to Digital Man on Wednesday, September 09, 2026 12:17:53
    Re: Error in Syncrypt?
    By: Wang Bu to All on Thu Aug 27 2026 08:31 am

    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 this.
    I was getting a similar error. Opened port 80 and finally it went away.

    command to verify.
    ./jsexec -Ldebug letsyncrypt.js



    BBsing, Sysop of Lunar Outpost, lunarout.sycnhro.net

    ---
    þ Synchronet þ Lunar Outpost BBS