open https://gitlab.synchro.net/main/sbbs/-/issues/237

Running jsexec letsyncrypt returns the following error:`Command line: jsexec letsyncryptJSexec v3.18c-Linux master/d7cf7c577 - Execute Synchronet JavaScript ModuleCompiled Feb 27 2021 21:57:33 with GCC 7.5.0Loading configuration files from /sbbs/ctrl/JavaScript-C 1.8.5 2011-03-31JavaScript: Creating runtime: 8388608 bytesReading script from /sbbs/exec/letsyncrypt.js/sbbs/exec/letsyncrypt.js compiled in 0.00 seconds!JavaScript /sbbs/exec/letsyncrypt.js line 270: Error: Error -44 calling cryptAddPrivateKey()/sbbs/exec/letsyncrypt.js executed in 0.29 seconds!Module (letsyncrypt) set exit_code: 1`I have attached the letsyncrypt.js (should be latest version).[letsyncrypt.js](/uploads/e0fd41a8d72411e625d98b272eacd8be/letsyncrypt.js)
--- SBBSecho 3.13-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/237#note_1694

System Info:``` Synchronet BBS for Linux Version 3.18 Revision C Mar 10 2021 07:47 SMBLIB 2.61 GCC 9.3.0 https://gitlab.synchro.net - master/e2bb9dde9 Copyright 2020 Rob Swindell - http://synchro.net JavaScript-C 1.8.5 2011-03-31 cryptlib 3.4.5 (345) Linux 5.4.0-66-generic x86_64 ```If you need anymore info, let me know.
--- SBBSecho 3.13-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/237#note_1695

That error indicates that the script could not read your private key from letsyncrypt.key, but that there's already a private key in that file. The most likely causes of this issue are that the hostname of the AJAX service has changed (ie: the Host line in the State section of your INI file), or your system password has changed.If you recently changed your system password, it's possible that my change to scfg which updated private keys when the system password is changed missed that file. If that's the case, keeping your private key will require some effort on your part... basically, you'll need to change your system password back to the old one using the current scfg, then update scfg and change it to the new one.I'll update this ticket when/if I make that commit.
--- SBBSecho 3.13-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/237#note_1697

Assigning to @rswindell in the hope that he addresses the TODO comment.
--- SBBSecho 3.13-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/237#note_1696

Yep, that's the problem. Pushing the commit right away. Be sure to set your syspass back first, update, then change your syspass to what you want.Sorry for the inconvenience.
--- SBBSecho 3.13-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

close https://gitlab.synchro.net/main/sbbs/-/issues/237
--- SBBSecho 3.13-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/237#note_1709

`3/15 21:58:47 evnt SYNCRYPT !JavaScript : uncaught exception: Authorization failed... https://acme-v02.api.letsencrypt.org/acme/authz-v3/...'Not gonna post the end of the URL because I think it's private... but essentially it just doesn't find the ACME challenge...
--- SBBSecho 3.13-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/237#note_1711

Have you changed your private cert/key, or changed your system password?Is your system receiving HTTP requests for the configured internet email domain (and any other letsyncrypt.ini domains) on port 80?
--- SBBSecho 3.13-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/237#note_1712

I did change my system password but I changed it back. As it happens, no, my web server is listening on another port. How can I specify this in letsyncrypt.ini?
--- SBBSecho 3.13-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/237#note_1715

You either have to do DNS activation, or port 80 http activation.. there are no other options. Depending on what you're using for (dyn)dns, there are tools to do DNS validation, many providers have an API for this.Those are really the only two options available. It might be worth considering a $10/month VPS to host on.
--- SBBSecho 3.13-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/237#note_1716

I do host on a VPS, but I've got another website listening on port 80/443. Would I have to take this website down for this to work?
--- SBBSecho 3.13-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/237#note_1717

If you can serve the .well+known directory from sbbs/web/root on your main http service on port 80 that will work.. should just be another content search path in your config. You may be able to set the directory in ctrl/letsyncrypt.ini
--- SBBSecho 3.13-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)