CoCoMcBeats

It was you, from this post This part of the config IS required for any wireguard setup. you would have had to do it when you originally had your stuff working, and like me, you probably just thought that you could just use the old wg0 config, even though the information in it is obfuscated.. I'm not sure it's the only issue you're having, but if the public key isn't getting parsed correctly, you'll never connect to the VPN, and qbittorrentvpn won't open the web ui.

@binhex I think i fixed it AND i think i know what caused it. I was trying to teach myself to fish, and was looking at my logs to see if anything stood out, and there it was. Even though i'd changed the port from 8080 to 8081, (by clicking Edit, and changing the port number in the modal) When i saved, the command execution kept spitting out -p '8081:8080/tcp' When i looked at other docker containers, both sides matched. So I figured i'd just delete the one docker that was also using 8080 (Scrutiny) and try putting your container back to 8080 and it immediately worked. and now the command execution reads -p '8080:8080/tcp' I am not a programmer by any stretch of the imagination, but if this is helpful to you in any way, Yay! if not... uh, thank you for your patience while i fixed it myself and wasted your time.

@Elmojo I popped back in to see if there was a response to my thing and saw your post. I think i know what part of your problem is. Earlier in the thread, you were talking to somebody about replacing the wg0 file, and i think you need to do that. I'm using protonvpn, so i don't know what the exact steps are for you, but i bet that's part of your problem (I had the same config parsing error.) So what you need to do is go to PIA and REDO the wireguard setup. I think what's happened is that you have redownloaded the cert, but after a set amount of time, PIA hides the public/secret keys. I had to delete my old wireguard setup, create a new one, download THAT config file, rename it to wg0.conf and then slap it into the appdata/binhex-qbittorrentvpn/wireguard folder. Also, ftr, you haven't removed some sensitive information from your logs, so your un/pw from your provider are hanging out for the whole world to see. you might want to erase those from your posts and then generate new creds from PIA. sorry i can't give you super clear step by steps, as i said, i use a different provider.

So, my router reports the IP of this machine as 192.168.1.105, as do system settings (i'm on a mac atm). when i run ifconfig i get a 127 number in the first block of text, but i'm only telling you this because i'm not sure if it's important and i think, while i wait for you to respond, that i'm going to try a windows machine too for giggles. **Edit** Ok, So i hopped on my laptop running fedora (192.168.1.189) and tried and i still can't access the webui from there. I saw your post to the other individual about tailscale, so i tried disabling that (I wasn't really using it) but disabling tailscale doesn't resolve my problems (I was never connecting via tailscale, just for the record.) I don't know if there's some kind of strange config that i'm not seeing anywhere that could be causing this container to hate me right now, It's been working like a dream for the last 6 months or so. So thank you so much for the work you've done on this, and the help so far.

Hello! I've been scouring this forum and others, and it appears that I've found a new and exciting way to screw up. My binhex-QbittorrentVPN docker container was working fine and dandy for the last little while, but due to a screwup on my side, i had to reinstall the container. I can't get it working for the life of me now. I created a new Wireguard config, I've made sure none of my ports are goofy, I ABSOLUTELY have confirmed that the LAN_Network var is correct. But i Cannot access the WebUI to save my life. If i disable the VPN, it still fails to load the webUI... just faster. For the sake of potentially saving time, the thing i messed up before having to reinstall the docker image was the config files on my flash drive, I accidentally deleted them, so everything was still running... but the Unraid webui couldn't actually access them. Every other container I've reinstalled (a mittful of the binhex Starr apps) are working fine. I'd appreciate any help, cause this is driving me nuts. Command Execution supervisordlog