400 bad request ping on Jackett
I suddenly started getting "Bad Request: 400 denied" ping on my Jackett app, despite it being accessible and seemingly working fine. No errors in logs on either one. Uptime Kuma detects it up as normally. Things tried so far:
- Stopped and restarted both homarr (updated to latest) as well as jackett.
- Cleared cache
- Removed/re-added the app tile
12 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
❓ Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
Hi @bleak , please provide the data as requested by @Cakey Bot
I actually found the error in console
Please provide your server side log. not the console. https://homarr.dev/docs/community/faq/#how-do-i-open-the-console--log
❓ Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
I did post it just a second ago but it's nothing
here
400 means that Jackett marks the request as "bad". Try another url (one that does not redirect you) or ad 400 as an accepted status code.
Ok so if I actually do http://localhost:9117/UI/Login?cookiesChecked=1 it works
Which is the url jackett redirects to if you're not logged in
What's odd is, it used to work fine before
Then you should use that URL 👍
You probably updated Jackett (or the proxy if you have one)
I didn't... but whatever, as long as it works
I apologize for this
A bit of a silly thread
I appreciate your help though
No worries. Can I mark this as resolved?
sure thing