Infinite loading screen on BitRemote launch when qbitorrent does not have any tasks

[3zero2]

My qbitorrent instance is behind a reverse proxy. When I try to connect I get the error below.

Any idea on how to resolve this?

Thank you.

[tatsuzo-arkstudios]

Sorry for the late reply. Did you setup a http basic authentication for the reverse proxy?

[3zero2]

What I have discovered in the meantime is that opening Bitremote when my Qbitorrent server has no active torrents results in a permanent loading screen:

If there is an active torrent then Bitremote manages to load the data correctly. I can even delete the torrent and get to this screen:

But as said above, this screen doesn't manage to load when there are no active torrent when app is launched.

[tatsuz0u]

Thank you for your detailed feedback. It appears that the authentication issue has been resolved.

However, the loading page could be due to a data conversion issue. Could you please also let us know which version of qBittorrent you are using?

[3zero2]

I'm using qBittorrent Version 4.6.5

[3zero2]

Just updated to BitRemote 1.2.0 and the issue persists.

[tatsuz0u]

Thanks for the update for this issue. We haven’t yet investigated this issue but will be looking into it. We appreciate your patience as we work on this. 🙏

[tatsuzo-arkstudios]

@3zero2 I have been using my qBittorrent behind a reverse proxy too and I have updated it to 4.6.5. Unfortunately I could not reproduce the issue in my environment.

Could you tell me how you authenticate with your instance? For example, what happens when you access your instance's WebUI in the browser?

• Http basic auth
  • A dialog pops up and asks for your username & pass

(PS: This is not actually a screenshot of a http basic auth dialog for a qBittorrent instance. But they should look the same.)

• WebUI login auth
  • The qBittorrent WebUI login page shows up and asks for your username & pass

Http basic auth or WebUI login auth, or both? 🤔

[3zero2]

Thank you for trying to reproduce the issue @tatsuzo-arkstudios.

I'm using the WebUI login:

In my case it looks a bit different as I'm using the VueTorrent WebUI.

[tatsuzo-arkstudios]

@3zero2 Thank you for the extra information.

Could you please try accessing your instance using the original WebUI? If the original one is available, then please try using the link to the original WebUI as BitRemote client host. 🤔

[3zero2]

@tatsuzo-arkstudios

Still happens with the default WebUI. Are there any logs I can provide?

[tatsuzo-arkstudios]

Finally reproduced. We’ll look into this and aim to resolve it in the next update.

[tatsuzo-arkstudios]

@3zero2 This issue should have been fixed in BitRemote 1.3.0. 😋