Enabling HTTPS Connections

This guide will walk you through how to generate your own self-signed certificates for use by the Plugin node.
You will need OpenSSL in order to generate your own self-signed certificates.
You need a domain name for your Node IP address to enabe HTTPS Connections
Create a directory tls/ within your local Plugin directory:
mkdir Plugin/tls
Run this command to create a server.crt and server.key file in the previously created directory:
openssl req -x509 -out ~/Plugin/tls/server.crt -keyout ~/Plugin/tls/server.key \
-newkey rsa:2048 -nodes -sha256 -days 365 \
-subj '/CN=localhost' -extensions EXT -config <( \
printf "[dn]\nCN=localhost\n[req]\ndistinguished_name = dn\n[EXT]\nsubjectAltName=DNS:localhost\nkeyUsage=digitalSignature\nextendedKeyUsage=serverAuth")
Next, add the TLS_CERT_PATH and TLS_KEY_PATH environment variables to your .env file.
echo "TLS_CERT_PATH=/Plugin/tls/server.crt
TLS_KEY_PATH=/Plugin/tls/server.key" >> 2_nodeStartPM2.sh
If PLUGIN_TLS_PORT=0 is present in your 2_nodeStartPM2.sh file, remove it by running:
sed -i '/PLUGIN_TLS_PORT=0/d' 2_nodeStartPM2.sh
Also remove the line that disables SECURE_COOKIES by running:
code": "sed -i '/SECURE_COOKIES=false/d' 2_nodeStartPM2.sh
Finally, restart the PM2 using following command
pm2 restart 1
Now when running the node, you can access it by navigating to https://<localhost ore remoteip>:6689 if running on the same machine or with a ssh tunnel.