Hi Community!
Amongst other tools installed on my physical server (Debian 9 + Virtualmin), I’ve created a virtual server for our wiki (tikiwiki, php application), which is, as all others, protected by a Let’s Encrypt certificate which provides for https connection. So far so good.
I’ve tried last week to switch the wiki engine to another one (wiki.js, java app):
- installed node.js on the server = OK
- backed the whole wiki virtual server up = OK
- deleted all files in wiki/www folder (except .htaccess) = OK
- unpacked wiki.js = OK
- ran
node wiki
as a service = OK - go to http://wiki.mydomain.com = OK (new wiki looks way better than the old one )
- go to https://wiki.mydomain.com = HTTP 403!
Hence my questions:
- is there any reason the certificate located in /wiki couldn’t be used for the new wiki?
- is there anything which I should fix in the .htaccess file (not very familiar with it but I think this .htaccess is largely tikiwiki-oriented)?
- should I change anything in the virtual server configuration as I’m now running a java app instead of a php one (Apache conf file)?
Note: the config.yml file for wiki.js includes the following section, which should obviously be edited.
ssl:
enabled: false (--> turned to TRUE)
# Certificate format, either 'pem' or 'pfx': (what is the format of the certificates installed by Virtualmin?)
format: pem (--> doesn't match the Let'sEncrypt ssl.cert / ssl.key format?)
# Using PEM format:
key: path/to/key.pem
cert: path/to/cert.pem
# Using PFX format:
pfx: path/to/cert.pfx
# Passphrase when using encrypted PEM / PFX keys (default: null):
passphrase: null (Virtualmin-defined, so I have no access to this, if required)
# Diffie Hellman parameters, with key length being greater or equal
# to 1024 bits (default: null):
dhparam: null
# Listen on this HTTP port and redirect all requests to HTTPS.
# Set to false to disable (default: 80):
redirectNonSSLPort: 80
Thanks in advance for any help!