I have tried applying the following configuration to my reverse proxy:
but to no avail
proxy_cache_bypass $http_upgrade;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $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_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Port $server_port;
I have tried again with both wan and domain in PEERTUBE_WEBSERVER_HOSTNAME
I have also been trying to use the provided nginx (800 and 4433 in my case) instead of whatever is running behind port 9000, but I cant even access it…
When trying to access http://wan:800, it says its not found. and when https://wan:4433, it says there is a certificate issue
Which then made me try cerbot, but I cannot get it to work
(I have the domain pointed to port 82 when that runs)
Sorry. I dont want to make the same mistake as in last topic; trying to cover too much ground. But I also dont want to leave out any information that could be relevant to my situation.
If I could understand how to make peertube work behind Nginx Proxy Manager that would be wonderful. I know it is not recommended to use in production whatever is running behind 9000; but it will be a single user peertube. So I dont worry about performance much; I dont need the provided nginx 800/4433.
Thanks!
Please let me know how can I improve my support request.
My goal is to have wan:9000 working under domain, behind Nginx proxy manager in https.
Regards,