Add Feature: Support for HTTPS (TLS/SSL)

When setting the ROOT_URL to https, restarting Wekan and try to access wekan via browser and the https-URL i just get:

ERR_CONNECTION_CLOSED

Tested with Wekan v.0.13, v.0.12, v.0.10.1 Manual installation on CentOS

[xet7]

Does somebody use only Node.js in production?

In all articles I found with Google search, Nginx/Caddy/some other webserver is used for load balancing and delivering static content in front of Node.js.

[iAdanos]

@NoodleBB, did you set up HTTPS in webserver config correctly? You should attach your webserver config here.

If you trying to start “stock” wekan in HTTPS mode (doesn’t matter docker instance or compiled from source), it will not work, because wekan needs webserver proxying it with SSL.

Offtop: IMHO, SSL is not the function Wekan itself must provide. It’s an app. Commutity must be concentrated on functions and stability of the primary service. I beleve, we want make a lightweight, fast and cool service. Making a monster with integrated webserver, DB etc. functions will kill the idea.