Closed andresatierf closed 2 years ago
I'm also unable to reach WEBUI via network, but fine via vnc to my server, but mine shows the PID. Otherwise completely fine log.
Same problem with watchtower and updated to the lastet image.
Stuck to `[info] qBittorrent PID:
I will try to go back to previous version `
Hi, I have same issue with OMV-Portainer. qBittorrent process can't start because remaining /var/run/qbittorrent-nox.pid file, which should be deleted at some step I presume. Workaround is to delete that file then restart container. All is fine then. I hope that helps.
Also having this issue after updating. Deleting /var/run/qbittorrent-nox.pid and restarting didn't resolve it.
Looks like a working workaround is listed under: https://github.com/MarkusMcNugen/docker-qBittorrentvpn/issues/91#issue-847475970
I'm running qBittorrentvpn in docker and have a watchtower container updating it regularly. I've noticed since the last update (from a couple days ago) the folowing line is missing a PID
2021-04-17 00:18:01.562182 [info] qBittorrent PID:
Since this update I've been unable to access qBittorrentvpn via the WebUI. Looking at the console, everything seems fine,
Here are the logs (same thing happens with vpn on):