scb147

This makes sense as to why qbittorrent was working with swag. I checked docker to see what drivers each network was using. And the network driver that was created for swag (based on the spaceinvader video) is using the bridge driver, but the network the NPM container created uses the macvlan driver. I'm not sure why the NPM container creates one with macvlan, but that is for a discussion in that container thread. I moved the qbittorent (and NPM) container over to a bridge driver network, and things work as expected. Thanks for the help!

I've been still struggling with this, I even attempted to use the binhex-deluge container, same issue. If I use the "Bridge" network, deluge/qbittorrent webui both work both connecting locally with the VPN enabled. If I use the custom br0 network (created by the Nginx Proxy Manager container), I can only connect to the webui locally when I am not connected to the VPN. My assumption is it has to do with the LAN_NETWORK configuration, but it already is set to 192.168.1.0/24. My deluge/qbittorrent containers are statically assigned 192.168.1.5 with the br0 network. I am not getting an instant error message from the browser when attempting to load the webui, it times out.

I am in the process of switching over to Nginx Proxy Manager, and I have gotten all of my other containers to work with it. However, I cannot gain access to the qBittorrent webui when I have the VPN enabled, this is even when I am using the local IP/port number for the container. I saw recent posts about VPN issues, so I made sure I had the latest opvn file from my VPN provider. supervisord.log.zip

I am using a domain name, as I already had one. So I set up swag with qbittorrent, sonarr and radarr with no issues using those containers. I am trying to get sabnzbd working, but I can't seem to access it using the subdomain (works fine if I use local IP and port). The browser is not giving an error message, just a blank white screen with the favicon in the tab. The only entry in the nginx log for the subdomain is: [04/Oct/2023:09:50:11 -0400] "GET /favicon.ico HTTP/2.0" 200 5430 "https://nzb.mydomain.com/" "Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/118.0" I did remove the url_base setting from the sabnzbd config. I also added the subdomains to the host_whitelist setting to the sabnzbd config as mentioned in the sabnzbd.subdomain.conf file from nginx. This is my sabnzbd.subdomain.conf file: ## Version 2023/05/31 # make sure that your sabnzbd container is named sabnzbd # make sure that your dns has a cname set for sabnzbd # edit the sabnzbd.ini host_whitelist to avoid hostname verification issues. This format: # host_whitelist = sabnzbd.domain.com, www.sabnzbd.domain.com server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name nzb.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth (requires ldap-location.conf in the location block) #include /config/nginx/ldap-server.conf; # enable for Authelia (requires authelia-location.conf in the location block) #include /config/nginx/authelia-server.conf; # enable for Authentik (requires authentik-location.conf in the location block) #include /config/nginx/authentik-server.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable for ldap auth (requires ldap-server.conf in the server block) #include /config/nginx/ldap-location.conf; # enable for Authelia (requires authelia-server.conf in the server block) #include /config/nginx/authelia-location.conf; # enable for Authentik (requires authentik-server.conf in the server block) #include /config/nginx/authentik-location.conf; include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app sabnzbd; set $upstream_port 8080; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } location ~ (/sabnzbd)?/api { include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app sabnzbd; set $upstream_port 8080; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } } The sabnzbd container in UnRAID is using 6060 (but in the sabnzbd config, it is still using 8080), as the qBittorrent container is using 8080. I tried changing the "set $upstream_port" entry to 6060, and I see the "Bad Gateway" message from nginx. Any suggestions on what might be wrong? EDIT: After messing around with this for most of the day, I noticed that if I attempt to load via my subdomain, I get this message in the nginx access.log: [04/Oct/2023:14:02:56 -0400] "GET / HTTP/2.0" 403 0 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/118.0" The http_referrer is "-". Does this mean the CNAME entry for my domain is not sending the subdomain? All my CNAME entries are the same, so I'm not sure why this one is working differently than the others.

OK, setting UnRAID SSL to No fixed it. Thanks!

I'm not accessing UnRAID via SSL. But it looks like ControlR is accessing via SSL, but I don't see any settings on the ControlR page to disable SSL, just a text entry for the location of the certificates. So when I select the link to open the Web UI, it navigates to: https://<IP_ADDRESS>:2379/#/ The port in ControlR settings is 2378. Cert dir is the default: /boot/config/ssl/certs

This is my list of dockers: PlexMediaServer, Sabnzbd, Sonarr, Radarr, Lidarr, qBittorrentvpn, CrashPlanPRO, Google-MusicManager, Speedtest (disabled) I'm not sure if any of these have a reverse proxy associated with them.

I'm having this same issue. What can I do to get this working? UnRAID 6.7.0 and ControlR v2019.03.28.

I figured it out. I believe my problem was that the WEBUI_PORT and WEBUI_PORT_ENV didn't match. One was 8080 and the other was 8081. I could have sworn I didn't touch those, so I'm not sure how that happened. And I was able to get everything working with the VPN too, so that is a plus. One thing I'm just not sure of is that I changed my WEBUI ports to 6060, but I couldn't change the Connector Port from the Edit menu. I had to delete the port config and readd it. Is this typical, or is there a setting that I'm missing somewhere?

So, I just installed qBittorrentvpn, but I can't access the WebUI. I've turned the VPN off and updated the LAN_NETWORK variable, which I set to 192.168.1.0/24 (UnRAID is on 192.168.1.11). Everything else is default. I cannot access the WebUI. I'm looking for any suggestions. This is my qBittorrent.log file: (N) 2018-10-12T04:28:17 - qBittorrent v4.1.3 started (I) 2018-10-12T04:28:17 - qBittorrent is trying to listen on any interface port: 8999 (N) 2018-10-12T04:28:17 - Peer ID: -qB4130- (N) 2018-10-12T04:28:17 - HTTP User-Agent is 'qBittorrent/4.1.3' (I) 2018-10-12T04:28:17 - DHT support [ON] (I) 2018-10-12T04:28:17 - Local Peer Discovery support [ON] (I) 2018-10-12T04:28:17 - PeX support [ON] (I) 2018-10-12T04:28:17 - Anonymous mode [OFF] (I) 2018-10-12T04:28:17 - Encryption support [ON] (I) 2018-10-12T04:28:17 - Embedded Tracker [OFF] (I) 2018-10-12T04:28:17 - GeoIP database loaded. Type: GeoLite2-Country. Build time: Tue Oct 9 21:56:23 2018. (N) 2018-10-12T04:28:17 - Web UI: Now listening on IP: *, port: 8080 (I) 2018-10-12T04:28:17 - qBittorrent is successfully listening on interface :: port: TCP/8999 (I) 2018-10-12T04:28:17 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/8999 (I) 2018-10-12T04:28:17 - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/8999 (I) 2018-10-12T04:28:17 - External IP: XXX.XXX.XXX.XXX