H
Homarr10mo ago
H₂O

No supported torrent, even tho qbit is integrated

as the title says, i keep getting no supported torrent clients found even tho qBit is integrated other integrations work fine its just qbit
No description
Solution:
Please check in the settings, not in the headers of a test response
Jump to solution
15 Replies
Cakey Bot
Cakey Bot10mo ago
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?
Manicraft1001
Manicraft100110mo ago
Hi @DaYroXy , please provide the data as requested by @Cakey Bot
H₂O
H₂OOP10mo ago
running on debian 12, docker
No description
No description
H₂O
H₂OOP10mo ago
for docker compose i kinda lost the configrations but these are the paths im passing in portainer
No description
H₂O
H₂OOP10mo ago
No description
No description
H₂O
H₂OOP10mo ago
H₂O
H₂OOP10mo ago
i think that should be all?
Manicraft1001
Manicraft100110mo ago
403 either means your password is wrong or qBittorrent is blocking the request (eg. CSRF protection)
H₂O
H₂OOP10mo ago
password is correct, i changed it now to double check also qbit doesnt use csrf i think here are the headers
HTTP/1.1 200 OK
Server: openresty
Date: Sun, 10 Mar 2024 08:40:07 GMT
Content-Type: text/html
Content-Length: 3594
Connection: keep-alive
cache-control: no-store
content-encoding: gzip
content-security-policy: default-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; script-src 'self' 'unsafe-inline'; object-src 'none'; form-action 'self'; frame-ancestors 'self';
cross-origin-opener-policy: same-origin
referrer-policy: same-origin
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
X-Served-By: qbittorrent.lan
HTTP/1.1 200 OK
Server: openresty
Date: Sun, 10 Mar 2024 08:40:07 GMT
Content-Type: text/html
Content-Length: 3594
Connection: keep-alive
cache-control: no-store
content-encoding: gzip
content-security-policy: default-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; script-src 'self' 'unsafe-inline'; object-src 'none'; form-action 'self'; frame-ancestors 'self';
cross-origin-opener-policy: same-origin
referrer-policy: same-origin
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
X-Served-By: qbittorrent.lan
Manicraft1001
Manicraft100110mo ago
Try to remove and readd the app again
H₂O
H₂OOP10mo ago
if you mean in homarr it self i did and tried no luck, also i tried using wget 172.25.0.2:8080 from homarr shell and i got the login html fine too
Manicraft1001
Manicraft100110mo ago
Did you disable CSRF in qBittorrent?
H₂O
H₂OOP10mo ago
its already off by default i didn't but in the headers there are no csrf
# wget --spider -S http://172.25.0.2:8080
Spider mode enabled. Check if remote file exists.
--2024-03-10 08:47:04-- http://172.25.0.2:8080/
Connecting to 172.25.0.2:8080... connected.
HTTP request sent, awaiting response...
HTTP/1.1 200 OK
cache-control: no-store
connection: keep-alive
content-length: 1671
content-security-policy: default-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; script-src 'self' 'unsafe-inline'; object-src 'none'; form-action 'self'; frame-ancestors 'self';
content-type: text/html
cross-origin-opener-policy: same-origin
date: Sun, 10 Mar 2024 08:47:04 GMT
referrer-policy: same-origin
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
Length: 1671 (1.6K) [text/html]
Remote file exists and could contain further links,
but recursion is disabled -- not retrieving.
# wget --spider -S http://172.25.0.2:8080
Spider mode enabled. Check if remote file exists.
--2024-03-10 08:47:04-- http://172.25.0.2:8080/
Connecting to 172.25.0.2:8080... connected.
HTTP request sent, awaiting response...
HTTP/1.1 200 OK
cache-control: no-store
connection: keep-alive
content-length: 1671
content-security-policy: default-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; script-src 'self' 'unsafe-inline'; object-src 'none'; form-action 'self'; frame-ancestors 'self';
content-type: text/html
cross-origin-opener-policy: same-origin
date: Sun, 10 Mar 2024 08:47:04 GMT
referrer-policy: same-origin
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
Length: 1671 (1.6K) [text/html]
Remote file exists and could contain further links,
but recursion is disabled -- not retrieving.
that from the homarr container
Solution
Manicraft1001
Manicraft100110mo ago
Please check in the settings, not in the headers of a test response
H₂O
H₂OOP10mo ago
Never knew that was a thing! now it works 🙂 was a simple CSRF issue thank you
Want results from more Discord servers?
Add your server