one of the possible workaround - is to wrap wekan with apache and do smoething like that:


<VirtualHost *:443>

        SSLEngine on
        SSLCertificateFile /etc/apache2/ssl/some.cert
        SSLCertificateKeyFile /etc/apache2/ssl/some.key

        ServerName servername
        ServerAdmin webmaster@mytodo.org

        DocumentRoot /var/www/wekan.site.com
        <Directory />
                Options FollowSymLinks
                AllowOverride AuthConfig FileInfo Indexes Options=MultiViews
        </Directory>

        <Directory /var/www/wekan.site.com>
                Options -Indexes +FollowSymLinks +MultiViews
                AllowOverride AuthConfig FileInfo Indexes Options=MultiViews
                Require all granted
        </Directory>

        ErrorLog /var/log/apache2/wekan.site.com-error.log

        # Possible values include: debug, info, notice, warn, error, crit,
        # alert, emerg.
        LogLevel warn

        CustomLog /var/log/apache2/wekan.site.com-access.log combined
        ServerSignature Off

        ProxyPassMatch   "^/(sockjs\/.*\/websocket)$" "ws://127.0.0.1:8085/$1"
        ProxyPass        "/" "http://127.0.0.1:8085/"
        ProxyPassReverse "/" "http://127.0.0.1:8085/"

</VirtualHost>

where 8085 - is your local wekan's port

Don't know where ... but somewhere I saw such installation ..

Add Feature: Support for HTTPS (TLS/SSL) #916

Description

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions