Embed Notice

@pere@micro.towards.vision Thanks a lot! Also, please don't worry if you can't reply immediately! I know you are working on amazing stuff :meow_heart_hug:
Currently, I've managed to run Vervis locally (just an FYI, I had to install pkg-config and libcurl4-openssl-dev, which I think isn't mentioned in INSTALL.md, but that was not a big deal), but I have trouble with deploying it on my server; I can't access it on https://instance.tld (image #1), and I have to type http://instance.tld:3000 instead (image #2).
It may be more of a web server management thing than something specific to Vervis (honestly, I'm a newbie in server management), so I'm sorry if this is due to my misconfiguration.
I'm currently using nginx to forward ports, but it's okay to switch to other methods, so please tell me if you recommend any other way.

I have /etc/nginx/sites-available/vervis like this (please check this on remote if the code block is hard to see on Mastodon)upstream vervis { server 127.0.0.1:3000 max_fails=5 fail_timeout=60s; } server { server_name code.naskya.net; listen 80; listen [::]:80; listen 443 ssl http2; listen [::]:443 ssl http2; ssl_certificate /path/to/cert ssl_certificate_key /path/to/cert_key proxy_http_version 1.1; proxy_set_header Host $http_host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; location / { proxy_pass http://vervis; } }
and config/settings.yml like this:host: "_env:HOST:*4" http-port: "_env:PORT:3000" ip-from-header: "_env:IP_FROM_HEADER:false" instance-host: "_env:INSTANCE_HOST:code.naskya.net" # and so on...
Big thanks in advance.