Problem with qBittorent
Posted: 24 May 2023, 19:09
After updating my Terramaster F2-221 to version 5.1.24-00324, Plex and qBittorent the two applications I use regularly stopped working.
I uninstalled Plex and reinstalled it, this fixed the issue and Plex was up and running.
However, qBittorent (which was version 4.4.50 from the TerraMaster forum) was uninstalled and I installed 4.1.11 from the App Center. When I tried to update the application by downloading the latest release from the TerraMaster Forum (like I had done before), I was met with "502 Bad Gateway, nginx/1.18.0".
I tried multiple times to update using different versions from the TerraMaster Forum but had no luck. So at the moment, I am stuck with version 4.1.11 which does not give me the functionality I require (the use of VueTorrent WebUI is only available on versions of qBittorrent.
Please can you advise on how to fix this? I have tried to uninstall the existing 4.1.11 and its configuration files before installing the latest version but this has not helped, and vice versa I have tried keeping the existing application and simply installing the new one. This also has given the same error.
I uninstalled Plex and reinstalled it, this fixed the issue and Plex was up and running.
However, qBittorent (which was version 4.4.50 from the TerraMaster forum) was uninstalled and I installed 4.1.11 from the App Center. When I tried to update the application by downloading the latest release from the TerraMaster Forum (like I had done before), I was met with "502 Bad Gateway, nginx/1.18.0".
I tried multiple times to update using different versions from the TerraMaster Forum but had no luck. So at the moment, I am stuck with version 4.1.11 which does not give me the functionality I require (the use of VueTorrent WebUI is only available on versions of qBittorrent.
Please can you advise on how to fix this? I have tried to uninstall the existing 4.1.11 and its configuration files before installing the latest version but this has not helped, and vice versa I have tried keeping the existing application and simply installing the new one. This also has given the same error.