1. Forum
  2. FidoNet
  3. SYNC SYSOPS

  • letsyncrypt authorization error

    From Nick Young@1:103/705 to GitLab issue in main/sbbs on Fri Feb 9 19:22:03 2024
    open https://gitlab.synchro.net/main/sbbs/-/issues/715

    Got an email about my letsencrypt certs expiring, turns out letsyncrypt.js is failing to run. I have tried to reset the .ini file to standard (without key-id & State) to no avail.

    ```plaintext
    nick ➜ /sbbs/ctrl $ jsexec letsyncrypt.js
    JSexec v3.20a-Linux master/e230bd350 - Execute Synchronet JavaScript Module Compiled Jan 8 2024 10:03:03 with GCC 11.4.0Loading configuration files from /sbbs/ctrl
    JavaScript-C 1.8.5 2011-03-31
    JavaScript: Creating runtime: 8388608 bytesReading script from /sbbs/exec/letsyncrypt.js
    /sbbs/exec/letsyncrypt.js compiled in 0.00 seconds
    !JavaScript : uncaught exception: Authorization failed... https://acme-v02.api.letsencrypt.org/acme/authz-v3/<redacted>
    /sbbs/exec/letsyncrypt.js executed in 4.10 seconds
    !Module (letsyncrypt.js) set exit_code: 1JavaScript: Destroying context JavaScript: Destroying runtimeReturning error code: 1
    ```
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Justin Waymire@1:103/705 to GitLab note in main/sbbs on Tue Feb 13 12:14:08 2024
    https://gitlab.synchro.net/main/sbbs/-/issues/715#note_4825

    Granted I have a brand new install, however, when attempting to use letsyncrypt, I noticed an error in the default values of the documentation. My true www root directory is "/sbbs/webv4/root" as shown in the server setup within scfg. All the documentation notes "/sbbs/web/root" and that directory does exist and is populated as well. I can only guess without going through the commits that there was an update that changed the primary directory. Once I changed the directorys in the letencrypt.ini, I went ahead and mirrored the .well-known/acme-challenge directories over to /sbbs/web4/root letsencrypt issued a certificate successfully.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nick Young@1:103/705 to GitLab note in main/sbbs on Wed Feb 14 01:18:31 2024
    https://gitlab.synchro.net/main/sbbs/-/issues/715#note_4829

    Interesting. This was working for me though, and nothing has changed, so it's odd it would just stop working.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nick Young@1:103/705 to GitLab note in main/sbbs on Wed Feb 14 02:19:07 2024
    https://gitlab.synchro.net/main/sbbs/-/issues/715#note_4830

    I now get this after trying a blank config.

    ```plaintext
    /sbbs/exec/letsyncrypt.js compiled in 0.00 seconds
    !JavaScript /sbbs/exec/load/acmev2.js line 139: Error: newOrder responded with 400 not 201
    /sbbs/exec/letsyncrypt.js executed in 2.11 seconds
    ```
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nick Young@1:103/705 to GitLab note in main/sbbs on Fri Feb 16 17:48:13 2024
    https://gitlab.synchro.net/main/sbbs/-/issues/715#note_4863

    I commented out all entries under `[key_id]` and `[State]` in `letsyncrypt.ini`, also removed `letsyncrypt.key` and then it worked. I think the newOrder issue occurs when you get rate-limited by LetsEncrypt so no idea why it didn't just simply renew.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nick Young@1:103/705 to GitLab issue in main/sbbs on Fri Feb 16 17:48:13 2024
    close https://gitlab.synchro.net/main/sbbs/-/issues/715
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)