1. Forum
  2. Hobby-Space
  3. Synchronet BBS

  • Let's Encrypt

    From Biggieb@HOBBYSPC to all on Mon Jun 1 07:43:24 2026
    So I have been getting this error for about a month and I reached out to Dove-Net a couple weeks ago and didn't really get an answer and now my webserver is down this morning. The Let's Encrypt cert has expired now and I can't renew it. My system has not outbound restrictions and seems to have no problem getting to the URL "https://acme-staging-v02.api.letsencrypt.org/directory" or pinging the address.

    Any ideas?

    6/1 07:06:00a SYNCRYPT !JavaScript C:\SBBS\exec\load\acmev2.js line 87: Error: Error fetching directory
    6/1 07:06:00a SYNCRYPT Timed event: '?letsyncrypt.js' returned -

    C:\sbbs\exec>jsexec letsyncrypt

    JSexec v3.21e-Win32 master/dba8d48f1 - Execute Synchronet JavaScript Module Compiled Mar 17 2026 01:22 with MSC 1944

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

    Reading script from C:\sbbs\exec\letsyncrypt.js
    C:\sbbs\exec\letsyncrypt.js compiled in 0.00 seconds
    !JavaScript C:\sbbs\exec\load\acmev2.js line 87: Error: Error fetching directory
    C:\sbbs\exec\letsyncrypt.js executed in 0.80 seconds
    !Module (letsyncrypt) set exit_code: 1

    JavaScript: Destroying context
    JavaScript: Destroying runtime

    Returning error code: 1

    ---
    þ Synchronet þ Hobby Space - Express Yourself hobbyspc.synchro.net
  • From Will-E@HOBBYSPC to Biggieb on Mon Jun 1 08:43:04 2026
    Make sure SBBS did not add the AWS server LE uses to the block list. This happened on HobbySPC and caused some issues with our webserver. Once it was removed from the blocklist it took a little bit for LE to reverify everything and start working again. I ran the jsexec command and seen a bunch of blocked inbound connections on the webserver. This is how I was able to determine the issue.

    ---
    þ Synchronet þ Hobby Space - Express Yourself hobbyspc.synchro.net
  • From Biggieb@HOBBYSPC to Will-E on Mon Jun 1 11:44:34 2026
    Make sure SBBS did not add the AWS server LE uses to the block list. This happened on HobbySPC and caused some issues with our webserver. Once it was removed from the blocklist it took a little bit for LE to reverify everything and start working again. I ran the jsexec command and seen a bunch of blocked inbound connections on the webserver. This is how I was able to determine the issue.


    Besides the filters in the BBS menu on the control panel, is there anywhere else I should be looking?

    ---
    þ Synchronet þ Hobby Space - Express Yourself hobbyspc.synchro.net
  • From BiggieB@HOBBYSPC/JJAMBBS to Will-E on Mon Jun 1 15:59:56 2026
    Make sure SBBS did not add the AWS server LE uses to the block list. This happened on HobbySPC and caused some issues with our webserver. Once it was removed from the blocklist it took a little bit for LE to reverify everything and start working again. I ran the jsexec command and seen a bunch of blocked inbound connections on the webserver. This is how I was able to determine the issue.


    Fixed it. BTW - nothing was blocking it. Some weird issues with the .ini file and the account link URL.

    I basically replaced the INI file which a stock file (from a new install) from backup and reran the "jsexec letsyncrypt.js", as though it was a new system, and it created a new link account, and it worked. Wohoo! Man, it sucked when it wasn't working. Inbound SMTP, IMAP, WEB and who knows what else that need SSL stopped working because the issue.

    Thanks!

    ---
    þ Synchronet þ Jersey Jam BBS - JerseyJam.com (1:266/325)
  • From Morningstarr@HOBBYSPC to BiggieB on Mon Jun 1 17:52:29 2026
    That's really good news dude. I made a fumble once, and our https was down for a hot minute. Thanks to my brother, he figured out the issue.

    ---
    þ Synchronet þ Hobby Space - Express Yourself hobbyspc.synchro.net
  • From BiggieB@HOBBYSPC/JJAMBBS to Morningstarr on Mon Jun 1 18:49:54 2026
    That's really good news dude. I made a fumble once, and our https was down for a hot minute. Thanks to my brother, he figured out the issue.


    Oh, and I had to issue the --REVOKE command. That didn't work before but when I replaced the INI file with stock, it then worked.

    ---
    þ Synchronet þ Jersey Jam BBS - JerseyJam.com (1:266/325)