Rémi Marseault

After some digging, the SID cookie set by qBittorrent is created using the HttpOnly which disallows its access in JS environment (e.g. VueTorrent). Given those restrictions the backend can't be...

Backend has been updated to allow for bypass. More info [in the wiki](https://github.com/VueTorrent/vuetorrent-backend/wiki/Installation#caveats)

I'll keep it open as the solution is only a workaround and might cause issues in the future.

Fixed with 2.0 release of the backend

> Unfortunately I can't build my own VueTorrent because I run qbittorent through a container and use lsio docker mods for vuetorrent. Well you could build your own by adding...

Do you know if there's a way to determinate which version (or fork) of qbit is installed through the API ?

When opening the WebUI, a request is made to detect the current login state (authentication is cookie-based). The login screen shows up if this request fails. Open up the DevTools...

I tried installing the enhanced version. I haven't seen any way to differentiateit from the official version. Without it I doubt that this is feasible.

The list is empty, try clearing your filters (the red funnel icon at the top)

That's it! The weird thing is that you receive some 404 on the buildInfo route (and tags for some reason). That's unusual 🤔, I didn't even know it was possible...