-
Notifications
You must be signed in to change notification settings - Fork 46
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
Request failed with status code 405 #39
Comments
+1 |
+1 dying to use this! |
+1 how can I restore to the default UI without logging in? Adding “api/v2/app/setPreferences?json=%7B%22alternative_webui_enabled%22:false%7D” after the URL no longer works. |
Did some investigation on this now in the morning. It looks like a bug in 4.4.4 :( My request is identical to this https://github.com/qbittorrent/qBittorrent/wiki/WebUI-API-(qBittorrent-4.1)#login #38 I'll see if I can find a way around it tomorrow. For now I'm myself rolling back to 4.4.3 which is still working as expected. I know this is not ideal, but there's only so much I can do on the front-end :/ |
Scratch my last comment. I was able to fix it by copying the request from the default WebUI. Pull the most recent master branch and you should be good to go! |
good job! |
So exciting to see that message when I'm ready to roll back |
I can't input text into the login field now? |
Yeah the page itself didn't change at all. Maybe a hard refresh in the browser? |
its okay on the desktop but will not work on mobile at all |
actually I figured it out, its confusing because I was clicking on the username writing but input was to the right, would be great if the text was inside an input box so it didn't confuse me! |
great work! so excited for more updates :) |
Ah that's fair, I'll make it so that tapping the username word focuses on the input |
Try this.
The config file is named qBittorrent.conf. You can do a search for this file with: |
What a wonderful theme. Unfortunately i get this error at he login screen. How do I fix this? I have qBittorrent 4.4.4.
The text was updated successfully, but these errors were encountered: