Everything posted by strike
-
[Support] binhex - qBittorrentVPN
You should change your PIA password asap, as you forgot to remove it from the log. Which IP and port are you trying to reach the webui on?
-
[Support] binhex - DelugeVPN
You should change your vpn password asap, as you forgot to remove it from the log. Then you can see Q17: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
-
[Support] binhex - DelugeVPN
NP, Glad we could get it working :)
-
[Support] binhex - DelugeVPN
Nice! It should be off. This is the subnet for the tailscale network, which is essentially the same as adding your local subnet 10.10.0.0/24 or 192.168.68.0/24, but for tailscale. I don't know what Tailscale IP you added before, but that looks like it's only for one IP, and not the entire subnet as it should be.
-
[Support] binhex - DelugeVPN
Ok, also add this to the LAN_NETWORK 100.64.0.0/10 Which IP are you trying to access the web UI on? Try accessing it with the servers tailscale ip:port. http://100.x.x.x:8112 Leaving the network as bridge, at least until you can access the webui. Do you have accept routes or accept dns enabled in your server's Tailscale settings?
-
[Support] binhex - DelugeVPN
Is tailscale installed in the container or are you accessing it through tailscale subnet router? Can you add 192.168.68.0/24 to the LAN_NETWORK variable in the template as well and try again.
-
[Support] binhex - DelugeVPN
Ok, You mentioned that you're accessing this from a remote computer. What is the local IP of that computer?
-
[Support] binhex - DelugeVPN
You should change your PIA password asap, as you forgot to remove it from the docker run command. If you change your network to bridge instead of docknet, can you access the webui then?
-
[Support] binhex - DelugeVPN
Yeah, this image has been rock steady for me for many years. I recently moved to qbittorrent tho.
-
[Support] binhex - DelugeVPN
You posted the container log again. You should post the docker run command. Click the link if you need help on how to get it. :)
-
[Support] binhex - DelugeVPN
Please post your docker run command as well.
-
[Support] binhex - DelugeVPN
What issues are you having? You can usually ignore the pkg_resources warning. Need a full log, please do this: https://github.com/binhex/documentation/blob/master/docker/faq/help.md
-
[Support] binhex - DelugeVPN
I can't see any reason you shouldn't be able to access the webui. You're using this ip and port right? 192.168.1.24:8112. It seems you have set everything correctly, so it should work. It might be something with port forwarding, but I'm not a protonvpn user, so I have no clue about that. You can try to post an issue on github. Since this is an unRAID-specific support thread, you might get more help relevant to your OS there.
-
[Support] binhex - DelugeVPN
The log looks better now. And by what network type you use, I meant what docker network type are you using? Host/bridge or custom network. You should be using bridge. Have you done this part?
-
[Support] binhex - DelugeVPN
This message is not coming from delugevpn I don't think. What are you using to manage your containers? If you disable the vpn, can you get to the webui? What network type do you use and what is the IP of the computer you're trying to access deluge webui? Edit: This here from your log is an issue tho, the vpn is not going to work correctly if iptables is not working. Have you checked your permissions? delugevpn | modprobe: FATAL: Module ip6_tables not found in directory /lib/modules/6.18.9 delugevpn | ip6tables v1.8.11 (legacy): can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?) delugevpn | Perhaps ip6tables or your kernel needs to be upgraded.
-
[Support] binhex - qBittorrentVPN
Download a new .ovpn file from your vpn provider and try again.
-
[Support] binhex - DelugeVPN
I can't see any other errors in the log besides the TLS handshake error. This can usually be solved by downloading a new .ovpn file from your vpn provider. I tried to ping the most recent server you connected to in your log, and it confirmed it's down.
-
[Support] binhex - DelugeVPN
Need a full log, please do this: https://github.com/binhex/documentation/blob/master/docker/faq/help.md
-
Private Internet Access & Tailscale
Try to disable "use tailscale dns" on your tailscale client on the phone. That should make it faster.
-
[Support] binhex - General
If you go to the template and toggle advanced view, do you have a specific tag set here: If you do, just set it to :latest instead of the tag and apply. You might have to check for updates again to get the latest version.
-
[Support] binhex - DelugeVPN
You don't need to set up proxy, the reason I asked is because if enabled it can cause connection issues if not set properly. Please post a new log, remember to redact user/pw
-
Tailscale "Serve" question
No, if you want it publicly accessible you have to use tailscale funnel.
-
[Support] binhex - DelugeVPN
But why are you messing with input/output ports then? That should only be used if the containers are behind the delugevpn container. Have you enabled host access to custom networks in settings-Docker? Do you have proxy enabled in sonarr/radarr? Please post a new log as well.
-
[Support] binhex - DelugeVPN
First, change your vpn password (and user if you can), as you forgot to redact them from the log. Second, set STRICT_PORT_FORWARD to no. And thrid, see Q17: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
-
[Support] binhex - DelugeVPN
Last update to this image was 11 months ago, so no recent updates.. The reason why it doesn't work when VPN is enabled and works when it is disabled is because of the strict ip tables rules in place. If the VPN is enabled all settings like Lan network, input/output ports needs to be correct. If it's not it will not work. And like mentioned, in your log, it's was not correct. I'm telling you what needs to be set for it to work and you keep ignoring it. Or at least you haven't said you have set the correct Lan network, yet. One thing I remember now tho, you have this container on a fixed IP I think? That can sometimes work and sometimes it does not. Post your setting for deluge in sonarr/radarr.