qBittorrent WebUI will "refuse" to download a torrent if added from a mobile device

[rdlf4]

qBittorrent & operating system versions

I'm running the latest v5.0.3 of the WebUI on my Raspberry Pi OS, along with:
Qt: 6.8.2
Libtorrent: 2.0.11.0
Boost: 1.87.0
OpenSSL: 3.4.0
zlib: 1.3.1.zlib-ng

What is the problem?

Here's the problem: when I access WebUI from my phone and a torrent file is provided to the WebUI, it will show on the "Downloading" panel, but it will stay stuck at "Stalled". I've tried to force start it with no results; Also, forcing a re-announcement does nothing either (both proceedings were done on my phone).
I've done this multiple times with the same output. But over on my PC, when I add the same torrent from my computer, it downloads right away.
So I took a different approach and grabbed both torrent files, from my phone and my computer, and compared them with sha256. Terminal outputs an "OK", which leaves my phone out of the equation. This must be a bug of some kind.

Steps to reproduce

First, download the torrent file from your mobile browser. I used Firefox Mobile for this.
Secondly, open the WebUI on mobile browser; tap on the Plus icon and provide the torrent file Firefox saved to internal memory of the phone.
Third, witness the torrent file has been started, but it gets stalled and nothing else will happen.***

Additional context

*** For context, I've also tried the reverse procedure. Meaning if I download the torrent file from my computer, then transfer it to my phone. Now, I access the WebUI on my phone and I provide it with the torrent file from my PC, and it works. But sha256 says the files' structures are the same and haven't been changed, so I don't get why WebUI is being picky. Again, sounds like a bug, doesn't it?

Log(s) & preferences file(s)

qbittorrent.log

watched_folders.json

[HanabishiRecca]

But sha256 says the files' structures are the same and haven't been changed, so I don't get why WebUI is being picky. Again, sounds like a bug, doesn't it?

No, sounds like a user error for me. If files are identical, WebUI can't be picky because there is literally no way to distinguish them.

[rdlf4]

But sha256 says the files' structures are the same and haven't been changed, so I don't get why WebUI is being picky. Again, sounds like a bug, doesn't it?

No, sounds like a user error for me. If files are identical, WebUI can't be picky because there is literally no way to distinguish them.

Then work on your text interpretation, the only "user error" here seems to be having you spit out nonsense and blame me for it.

[glassez]

@rdlf4
Could you provide screenshots of qBittorrent WebUI with added torrent for both the cases (added from your phone and from your PC)?

[glassez]

it will show on the "Downloading" panel, but it will stay stuck at "Stalled". I've tried to force start it with no results; Also, forcing a re-announcement does nothing either

Restarting qBittorrent doesn't help either?

[glassez]

@rdlf4
Is this a problem with any torrent or any specific one?
Did you try doing it from another (mobile) browser or phone?

[rdlf4]

@rdlf4 Is this a problem with any torrent or any specific one?

As far as I can tell, this is an issue affecting torrent files from Private Trackers. To challenge that theory, I created my own torrent file using the latest QBittorrent for desktop on my computer. I then used an open tracker (udp://tracker.opentrackr.org:1337/announce) and shared the torrent file with my phone, which is on the same network as my computer and my RPi, which is the torrent server. That went ok. I then downloaded the latest Linux Mint torrent on my phone and had WebUi start downloading it just fine. The problem only manifests when a torrent file has been downloaded from a private tracker on my phone, which was not happening on a previous version, mind you. I got to talk about this on IRC with one of the mods and I was told to log out, then back in to the site on my phone, then download a torrent file again, but that did not help either. I've double-checked the folder where QB is supposed to download files to, and it does have read & write access. I've also made sure the torrent is supposed to start downloading as soon as it's been added.

Did you try doing it from another (mobile) browser or phone?

Yeah, I did the same procedure with both Firefox for Android and Brave Browser.

Restarting qBittorrent doesn't help either?

No, it doesn't. And the qbittorrent.log file doesn't help either, as it only mentions when the torrent file has been added and deleted.

@rdlf4 Could you provide screenshots of qBittorrent WebUI with added torrent for both the cases (added from your phone and from your PC)?

I merged them into one. Have a look:

At the top you can see the torrent is downloading just fine on the Pi when added from my computer, whereas at the bottom the file was added from my phone's internal memory, which is where the browser saved the torrent file.

[glassez]

I merged them into one. Have a look:

At the top you can see the torrent is downloading just fine on the Pi when added from my computer, whereas at the bottom the file was added from my phone's internal memory, which is where the browser saved the torrent file.

In the context of this issue, displaying the Content pane is useless, while it would be much better to display the Trackers pane on your screenshots. Could you provide them?

[glassez]

For context, I've also tried the reverse procedure. Meaning if I download the torrent file from my computer, then transfer it to my phone. Now, I access the WebUI on my phone and I provide it with the torrent file from my PC, and it works.

Hmm...
What if download the torrent file from the phone, then transfer it to the computer and add to qBittorrent there?

[rdlf4]

For context, I've also tried the reverse procedure. Meaning if I download the torrent file from my computer, then transfer it to my phone. Now, I access the WebUI on my phone and I provide it with the torrent file from my PC, and it works.

Hmm... What if download the torrent file from the phone, then transfer it to the computer and add to qBittorrent there?

In that case, the download will also get stuck at "Stalled" on my computer. I gave it a minute, and made sure there's enough seeders (there is).
It just won't change. But qbittorrent.log will only say "Added new torrent".

[glassez]

I gave it a minute, and made sure there's enough seeders (there is).

In the screenshot above, there is not a single seeder in a similar case. Are they really different, or did you not wait for them to appear when you took that screenshot?

[rdlf4]

I gave it a minute, and made sure there's enough seeders (there is).

In the screenshot above, there is not a single seeder in a similar case. Are they really different, or did you not wait for them to appear when you took that screenshot?

Both pictures are about the same torrent file. The only difference is the device I used to download the torrent.
I told you previously that I gave it a minute, usually qBittorrent starts the torrent and for the first 2 to three seconds, the torrent will be "Stalled" until the downloading process takes off. But on the phone, it stays like that forever.

[glassez]

Both pictures are about the same torrent file. The only difference is the device I used to download the torrent.
I told you previously that I gave it a minute, usually qBittorrent starts the torrent and for the first 2 to three seconds, the torrent will be "Stalled" until the downloading process takes off. But on the phone, it stays like that forever.

I didn't ask about the differences between those two pictures. I was asking about the differences between the results shown on the second one (stalled torrent with zero seeders) and the ones you described in #22233 (comment) (stalled torrent with non-zero seeders, IIRC).

And how about screenshots with Trackers pane shown?