monitoring a remote qbittorrent instance, getting api error

[gottoesplosivo]

Hello,

I'm trying to setup a widget to monitor a remote qbittorrent instance, however after setting up the widget I get this error
API Error: JSON.parse: unexpected character at line 1 column 1 of the JSON data.

The snippet is the following

- Backup:
    - qBittorrent:
        icon: qbittorrent
        href: https://domain/qbittorrent
        ping: https://domain/qbittorrent
        widget:
            type: qbittorrent
            url: https://domain/qbittorrent
            username: user
            password: pass

Ping is working and showing the remote host is up, since it is. But I can't get widget to work.
Could anybody help?

Thanks!

[dkowis]

I'm having the same problem, my configuration is basically the same:

    - Qbittorrent:
        icon: qbittorrent.png
        href: http://qbittorrent:8080/
        description: Torrents Downloader
        widget:
          type: qbittorrent
          url: http://192.168.69.254:8080
          username: admin
          password: teeheehee

No slash on the end of the URL, I've even tried adding /api/v2 to it also, but I don't get any satisfaction.

I even installed curl into the homepage container to make sure it'd work, and it did, and yet still errors from the logs:

/app # curl -i --data 'username=admin&password=teeheehee' http://192.168.69.254:8080/api/v2/auth/login
HTTP/1.1 200 OK
connection: keep-alive
content-length: 3
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/plain; charset=UTF-8
cross-origin-opener-policy: same-origin
date: Sat, 23 Dec 2023 00:48:06 GMT
referrer-policy: same-origin
set-cookie: SID=pretendthisisvalid; HttpOnly; path=/; SameSite=Strict
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block

LOGS:

[2023-12-23T00:46:37.807Z] error: <qbittorrentProxyHandler> HTTP 404 getting data from qBittorrent.  Data: Not Found
[2023-12-23T00:46:48.538Z] error: <qbittorrentProxyHandler> HTTP 404 getting data from qBittorrent.  Data: Not Found
[2023-12-23T00:47:23.627Z] error: <qbittorrentProxyHandler> HTTP 404 getting data from qBittorrent.  Data: Not Found
[2023-12-23T00:47:49.636Z] error: <qbittorrentProxyHandler> HTTP 404 getting data from qBittorrent.  Data: Not Found

I don't know why it's giving a 404 in the logs, but I see the API error pasted above on the actual dashboard.

[dkowis]

I did get mine working eventually using a completely different API endpoint, honestly not sure why it wasn't working with the as configured one. Maybe I had a typo and was too tired to notice it?

[gottoesplosivo]

I got mine working by pointing the widget to http://host:webuiport and ofc login and pass are those to access the webui

[github-actions[bot]]

This discussion has been automatically closed because it was marked as answered.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.