• Letsyncrypt error.

    From Tony Langdon@VERT to All on Saturday, December 28, 2019 14:25:00
    Still trying to get HTTPS working. When I run letsyncrypt.js, I get the following error:

    sbbs@lemaker ~ $ jsexec letsyncrypt.js

    JSexec v3.17c-Linux (rev 1.210) - Execute Synchronet JavaScript Module
    Compiled Nov 3 2019 17:19:42 with GCC 4.6.3

    Loading configuration files from /sbbs/ctrl
    JavaScript-C 1.8.5 2011-03-31
    JavaScript: Creating runtime: 8388608 bytes
    JavaScript: Initializing context (stack: 16384 bytes)

    Reading script from /sbbs/exec/letsyncrypt.js
    /sbbs/exec/letsyncrypt.js compiled in 0.01 seconds
    libgcc_s.so.1 must be installed for pthread_cancel to work
    Aborted

    The library referenced is on the system, so this error message is very unhelpful. :(


    ... I shoot every third salesperson that calls. The second one just left.
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Digital Man@VERT to Tony Langdon on Saturday, December 28, 2019 14:18:53
    Re: Letsyncrypt error.
    By: Tony Langdon to All on Sat Dec 28 2019 02:25 pm

    Still trying to get HTTPS working. When I run letsyncrypt.js, I get the following error:

    sbbs@lemaker ~ $ jsexec letsyncrypt.js

    JSexec v3.17c-Linux (rev 1.210) - Execute Synchronet JavaScript Module Compiled Nov 3 2019 17:19:42 with GCC 4.6.3

    Loading configuration files from /sbbs/ctrl
    JavaScript-C 1.8.5 2011-03-31
    JavaScript: Creating runtime: 8388608 bytes
    JavaScript: Initializing context (stack: 16384 bytes)

    Reading script from /sbbs/exec/letsyncrypt.js
    /sbbs/exec/letsyncrypt.js compiled in 0.01 seconds
    libgcc_s.so.1 must be installed for pthread_cancel to work
    Aborted

    The library referenced is on the system, so this error message is very unhelpful. :(

    Can you jsexec anything else?

    Normally, letsyncrypt.js is run via timed event. Have you tried that?

    digital man

    This Is Spinal Tap quote #30:
    Big bottom, big bottom / Talk about mud flaps, my girl's got 'em!
    Norco, CA WX: 59.1øF, 61.0% humidity, 2 mph NNW wind, 0.00 inches rain/24hrs

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Tony Langdon@VERT to Digital Man on Sunday, December 29, 2019 20:15:00
    On 12-28-19 14:18, Digital Man wrote to Tony Langdon <=-

    The library referenced is on the system, so this error message is very unhelpful. :(

    Can you jsexec anything else?

    Yes, just ran tickit.js to prove it.

    Normally, letsyncrypt.js is run via timed event. Have you tried that?

    Yes, I did. From memory I got critical errors, but have reenabled that event. That's why I started using jsexec, so I could see the output.


    ... I couldn't repair the brakes.. So I made your horn louder!
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Digital Man@VERT to Tony Langdon on Sunday, December 29, 2019 02:07:31
    Re: Re: Letsyncrypt error.
    By: Tony Langdon to Digital Man on Sun Dec 29 2019 08:15 pm

    On 12-28-19 14:18, Digital Man wrote to Tony Langdon <=-

    The library referenced is on the system, so this error message is very unhelpful. :(

    Can you jsexec anything else?

    Yes, just ran tickit.js to prove it.

    Normally, letsyncrypt.js is run via timed event. Have you tried that?

    Yes, I did. From memory I got critical errors, but have reenabled that event. That's why I started using jsexec, so I could see the output.

    When run as a timed event, it doesn't use jsexec. It sounds like you're having an issue with jsexec and crpytlib (needed for TLS). I don't know if you're also having an issue with sbbs and cryptlib because I don't know what "critical errors" to which you are refering.

    digital man

    Synchronet "Real Fact" #46:
    Synchronet External X/Y/ZMODEM protocol driver (SEXYZ) was introduced in 2005. Norco, CA WX: 45.3øF, 94.0% humidity, 0 mph SW wind, 0.00 inches rain/24hrs

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Tony Langdon@VERT to Digital Man on Monday, December 30, 2019 09:57:00
    On 12-29-19 02:07, Digital Man wrote to Tony Langdon <=-

    When run as a timed event, it doesn't use jsexec. It sounds like you're having an issue with jsexec and crpytlib (needed for TLS). I don't know
    if you're also having an issue with sbbs and cryptlib because I don't
    know what "critical errors" to which you are refering.

    OK, had a typo in my timed event. The script seems to be running, just have fine tune things because I still have the self signed cert. At least the script is running now.


    ... Oh, I almost forgot . . . It's absolutley VITAL to insta
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Melkor@VERT/STARFRON to All on Thursday, October 15, 2020 04:48:23
    I dont check my logs very often unless I see a reason too. I decided to check them tonight and found this in my error log, The first instance is Sept 29th.

    evnt SYNCRYPT! JavaScript : uncaught exception: Authorization failed... https://acme-v02.api.letsencrypt.org/acme/authz-v3/755812921.
    And similar messages everytime its ran. I tried to run it manually with jsexec using the --force option and got the same message except the numbers at the end were /7902776507

    ---
    þ Synchronet þ Star Frontiers BBS starfron.synchronetbbs.org
  • From Digital Man@VERT to Melkor on Wednesday, October 14, 2020 23:02:21
    Re: Letsyncrypt error.
    By: Melkor to All on Thu Oct 15 2020 04:48 am

    I dont check my logs very often unless I see a reason too. I decided to check them tonight and found this in my error log, The first instance is Sept 29th.

    evnt SYNCRYPT! JavaScript : uncaught exception: Authorization failed... https://acme-v02.api.letsencrypt.org/acme/authz-v3/755812921.
    And similar messages everytime its ran. I tried to run it manually with jsexec using the --force option and got the same message except the numbers at the end were /7902776507

    Try some of the other command-line options for letsyncrypt.js. If all else fails, find Deuce on irc.synchro.net, he wrote that.

    digital man

    This Is Spinal Tap quote #11:
    Nigel Tufnel: No. no. That's it, you've seen enough of that one.
    Norco, CA WX: 72.9øF, 55.0% humidity, 0 mph WSW wind, 0.00 inches rain/24hrs

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net