DyonR

Are you sure your OpenVPN config file contains the line **auth-user-pass credentials.conf** And, are you sure that that a file **credentials.conf** exists next to the OpenVPN config file?

It seems like there is an issue creating a route to your default gateway, which is odd. Could you perhaps send your .ovpn file? Make sure to censor any IP...

> Since their config file is available publicly on their website, I'm uploading that as well. [OV-2023-DC - Copy.txt](https://github.com/DyonR/docker-qbittorrentvpn/files/11360299/OV-2023-DC.-.Copy.txt) That was just what I asked for 😝 I'll look at...

@bigbtechnology Could you give this .ovpn file a try? If it doesn't work please send a new log, note it's a `.txt` file, you should change it to `.ovpn` [newconf.txt](https://github.com/DyonR/docker-qbittorrentvpn/files/11360308/newconf.txt)

Alright, the authentication etc to the OpenVPN server works fine now. So the OpenVPN file is working properly now. I think the current issue may be caused by a potential...

Last thing I can think of for now is a conflict in the WebUI port and the OpenVPN port. In this OpenVPN config file line: `remote gw2.yul2.octanevpn.com 8080` Change 8080...

Very weird. Add another environment variable `RESTART_CONTAINER` and set to `no` (default is `yes`) and check if the WebUI will be accessible then. If the WebUI works, and the container...

For reference, here is my .ovpn file, maybe you can see some settings in my file that you may miss, but it really differs per provider obviously: ``` client dev...

Here is my full `docker run` command also, note there are many settings that don't impact the working of the container like HOST_OS, HOST_HOSTNAME: ``` docker run -d --name='qbittorrentvpn' --net='bridge'...

Sounds like more a VPN Provider problem to me. I can't imagine a VPN provider just opening all ports, especially since IPs are shared. Did you for example test to...