After installing Letsencrypt I get the "Congradulations you have succefully installed certificate" blah blah blah. However when I navigate Chrome to https://havens.synchronetbbs.org I get this:
This certificate has been verified for the following usages:
Issued To
Common Name (CN) havens.synchronetbbs.org
Organization (O) Havens BBS
Organizational (OU) <Not Part of Certificate>
Issued By
Common Name (CN) havens.synchronetbbs.org
Organization (O) Havens BBS
Organizational (OU) <Not Part Of Certificate>
Validity Period
Issued On Monday, November 4, 2019 at 8:30:57 PM
Expires On Saturday, December 15, 2035 at 7:00:00 PM
Fingerprints
SHA-256 Fingerprint CB AC A4 D0 60 42 62 2B F1 25 B6 F3 05 E8 AB F9
A3 01 27 56 C2 7F 67 65 58 37 EA 16 92 C8 1D D1
SHA-1 Fingerprint 45 0A D4 5A 6A EB CB 52 4B 31 26 4B EB C6 37 87
A2 38 AC 4D
Re: Letencrypt
By: HusTler to All on Mon Dec 09 2019 05:48 pm
If I use firefox I get this:
Warning: Potential Security Risk Ahead
Firefox detected a potential security threat and did not continue to havens.synchronetbbs.org. If you visit this site, attackers could try to steal information like your passwords, emails, or credit card details.
Learn more...
H A V E N S B B S havens.synchro.net:23
---
¨ Synchronet ¨ Havens BBS havens.synchro.net
After installing Letsencrypt I get the "Congradulations you have succefully installed certificate" blah blah blah. However when Inavigate
Chrome to https://havens.synchronetbbs.org I get this:F9
This certificate has been verified for the following usages:
Issued To
Common Name (CN) havens.synchronetbbs.org
Organization (O) Havens BBS
Organizational (OU) <Not Part of Certificate>
Issued By
Common Name (CN) havens.synchronetbbs.org
Organization (O) Havens BBS
Organizational (OU) <Not Part Of Certificate>
Validity Period
Issued On Monday, November 4, 2019 at 8:30:57 PM
Expires On Saturday, December 15, 2035 at 7:00:00 PM
Fingerprints
SHA-256 Fingerprint CB AC A4 D0 60 42 62 2B F1 25 B6 F3 05 E8 AB
A3 01 27 56 C2 7F 67 65 58 37 EA 16 92 C8 1D D187
SHA-1 Fingerprint 45 0A D4 5A 6A EB CB 52 4B 31 26 4B EB C6 37
A2 38 AC 4D
Now what?
If I use firefox I get this:
havens.synchronetbbs.org uses an invalid security certificate.
The certificate is not trusted because it is self-signed.
Common Name (CN) havens.synchronetbbs.org
Organization (O) Havens BBS
Organizational (OU) <Not Part Of Certificate>
Validity Period
Issued On Monday, November 4, 2019 at 8:30:57 PM
Expires On Saturday, December 15, 2035 at 7:00:00 PM
FingerprintsF9
SHA-256 Fingerprint CB AC A4 D0 60 42 62 2B F1 25 B6 F3 05 E8 AB
A3 01 27 56 C2 7F 67 65 58 37 EA 16 92 C8 1D D187
SHA-1 Fingerprint 45 0A D4 5A 6A EB CB 52 4B 31 26 4B EB C6 37
A2 38 AC 4D
Now what?
That is the creds from ssl.cert created by SBBS, I am not sure how you
get the creds to point to the letsyncrypt.key
I'm at a loss here. Other then the letsencrypt.org and letsycrypt module documentation are there any other trouble shooting pages?
Try deleting or renaming your ctrl/ssl.cert file (this one appears to be self-signed, *not* signed by LetsEncrypt) and then re-run theletsyncrypt.js
script, it should recreate the ssl.cert file, this time signed by LetsEncrypt.
Re: Re: Letencrypt
By: Digital Man to HusTler on Tue Dec 10 2019 09:14 am
Try deleting or renaming your ctrl/ssl.cert file (this one appears to be self-signed, *not* signed by LetsEncrypt) and then re-run the letsyncrypt.js script, it should recreate the ssl.cert file, this time signed by LetsEncrypt.
Here's a copy of my letsyncrypt.ini is this correct? if it's correct I run jsexec letsyncrypt.js new-key ????
; $Id: letsyncrypt.ini,v 1.1 2019/07/24 22:32:54 rswindell Exp $
; For use with exec/letsyncrypt.js
; See http://wiki.synchro.net/module:letsyncrypt for details
Host = acme-v02.api.letsencrypt.org
Directory = /directory
TOSAgreed = true
GroupReadableKeyFile = false
[Domains]
havens.synchronetbbs.org = /sbbs/web/root
havens.synchro.net = /sbbs/web/root
The TOSAgreed variable is in two places. It's in the .ini and in the .js.I had a problem with it
when I ran it initially and then I took a step back and reviewed the twofiles involved in the
process and found that in the .js file, the variable is set to false. Ichanged it to true, re-ran
it and it worked fine.
Editing the script is not necessary. There was a problem with your INIfile.
TOSAgreed *defaults* to false in the script. It only remains false if thescript can't read your INI file, if TOSAgreed
is set to false in your INI file, or if TOSAgreed is missing from yourINI file.
(Or perhaps you were using some older version of the script with a bug.)
The TOSAgreed variable is in two places. It's in the .ini and in the .js..js
I had a problem with it when I ran it initially and then I took a step back and reviewed the two files involved in the process and found that in the
file, the variable is set to false. I changed it to true, re-ran it and it
The TOSAgreed variable is in two places. It's in the .ini and in the .js.I had a problem with it when I ran it initially and then I took a step back and reviewed the two files involved in the process and found that in
the .js file, the variable is set to false. I changed it to true, re-ranit and it worked fine.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 412 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 03:04:25 |
| Calls: | 8,637 |
| Files: | 13,238 |
| Messages: | 5,936,917 |