I'm getting this error:
TransmissionError('Request failed.', error) TransmissionError: Request failed. Original exception: HTTPHandlerError, "HTTPHandlerError 401: Unauthorized"
in the checks page but it appears to be listing the torrents properly.
I have my transmission server on a different server and I made sure to set the IP, ports, and credentials properly in the config and database but I'm getting that error. I also made sure to whitelist the WM2 IP in the transmission config and I have a reverse proxy in Apache that connects to it fine. This may be because I updated transmission to 2.94 but I can't say that with certainty.
I believe this issue might be partially because in the past I just deleted torrents from the instance using remote or the web gui when they became unregistered but I do not know if that is the issue. One thing that I also think might be good is if there was a button to delete torrents from the database if they were no longer in transmission. I was having issues with this in the past and getting the database entries to delete properly was kind of a pain because it involved getting rid of several related entries.
My setup is a bit weird, as I have a transmission instance on one server with a NFS share to the webserver where they both have the same paths to the files. For example, on the transmissions server the files may be in /mnt/share/wmfiles/groupid/... and they are also in /mnt/share/wmfiles/groupid/... on the webserver because of how I have the NFS share mounts.
I haven't been using WM2 lately and I periodically check it to make sure it's running well and this check issue seems to be a new issue that has arisen after I updated transmission to 2.94 without changing any other variable.
I'm getting this error:
TransmissionError('Request failed.', error) TransmissionError: Request failed. Original exception: HTTPHandlerError, "HTTPHandlerError 401: Unauthorized"in the checks page but it appears to be listing the torrents properly.
I have my transmission server on a different server and I made sure to set the IP, ports, and credentials properly in the config and database but I'm getting that error. I also made sure to whitelist the WM2 IP in the transmission config and I have a reverse proxy in Apache that connects to it fine. This may be because I updated transmission to 2.94 but I can't say that with certainty.
I believe this issue might be partially because in the past I just deleted torrents from the instance using remote or the web gui when they became unregistered but I do not know if that is the issue. One thing that I also think might be good is if there was a button to delete torrents from the database if they were no longer in transmission. I was having issues with this in the past and getting the database entries to delete properly was kind of a pain because it involved getting rid of several related entries.
My setup is a bit weird, as I have a transmission instance on one server with a NFS share to the webserver where they both have the same paths to the files. For example, on the transmissions server the files may be in /mnt/share/wmfiles/groupid/... and they are also in /mnt/share/wmfiles/groupid/... on the webserver because of how I have the NFS share mounts.
I haven't been using WM2 lately and I periodically check it to make sure it's running well and this check issue seems to be a new issue that has arisen after I updated transmission to 2.94 without changing any other variable.