qBittorrent client is not reachable

typhoon71 commented 5 months ago

qBittorrent & operating system versions

qBittorrent: qbittorrent-nox 4.6.5 Operating system: debian bullseye (raspbian) [edit] this is a headless system [edit]

What is the problem?

The webUI becames unusable (red message "qBittorrent client is not reachable" in the lower part of the page)

Steps to reproduce

connect to the webUI with no torrent loaded (with or without SSL)
wait some time (usually less than a minute, or just 10 seconds)
webUI becomes unusable (red message "qBittorrent client is not reachable" in the lower part of the page)
once it happens, you have to log in again and it works normally... till it happens again.

Additional context

I googled about "qBittorrent client is not reachable" and I understand that when this happens is becaude the webUI doesn't "see" the remote qbittorrent device (raspberrypi) anymore.

I know the resources are limited on my old raspberrypi 1B but since the issue happens with no torrents loaded I don't think it's a performance issue. I watched htop while it happened and I didn't notice any spikes in cpu/disk/ram usage.

qbittorrent-nox process doesn't crash and continues to work normally even if there's a torrent loaded: it continues leeching/seeding. Only the webUI seems to be affected.

raspberry is connected to the network by lan cable, I connect to it by wifi.

Log(s) & preferences file(s)

No response

colemar commented 3 days ago

Same issue on Ubuntu 22.04 with qbittorrent-nox v4.5.5. The Web UI becomes irresponsive and shows "qBittorrent client is not reachable" after about 1 hour if not actively used (in a Chrome tab not in focus). I don't recall any instance where it happened while actively using it.

Increasing Session timeout: from 3600 to 86400 seconds in Web UI settings made no difference.

HanabishiRecca commented 2 days ago

Ubuntu 22.04 with qbittorrent-nox v4.5.5

This is outdated and unsupported version. Update to the latest version (5.0.1 atm) and see if the problem persists. If you use the PPA repo, your system won't get updates though. Use the official AppImage instead.

colemar commented 2 days ago

@HanabishiRecca I know nothing about AppImage. The info I found online only talks about "double-clicking" the image file. I use the bash shell via ssh exclusively, since the server is a remote machine and, while operating the GUI is possible, it would be very slow. In other words, a headless server. What if I am only interested in qbittorrent-nox (Web UI only) and I want to retain the current workings: systemd service, folders, other settings etc.?

HanabishiRecca commented 2 days ago

What if I am only interested in qbittorrent-nox (Web UI only) and I want to retain the current workings: systemd service, folders, other settings etc.?

Unfortunately, then you are out of luck with official builds at least. Unless you wish to update to the latest Ubuntu 24.10 of course, which has 5.x branch in the PPA.

There is also unofficial qbittorrent-nox-static project. It could work for you in theory, although I never used it myself.

colemar commented 1 day ago

There is also unofficial qbittorrent-nox-static project. It could work for you in theory, although I never used it myself.

Wonderful, I dropped the new executable in place of the old and it worked perfectly. Let's see if the Web GUI times out again.

I noticed that 21 IP addresses were banned since 5 minutes after it started, as reported in tab [Execution Log/Blocked IPs]. Do you know why?

HanabishiRecca commented 1 day ago

I noticed that 21 IP addresses were banned since 5 minutes after it started, as reported in tab [Execution Log/Blocked IPs]. Do you know why?

No. Every alert entry shows reason. If you think there is a bug, open a new issue.

qbittorrent / qBittorrent