Is there a letsencrypt work around for Synchronet Web serve?
I've
uninstalled letsencrypt and certbot. I would like to have synchronets web server handle all web requests including https. Currently I'm still getting a warning that the certificate is unsigned.
How can I get a signed certicate
just using synchronets web server?
No Apache or any other server software.
Just the default Synchronet Web server. Eg. point my browser to https://havens.synchronetbbs.org without any warnings or errors. Is that possible?
HusTler wrote to All <=-
Is there a letsencrypt work around for Synchronet Web serve?
I've uninstalled letsencrypt and certbot. I would like to have
synchronets web server handle all web requests including https.
Currently I'm still getting a warning that the certificate is
unsigned. How can I get a signed certicate just using synchronets
web server? No Apache or any other server software. Just the
default Synchronet Web server. Eg. point my browser to https://havens.synchronetbbs.org without any warnings or errors.
Is that possible?
There is no "workaround" required.
It only requires correct configuration.
You've been given MULTIPLE suggestions by MULTIPLE people, and
don't even bother responding that you received them, much less
tried them, and whether they worked or not. You don't even
Re: Re: Letsencrypt work around?works
By: Gamgee to HusTler on Thu Dec 12 2019 07:57 am
There is no "workaround" required.
It only requires correct configuration.
You've been given MULTIPLE suggestions by MULTIPLE people, and
don't even bother responding that you received them, much less
tried them, and whether they worked or not. You don't even
I didn't reply because none of the suggestions worked. When something
I'll let everyone know it worked. I've followed everyone's instructions to the tee. My site is still insecure.
I didn't reply because none of the suggestions worked. When somethingworks I'll let everyone know
You've been given MULTIPLE suggestions by MULTIPLE people, and
don't even bother responding that you received them, much less
tried them, and whether they worked or not. You don't even
I didn't reply because none of the suggestions worked.
When something works I'll let everyone know it worked. I've followedeveryone's instructions to the tee. My site is still insecure.
I always get this when I run letsyncrypt:
Reading script from /sbbs/exec/letsyncrypt.js
/sbbs/exec/letsyncrypt.js compiled in 0.00 seconds
Getting directory.
Calling newOrder.
0008 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
0008 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
{
"type": "urn:ietf:params:acme:error:malformed",
"detail": "JWS verification error",
"status": 400
}
!JavaScript : uncaught exception: newOrder responded with 400 not 201 /sbbs/exec/letsyncrypt.js executed in 1.54 seconds
!Module (letsyncrypt) set exit_code: 1
JavaScript: Destroying context
JavaScript: Destroying runtime
I have SBBS running on Port 80/443
My letsyncrpt.ini:
Host = acme-v02.api.letsencrypt.org
Directory = /directory
TOSAgreed = true
GroupReadableKeyFile = false
[Domains]
alleycat.synchro.net=/sbbs/web/root
[key_id]
acme-v02.api.letsencrypt.org=https://acme- v02.api.letsencrypt.org/acme/acct/51915535
[State]
Woohoo, I finally got it working, on my Linuxbox, anyway, my windowsbox
runs sbbs WE ON 81/4443 but my test SBBS is running on 80/443.
1) shutdown the BBS
2) deleted the letsyncrypt.key and sll.cert files.
3) restarted sbsb
4) Deleted the entries in letsyncrypt.ini [Key_id] and [State]
5) re-ran jsexec letsyncrypt.js --force
... though it was showing as TLS error same as before it actually completed the script and created /sbbs/web/root/.well_known/acme-challenge and letsyncrypt.key, now when I connet via https it gives a secure connection!
I know the wiki says "Do not modify the [Key_id] and [State] sections, but the letsyncrypt.ini file I grabbed a while ago had the [Key_id] already filled in ...
please consider adding a note that if the [Key_id] and
[State] is defined it will Error 400 JWS.
Woohoo, I finally got it working, on my Linuxbox, anyway, my windowsbox
runs sbbs WE ON 81/4443 but my test SBBS is running on 80/443.
1) shutdown the BBS
2) deleted the letsyncrypt.key and sll.cert files.
3) restarted sbsb
4) Deleted the entries in letsyncrypt.ini [Key_id] and [State]
5) re-ran jsexec letsyncrypt.js --force
... though it was showing as TLS error same as before it actually completed the script and created /sbbs/web/root/.well_known/acme-challenge and letsyncrypt.key, now when I connet via https it gives a secure connection!
I know the wiki says "Do not modify the [Key_id] and [State] sections, but the letsyncrypt.ini file I grabbed a while ago had the [Key_id] already filled in ... please consider adding a note that if the [Key_id] and
[State] is defined it will Error 400 JWS.
worksThere is no "workaround" required.
It only requires correct configuration.
You've been given MULTIPLE suggestions by MULTIPLE people, and
don't even bother responding that you received them, much less
tried them, and whether they worked or not. You don't even
I didn't reply because none of the suggestions worked. When something
I'll let everyone know it worked. I've followed everyone's instructions to the tee. My site is still insecure.
Woohoo, I finally got it working, on my Linuxbox, anyway, my windowsbox runs sbbs WE ON 81/4443 but my test SBBS is running on 80/443.
1) shutdown the BBS
2) deleted the letsyncrypt.key and sll.cert files.
3) restarted sbsb
4) Deleted the entries in letsyncrypt.ini [Key_id] and [State]
5) re-ran jsexec letsyncrypt.js --force
Re: Re: Letsencrypt work around?windowsbox
By: Mortifis to Digital Man on Sat Dec 14 2019 05:30 pm
Woohoo, I finally got it working, on my Linuxbox, anyway, my
runs sbbs WE ON 81/4443 but my test SBBS is running on 80/443.
1) shutdown the BBS
2) deleted the letsyncrypt.key and sll.cert files.
3) restarted sbsb
4) Deleted the entries in letsyncrypt.ini [Key_id] and [State]
5) re-ran jsexec letsyncrypt.js --force
Does this now show as a real signed cert, not self-signed? Something that the documentation doesn't make clear is whether you should end up with a CA-signed cert. Mine is still showing self-signed at the moment.
Re: Re: Letsencrypt work around?windowsbox
By: Mortifis to Digital Man on Sat Dec 14 2019 05:30 pm
Woohoo, I finally got it working, on my Linuxbox, anyway, my
thatruns sbbs WE ON 81/4443 but my test SBBS is running on 80/443.
1) shutdown the BBS
2) deleted the letsyncrypt.key and sll.cert files.
3) restarted sbsb
4) Deleted the entries in letsyncrypt.ini [Key_id] and [State]
5) re-ran jsexec letsyncrypt.js --force
Does this now show as a real signed cert, not self-signed? Something
the documentation doesn't make clear is whether you should end up witha
CA-signed cert. Mine is still showing self-signed at the moment.
Razor
That makes sense. I've figured out that my issue with not getting a cert that's signed by Let's Encrypt is likely related to my system not listening on port 80.
Here's the log that Let's Encrypt generated https://acme-v02.api.letsencrypt.org/acme/authz-v3/1823799891
It looks like it may be possible to tell the API to connect on an alternate port, possibly 9999 https://www.virtualmin.com/node/53385
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 412 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 22:36:47 |
| Calls: | 8,625 |
| Calls today: | 11 |
| Files: | 13,238 |
| Messages: | 5,936,886 |