Easy to configure SSL Server that can be used for development or production

HTTP requests are redirected to HTTPS

Production servers can use and renew Lets Encrypt 90 Day Certificates automatically.

Designed to get out of your way, you can still change anything about the server.

The easiest usage would be to serve a website:

1. Clone or Download the main branch and extract it somewhere
2. Put your website in the website folder
3. Open the server-ssl folder in Command Prompt or Git Bash
4. Run start-windows.bat
5. View your website at https://localhost

start-windows.bat takes your arguments and starts the server

# Start for production (Lets Encrypt!) with SAN Extension
./start-windows.bat --letsEncrypt --domains=['www.ssl.boats','ssl.boats']

# Start for production (BYO)
./start-windows.bat --cert="your-certificate.pem" --pk="your-private-key.pem"

server-ssl.js has some optional arguments you can use in production if the defaults aren't enough.

All Arguments are case sensitive.

You can use Lets Encrypt to generate certificates.

Certificates are valid for 90 days but are renewed automatically sooner.

The certificates will be changed automatically when they are updated, you don't need to do anything.

start-windows.bat is required to use --autoRestart

./start-windows.bat --letsEncrypt --domains=['www.ssl.boats','ssl.boats']

At the end of the day, this is just a Node.js server that sets up SSL automatically

const HTTPS_SERVER = createServerHTTPS(S_SSL.loadDefaultSecureContext(), (req, res) => {
    // do whatever you like
}).on('error', (e) => e.code === S_SSL.ADDR_IN_USE && console.error(`${S_SSL.optPort}${S_SSL.IN_USE}`)).listen(S_SSL.optPort, (err) => err ? console.error(S_SSL.ERROR_STARTING, err) : console.log(`${S_SSL.STARTED_HTTPS}${S_SSL.optPort}`));

You can remove everything inside HTTPS_SERVER and do whatever you like.

There are also helpers you can use in S_SSL

This structure is designed to keep the project organized and maintainable, separating error handling, website content, and server configuration.

/root
│
├── /error
│   ├── 404.html
│   └── 500.html
│
├── /ssl
│   ├── /openssl
│   ├── /module
│   │   ├── /crypt
│   │   ├── /jose
│   │   └── lets-encrypt-acme-client.js
│   │
│   ├── acmeKeys
│   ├── private-key.pem
│   └── certificate.pem
│   └── ssl.js
│
├── /website
│   └── index.html <---- Your website goes here
│
├── node.exe
├── server-ssl.js            <--- server config
└── start-windows.bat

The server is configured to serve custom 404 and 500 error pages, instead of plain-text.

Currently everything is treated like a Server Error except for Not Found

These pages will automatically select light/dark mode

./start-windows.bat --cert="your-certificate.pem" --pk="your-private-key.pem"
node server-ssl.js --cert="your-certificate.pem" --pk="your-private-key.pem"

start-windows.bat will automatically create a Certificate and Private Key when you run it if you don't provide any and none exist

When you run start-windows.bat the first time the latest version of node.exe portable will be downloaded