helomen Posted January 28, 2020 Share Posted January 28, 2020 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! Quote Link to comment
SimoneM1988 Posted March 26, 2021 Share Posted March 26, 2021 I’m facing the same problem, have you solved it? Quote Link to comment
jmztaylor Posted March 30, 2021 Share Posted March 30, 2021 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 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.