-
[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.
-
[Support] binhex - DelugeVPN
I'll check your log after work to see if there's anything obvious. In the meantime check out the FAQ.
-
[Support] binhex - DelugeVPN
Aha, sorry then I misunderstood your first post. You still need to fix your Lan network tho. As mentioned all subnets that are going to access the webui must be defined in Lan networks, including the vlan subnet. And in the log from before it was not defined. Also make sure you don't use a proxy in the other containers. If it still doesn't work after doing that you should look at the faq. Theres a few things in there regarding using the VPN on other containers. I'm on my phone at work right now so I don't have the link.
-
Emby Server - Incorrect Permissions
Yeah, it looks better now.
-
[Support] binhex - DelugeVPN
That's exactly what I'm saying.. In your log from before, it says your LAN_NETWORK is defined as: 10.33.101.0/27 This is not correct if the computer your trying to access the webui from is x.x.12.0/27 Forget about sonarr,privoxy etc for now. First, fix deluge so you can get to the deluge webui. As I've said multiple times, ALL subnets you're accessing the web ui from need to be defined in LAN_NETWORK. So if the computer you're trying to get to the webui from is on x.x.12.0/27 you need to add that. Subnets are separated by commas. After doing this you still can't get to the deluge webui? What do you mean by this?
strike
Members
-
Joined
-
Last visited