bcollins

It's unbelievable that this is still an open issue over 3 years after it was first logged.

Still an issue in 2023

I am experiencing the same issue with a structured library. Downgrading the plugin to 1.0.3.4 resolves the problem.

You only need to expose your qBittorrent ports within protonvpn-docker; you can remove ports entirely from your qBittorrent compose.

Unfortauntely not, port forwarding is only available in the Windows client so it's something Proton need to address before it can be added to this container.

Use a MacVLAN network