Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 32202  |
|  Sam Alexander to Digital Man  |
|  Unable to figure out how to create ssl.c  |
|  07 Jul 25 21:01:47  |
 TZUTC: -0500 MSGID: 58307.sync_sys@1:103/705 2cd2a3a8 REPLY: 58304.sync_sys@1:103/705 2cd21ecd PID: Synchronet 3.21a-Linux master/40daa513e Jul 03 2025 GCC 13.3.0 TID: SBBSecho 3.28-Linux master/e2705e616 Jul 05 2025 GCC 12.2.0 COLS: 190 BBSID: BLUEBOX CHRS: CP437 2 FORMAT: flowed NOTE: FSEditor.js v1.105 Re: Unable to figure out how to create ssl.cert By: Digital Man to Sam Alexander on Mon Jul 07 2025 10:34 am > > You'd mentioned the ssl.cert should've been created automatically, but I didn't have it after I built SBBS. > > The ctrl/cryptlib.key (private key) and ctrl/cert.ssl (self-signed cert) files are automatically created when you *run* (not build) SBBS. Do you have the cryptlib.key file? Note: If you > change your system password, these files have to be recreated. I don't have /sbbs/ctrl/ssl.cert even after stopping and restarting SBBS, but I do have /sbbs/ctrl/cryptlib.key. I get these often in my sbbs logs. 7/7 20:13:52 mail Failed to open/read TLS certificate: /sbbs/ctrl/ssl.cert Also I'm trying to use letsyncrypt, and trying to generate a new key: /sbbs/exec/jsexec letsyncrypt --new-key I see in the logs where Let's Encrypt tries to read into the web server and pull out the file for authenticate, but the file doesn't exist. I have /sbbs/web/root/.well-known/acme-challenge/ but apparently the js isn't creating the file for Let's Encrypt to find. 7/7 20:50:50 web 0011 HTTP [23.178.112.213] Connection accepted on 192.168.4.109 port 80 from port 37161 7/7 20:50:50 web 0011 HTTP [23.178.112.213] Request 1: GET /.w ll-known/acme-challenge/b1NbeFUniIxhs2GGS_64fM91UKqr2fgDsgmRwJLEgaU HTTP/1.1 7/7 20:50:50 web 0011 HTTP [23.178.112.213] User-Agent: Mozilla/5.0 (compatible; Let's Encrypt validation server; +https://www.letsencrypt.org) 7/7 20:50:50 web 0011 HTTP [23.178.112.213] !ERROR: 404 Not Found (line 4031) request: /.well-known/acme-challenge/b1NbeFUniIxhs2GGS_64f 91UKqr2fgDsgmRwJLEgaU 7/7 20:50:51 web 0011 HTTP [23.178.112.213] Session thread terminated after 1 requests (0 clients and 2 threads remain, 27 served, 6 concurrently) For this the script fails: JSexec v3.21a-Linux master/40daa513e - Execute Synchronet JavaScript Module Compiled Jul 03 2025 19:17 with GCC 13.3.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 !JavaScript /sbbs/exec/load/acmev2.js line 307: Error: keyChange did not return 200 /sbbs/exec/letsyncrypt.js executed in 1.73 seconds !Module (letsyncrypt) set exit_code: 1 JavaScript: Destroying context JavaScript: Destroying runtime Returning error code: 1 So either route i'm not having much luck getting the certs setup for email. I even ran chmod 775 on /.well-known/acme-challenge folders which I'm running the jsexec as my sbbs user, owner of the sbbs folder, so I don't think it's a permissions thing. Thanks for any advise. --- þ Synchronet þ -==[ Totally Nerd BBS ]==- (Work in Progress) - totallynerd.com * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705) SEEN-BY: 103/13 705 105/81 106/201 124/5016 128/187 129/14 153/757 SEEN-BY: 153/7715 154/10 30 110 203/0 218/700 221/0 226/30 227/114 SEEN-BY: 229/110 206 317 400 426 428 550 700 705 240/1120 5832 263/1 SEEN-BY: 266/512 280/464 5003 5006 291/111 292/8125 301/1 320/219 SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124 SEEN-BY: 467/888 633/280 712/848 770/1 902/26 5020/400 8912 5054/30 SEEN-BY: 5075/35 PATH: 103/705 280/464 460/58 229/426 |
[ << oldest | < older | list | newer > | newest >> ]