Instead of running SSL natively on Synchronet, would anything break by just running http internally and using NPM to manage certificates and
then pass on HTTPS traffic to HTTP internally?
I have Letsyncrypt running on my BBS, with several subdomains off of realitycheckbbs.org. I've got other systems using Lets Encrypt.
I used to have to change my router NAT entries to point 80 to each system that I manually renewed the certificate on.
I set up Nginx Proxy Manager and have it proxying for my internal hosts. It can register certs for my internal hosts.
Instead of running SSL natively on Synchronet, would anything break by just running http internally and using NPM to manage certificates and then pass on HTTPS traffic to HTTP internally?
I set up Nginx Proxy Manager and have it proxying for my internal hosts. It can register certs for my internal hosts.
Instead of running SSL natively on Synchronet, would anything break by just running http internally and using NPM to manage certificates and then pass on HTTPS traffic to HTTP internally?
echicken wrote to poindexter FORTRAN <=-
IMHO nginx configs are quite easy to manage by hand on a small scale
like you'd typically find in BBS-land. I suspect you'd be doing
yourself a favour by just taking NPM out of the mix and using nginx on
its own. I can share my settings with you if you like.
Thanks for the offer, I'd love to see your setup. I use nginx at work both as a web server and proxy, so I know my way around nginx pretty well. I'm
mostly using NPM because I liked the front-end and it came in a container :)
Sysop: | Ruben Figueroa |
---|---|
Location: | Mesquite, Tx |
Users: | 3 |
Nodes: | 4 (0 / 4) |
Uptime: | 82:36:55 |
Calls: | 77 |
Files: | 53 |
Messages: | 72,762 |