• !JavaScript /sbbs/exec/load/acmev2.js line 312: Error: keyChange retur

    From Angel Ripoll@2:341/66 to Todos on Mon Apr 20 20:16:30 2026
    Hola Todos!

    I'm having a problem with my Let's Syncrypt certificate. It's not working right now, and when I try to renew it with "jsexec "letsyncrypt.js --force", I get the following error: "!JavaScript /sbbs/exec/load/acmev2.js line 139: Error: newOrder responded with 400 not 201". I get a similar error with other parameters.

    Does anyone know how to fix this error?

    Thanks in advance.

    Un saludo,
    Angel Ripoll
    aripoll @ zruspas.org

    --- GoldED+/LNX 1.1.5-b20260304 + HPT 1.9 + Binkd 1.1 en Debian
    * Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)
  • From Digital Man@1:103/705 to Angel Ripoll on Mon Apr 20 12:52:19 2026
    Re: !JavaScript /sbbs/exec/load/acmev2.js line 312: Error: keyChange retur
    By: Angel Ripoll to Todos on Mon Apr 20 2026 08:16 pm

    Hola Todos!

    I'm having a problem with my Let's Syncrypt certificate. It's not working right now, and when I try to renew it with "jsexec "letsyncrypt.js --force", I get the following error: "!JavaScript /sbbs/exec/load/acmev2.js line 139: Error: newOrder responded with 400 not 201". I get a similar error with other parameters.

    Does anyone know how to fix this error?

    The clues are: your web server log output and the detail link in the Let's Encrypt error report, if provided.
    --
    digital man (rob)

    Rush quote #27:
    Growing up it all seems so one-sided, opinions all provided
    Norco, CA WX: 73.6øF, 46.0% humidity, 7 mph WNW wind, 0.00 inches rain/24hrs --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Angel Ripoll@2:341/66 to Digital Man on Thu Apr 23 20:14:02 2026
    Hola Digital!

    20 Apr 26 12:52, Digital Man dijo a Angel Ripoll:

    The clues are: your web server log output and the detail link in the Let's Encrypt error report, if provided.

    It seems to be working now. I saw that the log was showing "TLS ERROR 'Server certificate has expired' (-3) setting private key". I deleted the ctrl/letsyncrypt.key file, then ran "exec/jsexec.sj letsyncrypt.js --new-key", and now port 443 works with the certificate (although I'm still getting the "returned 400, not 200" error). Is that normal?

    Un saludo,
    Angel Ripoll
    aripoll @ zruspas.org

    --- GoldED+/LNX 1.1.5-b20260304 + HPT 1.9 + Binkd 1.1 en Debian
    * Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)
  • From Digital Man@1:103/705 to Angel Ripoll on Thu Apr 23 14:16:06 2026
    Re: !JavaScript /sbbs/exec/load/acmev2.js line 312: Error: keyChange retu
    By: Angel Ripoll to Digital Man on Thu Apr 23 2026 08:14 pm

    Hola Digital!

    20 Apr 26 12:52, Digital Man dijo a Angel Ripoll:

    The clues are: your web server log output and the detail link in the Let's Encrypt error report, if provided.

    It seems to be working now. I saw that the log was showing "TLS ERROR 'Server certificate has expired' (-3) setting private key". I deleted the ctrl/letsyncrypt.key file, then ran "exec/jsexec.sj letsyncrypt.js --new-key", and now port 443 works with the certificate (although I'm still getting the "returned 400, not 200" error). Is that normal?

    No. Check the output for more clues.
    --
    digital man (rob)

    Synchronet/BBS Terminology Definition #29:
    DTR = Data Terminal Ready
    Norco, CA WX: 75.3øF, 33.0% humidity, 3 mph WNW wind, 0.00 inches rain/24hrs --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Angel Ripoll@2:341/66 to Digital Man on Thu Apr 23 23:34:38 2026
    Hola Digital!

    23 Apr 26 14:16, Digital Man dijo a Angel Ripoll:

    getting the "returned 400, not 200" error). Is that normal?

    No. Check the output for more clues.

    I just did "exec/jsexec letsyncrypt.js --force" and now it worked perfectly:

    exec/jsexec letsyncrypt.js --force

    JSexec v3.22a-Linux master/1f0bc9c6b - Execute Synchronet JavaScript Module Compiled Apr 19 2026 11:14 with GCC 14.2.0

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

    Reading script from /sbbs/exec/letsyncrypt.js
    /sbbs/exec/letsyncrypt.js compiled in 0.00 seconds
    /sbbs/exec/letsyncrypt.js executed in 4.23 seconds

    JavaScript:Destroying Context
    JavaScript: Destroying runtime

    Previously, `--force`, `--new-key`, and `--revoke` weren't working. Now I've tried `--new-key` and I get the error "keyChange returned 400, not 200". I assume this is because I already have a valid certificate. If I run `--force`, the result is the one I mentioned before.

    Thank you very much :)

    Un saludo,
    Angel Ripoll
    aripoll @ zruspas.org

    --- GoldED+/LNX 1.1.5-b20260304 + HPT 1.9 + Binkd 1.1 en Debian
    * Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)