I have no idea how I can tackle this SSL issue. Firstly, it's a production server that needs to run, means I am probably over careful.
I want to install isso (a comment system) as a docker container, as described here.
I have a subdomain (A record) in Cloudflare, pointing at my IP. There is no real website, so nothing for the subdomain in /var/www/
, means also nothing in /etc/nginx/sites-available/
. Only aisso.conf
in /etc/nginx/conf.d/
. That's a reverse proxy I guess.
So far it's pretty clear to me.
But how to handle the SSL issue? The guide I use uses certbot, that's an option, But will that interfere with --letsencrypt/ACME?
Would that work? >> wo site create isso.myproxy.com --proxy=127.0.0.1:8080 --letsencrypt
server {
listen 80;
listen [::]:80;
server_name isso.myproxy.com;
return 301 https://mwtarget.com$request_uri;
access_log /dev/null;
error_log /dev/null;
}
server {
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name isso.myProxy.com;
access_log /var/log/nginx/isso-access.log;
error_log /var/log/nginx/isso-error.log;
ssl_certificate /etc/letsencrypt/live/isso.myproxy.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/isso.myproxy.com/privkey.pem;
location / {
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass http://localhost:8080;
}
}