January 28, 20206 yr I try to configure cops with the reverse proxy. The reverse proxy with letsencrypt works fine for me so far (e.g. sonarr, radarr, calibre,... are working perfectly). Unfortunately I can't write the "proxy-conf" for cops correctly. I tried the following: 1. I installed cops with the Host Port 1: 9082 (Container Port: 80) 1. I have created a conf-file \appdata\letsencrypt\nginx\proxy-confs and named it cops.subdomain.conf 2. This is how it looks like: server { listen 443 ssl; listen [::]:443 ssl; server_name cops.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_cops cops; proxy_pass http://$upstream_cops:9082; proxy_set_header Range $http_range; proxy_set_header If-Range $http_if_range; } location ~ (/cops)?/socket { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_cops cops; proxy_pass http://$upstream_cops:9082; # replace this with IP address and port of Cops proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; } } My subdomain starts with cops.xxxxxxxxxxxxxxxxxxx, so the server_name should be right. I'm not sure if there is an issue with the proxy_pass. Any ideas? Thx for your help!
March 30, 20215 yr I've never messed with using container name in the swag config without being on shared network. I would see if changing $upstream_cops cops to $upstream_cops localhost will work.Or try your server IP instead of localhost
Archived
This topic is now archived and is closed to further replies.