strike

I know, but the other containers where running through the binhex vpn container, thus making it a binhex vpn config issue. But glad the faq helped you out

Have you read the faq for the binhex vpn containers, specifically Q24? https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md If that doesn't solve your issue you should post in the appropriate support thread for the container. It has nothing to do with the unraid OS. To find the correct support thread right click the container and choose support.

Are you using rclone to mount your gdrive by any chance? If so, then rclone is most likeliy running as root and screwing up your permissions. Add this to your rclone mount script: --uid 99 --gid 99 Btw, you should have mentioned rclone and gdrive (if I'm right and your'e using that) in your posts as this is vital information and that's why nobody was able to help you. I'm only guessing here because your host path in your screenshot says mergerfs/gdrive...

You had it almost right in your last post. The port is wrong, should be 8118. So change the port and change the IP back to the 198.... IP

Do this: https://github.com/binhex/documentation/blob/master/docker/faq/help.md also post your docker run command in your next post

From your log: 022-04-03 10:00:34,126 DEBG 'start-script' stdout output: 2022-04-03 10:00:34 [UNDEF] Inactivity timeout (--ping-restart), restarting 2022-04-03 10:00:34,127 DEBG 'start-script' stdout output: 2022-04-03 10:00:34 SIGHUP[soft,ping-restart] received, process restarting See Q17: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

That looks good. Wrong volume mappings usually cause the symptoms you're seeing, but your mappings looks ok. So it's not that. Do you have free space in your Downloads folder? Can you write to it from inside the delugevpn container? Try to open a terminal in the container and do: fallocate -l 100M /data/completed/test.img That should write a test file in your completed folder. If it fails your have a permission issue.

Post your docker run command and a screenshot of your deluge downloads settings

Remove the port forwarding on your router, it's serves no purpose when you're using a vpn and is a security risk. Also request a different port from torguard and set that as the incoming port in deluge. Port 58846 is in use by the deluge deamon and I suspect that's why the active port is showing as 58847 which is the next port number in line.

Post your docker run command or a screenshot of your container template settings. Also post a screenshot of the downloads settings in deluge Edit: Be sure to redact your username/password

What IP are you trying to reach and what is your unraid IP? You can not use the unraid IP, but you have to use the IP you set up in zerotier. Edit: And have you authorized you device in zerotier?

Have you tried just rebooting? Do you by any chance have wireguard on unraid enabled and/or a VM running?

This usually happens when you run another docker container with the same port assignments. Check you docker tab to ensure that no other container is using the same ports. Or maybe the easier way is to click edit on the container, scroll down and click "show docker allocations". If there are multiple containers running on the same port they will be marked in red IIRC. If there are any containers using the same port, change ports on one of them. There will be no logs created for the container because the container fails to start. But you will see an error in your unraid syslog I think. There could be several other reasons why you get this error as well, so you will have to post your diagnostics in your next post if you want more help.

As I said you can not use openvpn becuse you can not port forward due to carrier grade NAT. And you're using openvpn wrong anyway. To reach your unraid machine with openvpn, you need a openvpn server on the unraid machine and a client on the machine you're connecting from. But as I said just forget about openvpn, you can not use it if you can not port forward on your router. use zerotier instead. You can use the openvpn server on your VPS as a router in a way so that clients can connect to each other but that is a advanced feature I think. If you want to try this google openvpn client-to-client. But I would just use zerotier instead and connect directly to your unraid machine instead of routing everything through a VPS, seems like too much trouble if you ask me.

Then you need to use something like ZeroTier, to use openvpn or wireguard you need to be able to port forward. But with something like zerotier you don't need that. There is a docker container for it.

Maybe check out Q2: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

OH, then you don't want to reverse proxy it with swag.. That's what's swag is for, making it open to the internet ,securely. But maybe you can copy the certs from swag to nextcloud, idk. You'll have to google it as I have no clue, but I THINK it can be done.

Just set up a subdomain. @SpaceInvaderOne has a video on how to set up nextcloud with swag: https://www.youtube.com/watch?v=I0lhZc25Sro

What is your network type? And what IP does your unraid box have?

See Q25 and maybe 27: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

No point in posting the log if everything is working. Maybe the vpn server you connected to had issues. You won't be able to see the webui before the vpn tunnel is up.

If I have to guess it's probably your LAN_NETWORK being wrong. See Q4: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md If you still can't get it to work do this: https://github.com/binhex/documentation/blob/master/docker/faq/help.md

When you read the faq to get the webui working it didn't occur to you to continue reading it? See Q27: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

That can be an option as well, but you better take that up with them as you said. Speed will vary across vpn servers as some have higher load than others, and this will constantly change. So to pick a server that is better than the other is just pure hit and miss and can change fast. But European servers tend to be faster when using p2p. That's my experience anyway. How will you know tho? When you switch vpn servers your connection will reset, and you might not even get connected to the same peers as before. In your settings you probably have only about 150 total connections or something set up. As in the example in my last post. Say you have a torrent with 500 seeders, and you're connected to 100 seeds and 50 leechers on this torrent. That's a total of 150 connections. Only 2 have an open incoming port of those, so you get 8MiB/s, which is the max those peers can upload. You switch vpn server and connect again to 100 seeds and 50 leechers. And none of them are one of the peers you connected to before, and of those there are now 3 with an open incoming port so you get 10MiB/s. Say you switch vpn servers back and forth, you will connect to different peers every time, so the speed will also vary not only based on the load on the vpn server but the speed of those you are connected to as well which can change every time. So again, how can you know that, when you are not even connecting to the same peers as before? IMHO available connections (an open incoming port) is the number one factor when it comes to speed in p2p. In any case, when your subscription is up you'd be better of with a provider that supports port forwarding. In fact, not just you will be better off, but all the other peers that you will encounter will thank you too

it did read the entire thing. And why not? Why shouldn't that explain it? If noting else changed in your settings or network it's either that or slow vpn server. If you don't have an open incoming port your speed will always fluctuate. Today you get 8MiB/s tomorrow you might get 2, 10 or 20. But as I said you almost certainly do not get full speed. This guy from reddit says it well: Source: https://www.reddit.com/r/torrents/comments/agwhiq/why_opening_bittorrent_ports/