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)