-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resume torrents failing after completed race #43
Comments
Related to #39 I think. Initially the API worked with both GET and POST, though as per spec it should be POST Over time they started to enforce this. Let me fix it for this endpoint, and update the release. |
Awesome, thanks for the quick response! I did just test it by copying and pasting the pause torrent snippet, changing it to resume and it worked. So it's good for me at the moment if you want to take your time to update the release. |
@durgins I've released the fixed version. You can update it by running:
I am not entirely sure how this affects manual patches, but I guess it will just overwrite it. |
When running qbit-race with the completed option, it isn't resuming torrents in qBittorrent 4.6.0 with an error in the log file:
2023-11-20T22:22:28.161Z [ERR]: Failed to resume torrents! Error: Failed to resume torrents. Error: AxiosError: Request failed with status code 405
I looked this up and it looks like 405 is usually returned when using a GET method when POST is wanted.
The problem seems to lie here :
qbit-race/src/qbittorrent/api.ts
Lines 102 to 104 in 1882490
I see that other things like pausing the torrents, adding tags, etc are all using POST and they are working. Is there any reason why this was coded with GET? If so, would a fallback to POST on failure fix my problem?
The text was updated successfully, but these errors were encountered: