Use my own SSL-Certificates and not Let's Encrypt?

[hspies91]

Hey Guys,

i installed Wiki JS following this Article:

https://docs.requarks.io/install/ubuntu and started to use the wiki for my own internal stuff.
Now, i wanted to use https and publish the Server BUT i can not use LE for several reasons (no forwarding of Port 80 etc.).
How can i now use HTTPS and pass my Cert & Key File in this Line?

docker create --name=wiki -e "HERE NOT LE, I WANT TO PASS MY OWN CERTIFICATES" -e SSL_ACTIVE=1 -e DB_TYPE=postgres -e DB_HOST=db -e DB_PORT=5432 -e DB_PASS_FILE=/etc/wiki/.db-secret -v /etc/wiki/.db-secret:/etc/wiki/.db-secret:ro -e DB_USER=wiki -e DB_NAME=wiki -e UPGRADE_COMPANION=1 --restart=unless-stopped -h wiki --network=wikinet -p 80:3000 -p 443:3443 ghcr.io/requarks/wiki:2

Is this possible?
Best Regards, :)

[eglyn]

I up this thread, as I have the same question :)
I find some variables in the request section: SSL_PEM_CERT_FILEPATH and SSL_PEM_KEY_FILEPATH, but it does not work. It seems wiki looks always for a letsencrypt email, thx !

docker create --name=wiki -e SSL_PROVIDER=CUSTOM -e SSL_PEM_CERT_FILEPATH=/opt/ssl/domain.cert.pem -e SSL_PEM_KEY_FILEPATH=/opt/ssl/domain.key.pem -e SSL_ACTIVE=1 -e DB_TYPE=postgres -e DB_HOST=db -e DB_PORT=5432 -e DB_PASS_FILE=/etc/wiki/.db-secret -v /etc/wiki/.db-secret:/etc/wiki/.db-secret:ro -e DB_USER=wiki -e DB_NAME=wiki -e UPGRADE_COMPANION=1 --restart=unless-stopped -h wiki --network=wikinet -p 80:3000 -p 443:3443 ghcr.io/requarks/wiki:2

[eglyn]

Ok, i answer on my own question :D I use a apache proxy, and it works great, my conf:

• wiki only on port 3000 http
  docker create --name=wiki -e DB_TYPE=postgres -e DB_HOST=db -e DB_PORT=5432 -e DB_PASS_FILE=/etc/wiki/.db-secret -v /etc/wiki/.db-secret:/etc/wiki/.db-secret:ro -e DB_USER=wiki -e DB_NAME=wiki -e UPGRADE_COMPANION=1 --restart=unless-stopped -h wiki --network=wikinet -p 3000:3000 ghcr.io/requarks/wiki:2

• install apache
  apt install apache2
a2enmod ssl rewrite headers proxy proxy_http

• config apache:

<VirtualHost *:80>
        ServerName myserver.mydomain.com
        RewriteEngine On
        RewriteRule ^(.*)$ https://%{HTTP_HOST}$1 [redirect=301]


</VirtualHost>

<IfModule mod_ssl.c>
        <VirtualHost *:443>
                ServerName myserver.mydomain.com
                # Use HTTP Strict Transport Security to force client to use secure connections only.
                Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
                # Referer logging is used to allow websites and web servers to identify where people are visiting them from, for promotional or statistical purposes.
                Header always set Referrer-Policy "no-referrer"

                SSLCertificateFile /opt/ssl/myserver.mydomain.com.cer
                SSLCertificateKeyFile /opt/ssl/myserver.mydomain.com.fr.key

                SSLEngine on
                SSLProtocol all -TLSv1 -TLSv1.1 -SSLv2 -SSLv3
                SSLHonorCipherOrder on
                SSLCompression off
                SSLOptions +StrictRequire
                SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA>

                ProxyPreserveHost On
                ProxyPass / http://localhost:3000/
                ProxyPassReverse / http://localhost:3000/
        </VirtualHost>
</IfModule>

[riversdev0]

For anyone else who ends up here (like I did), there is a mention under the HTTPS header on the installation page for software version 2 that says this:

If you want to provide your own SSL certificate configuration, you must instead mount a config file as explained below.

There is a sample config.yml available on GitHub.

So, I removed all my environment variables from my Docker command, created a config.yml on my Docker host instead, and then mapped my config.yml into the container in the /wiki folder, by adding this to my Docker command:

-v /home/user/wiki.js/config.yml:/etc/config.yml

And now it works!