Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by THF13

  1. Not really sure if this is a better solution, but it is an alternative. Leave the local basic auth as is, and in your reverse proxy add the line proxy_set_header Authorization "Basic YWRtaW46cnV0b3JyZW50"; This will pass the default admin/rutorrent password along after you auth via the reverse proxy. Definitely do not do this if you do not have basic auth setup in your reverse proxy. If you are using a different username and password you'll need to convert your "user:password" to base 64. https://www.opinionatedgeek.com/codecs/base64encoder
  2. 4.0.3 isn't coming for docker/linux builds apparently, the fix will be in the next patch they hope to have out next week. In the meantime I'd recommend Emby users mount their shares as RO. Emby devs respond to just about everything posted on their official forums.
  3. Open /config/auth and add a second line with the following. <username>:<password>:10 Then use those credentials to connect from the thin client, obviously using the appropriate IP and Port to reach the container.
  4. -e VPN_ENABLED=yes Needs to be set, but I'm assuming you probably did that.
  5. I actually used to do just that, had a VM with deluge installed with my router configured to only allow that whole VM to connect to the internet through the VPN. I'm using my current UbuntuVM for more containers than just DelugeVPN, and honestly the way this container has the VPN rules set up and includes privoxy works better than what I did manually. Also Docker for Windows sets up its own VM in hyper-v to work anyways.
  6. I setup an Ubuntu VM using hyper-V. Mounted a windows share in the VM and used that for the /data directory.
  7. I'd prefer to have this container accessible through my linuxserver/letsencrypt reverse proxy, has anyone got that working well and can post their config? I've been trying it with various options and haven't gotten it quite right. When I refresh the page it seems almost random what happens, sometimes it loads correctly, sometimes it times out, sometimes it takes a long time to load, sometimes it loads some of the interface but with an error. Seems similar to an issue kostecki was having but that was back in August and I didn't see any response to it. Reverse proxy on same local network as rtorrentvpn, using a subdomain, rtorrentvpn loads correctly when going directly to IP:9080, other sites using reverse proxy working normally. EDIT: Think I've got it working, will edit post again if I find an issue after a couple days of testing. Commented out authorization in the rtorrentvpn container by editing nginx.conf Used the below server and location block on the reverse proxy container. #RTorrentVPN server { listen 443 ssl http2; #root /config/www; #index index.html index.htm index.php; server_name rvpn.domain.com; include /config/nginx/ssl.conf; client_max_body_size 0; location / { proxy_pass_header Authorization; proxy_pass http://192.168.1.XXX:9080; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_http_version 1.1; proxy_set_header Connection ""; proxy_buffering off; proxy_request_buffering off; client_max_body_size 0; proxy_read_timeout 36000s; proxy_redirect off; proxy_ssl_session_reuse off; auth_basic "Restricted Content"; auth_basic_user_file /config/nginx/.htpasswd; } }