After new update, qbittorrent doesn't accept new torrents..

[heinowalther]

Hi

After the recent update to version 2.0, first of all the configuration from the old version is just wiped and you start with a clean install??
I then added my qbittorrent server which is very simple, running a non HTTPS setup... but it won't accept any of the torrents I try... the GUI pops up with the request to set a label, which I do, but nothing seems to be passed to the server... ?!?

This is on latest Chrome on MacOS... With a qbittorrent server version 5.1.2 presented on port 8080....

[sandorx-cobol]

When mine updated my config was also lost.

When re-added qbittorent and clicked a link nothing would happen. I noticed in the manage extensions that the new version was getting an error. Did some digging and looked like a 401 error.

Long story short, I had to disable "Enable Cross-Site Request Forgery (CSRF) protection" in qbittorent (options / webui) for this extension to work.

[bluasoar]

I also seem to be having an issue since the Sept 2nd update, I've re-added my qBit client to the config but can't seem to get the "Add to Remote WebUI" to co-operate, it doesn't seem to be popping up with the box for category / directory input like it used to. Really appreciate all the work put into this tool sorry I don't have any additional / helpful info.. Thank you!

[DazzXXX]

Similar issue here. Update wiped out settings. Reconfigured for Deluge, adding address to client, port and password. Simple. Left everything else at defaults. Can't seem to get it to add Magnet or Torrent. Using Brave 1.81.137, Deluge Client 2.1.1. Everything was working fine before update.

[nothing2obvi]

It's working for my v4.5.5 qbittorrent instance but not v5.0.0

[bogenpirat]

you're all correct about the settings migration - that didn't work as i expected (and wasn't really testable) because it relies on a new API which doesn't deliver the data that the old one did like i expected. so re-configuration is indeed necessary.

since y'all are describing distinct issues, i'd appreciate it if you could open separate github issues unless you're certain it's the same problem, because solving 5 things in 1 github issue is annoying.

I then added my qbittorrent server which is very simple, running a non HTTPS setup... but it won't accept any of the torrents I try... the GUI pops up with the request to set a label, which I do, but nothing seems to be passed to the server... ?!?

please check the inspect view for the extension's service worker. you can do that under chrome://extensions/?id=oabphaconndgibllomdcjbfdghcmenci -> as per your description, there should be an error log entry as when you try (and fail) to add a torrent/magnet. this'll tell us what's going on.

I also seem to be having an issue since the Sept 2nd update, I've re-added my qBit client to the config but can't seem to get the "Add to Remote WebUI" to co-operate, it doesn't seem to be popping up with the box for category / directory input like it used to. Really appreciate all the work put into this tool sorry I don't have any additional / helpful info.. Thank you!

the label/dir selection dialog is no longer injected as part of the website - instead, it's now implemented as the extension popup window. try to check the aforementioned instructions for viewing log messages so we can figure out what might've gone wrong.

Similar issue here. Update wiped out settings. Reconfigured for Deluge, adding address to client, port and password. Simple. Left everything else at defaults. Can't seem to get it to add Magnet or Torrent. Using Brave 1.81.137, Deluge Client 2.1.1. Everything was working fine before update.

same answer as above - let's check the error logs. as an aside, i have no aspirations of supporting browsers other than chrome, where RTA was no longer working - hence the rewrite/update.

It's working for my v4.5.5 qbittorrent instance but not v5.0.0

as @sandorx-cobol already mentioned and as is documented in various places for RTA v2: try disabling CORS. manifest v3 APIs do not allow extensions to circumvent CORS checks. in QBT webui options, these settings work for me:

[jporban]

Disabling CSRF protection and cookie Sercure Flag worked for me.

[bluasoar]

Here are the errors I am receiving -- https://paste.passtheheadphones.me/?f01cfef8aab54d52#4v3jbXRHLftUutpNt3g8wXwp8zX3kgiEv9KXqCtR319i I have disabled both CSRF Protection & the Secure Cookie Flag within qBit (5.1.0) and the issue still persists. I used to be able to send to client via the Download button but it seems now it detects it as text / html? I am not entirely sure what could be causing this. Thank you!

[bogenpirat]

@bluasoar does this happen on other sites too? e.g. https://webtorrent.io/free-torrents

[bluasoar]

@bogenpirat Hey, I just tested it out and yup, same exact error. I am also getting a notification from the Browser saying "Remote Torrent Adder Failed Error: [Object; Object]" Sorry I don't have any valuable information beyond no workie D:

Edit: Apparently I had to whitelist the machine I am adding the torrent from, this wasn't the case previously but everything is working how I'd expect now. Appreciate the help bogenpirat and sorry for the bother! I also wanted to ask about the Label / Directory option and whether it was possible to select which you'd like upon adding / how it decides what label to set?

[bogenpirat]

yeah, the notification for errors emanating at that particular stage is fucked in the v2.0.0 release. i've fixed it in the repository - if you feel like it you could take a look at what e.g. this version loaded manually in developer mode spits out.

same exact error

i'm having a hard time believing that. your log shows three separate error messages:

1. webui.ts something within the QBT module errors out
2. torrent download:
   a) in messaging.ts something at torrent download errors out because the server complains about too many requests
   b) in download.ts the received file has the wrong content type

i can see 1. happening for this other URL, but not 2a/b - i've been testing with that site quite extensively and it's never thrown that sort of error. can you clarify what exactly your error log looks like on that page?

[bluasoar]

Hey, so I seem to be getting rate limited whenever I try to add stuff to the client. I see this in the Console output "Uncaught (in promise) Error: Failed to open popup" and "Uncaught (in promise) Error: Extension does not have a popup on the active tab." I can see the context menu disappearing and reappearing rapidly. I also see an insane amount of 429 errors in the log when I try "Add to Remote WebUI" similar to the first log I had sent. -- https://paste.passtheheadphones.me/?5fcc29ddd82fe411#6e1vqKmYkE8BRPV7s9nL4TcnH9qKK6ekXf6KmJGVQRUG

[off3nc3]

I have another issue , i can't for the life of me proc the choosing category/label when right clicking torrent links/magnets , no pop-up nothing happens, no download nothing , and i enabled/added all the labels for the dirs. and everything.

I can't get the extension to work at all.

Trying my best to setup QbittorrentWEB ui for my seedbox, i feel like the OG remote adder was much more easier to setup or i'm missing something now ?

[bogenpirat]

@bluasoar @off3nc3 from my understanding both of your last posts represent new problems - please feel free to open separate issues for them.

for some additional info, please include some info from this:

please check the inspect view for the extension's service worker. you can do that under chrome://extensions/?id=oabphaconndgibllomdcjbfdghcmenci -> as per your description, there should be an error log entry as when you try (and fail) to add a torrent/magnet. this'll tell us what's going on.

[off3nc3]

check the inspect view for the extension's service worker

https://imgur.com/a/r3sCdpt

Done , please take a look ..

[thisisnotmyrealname]

So, I had the same issue about pushing torrents to QBT 5.1.2.

No error from the extension saying it was unable to add the torrent.

Same CORS error, even though CORS is disabled in the QBT advanced settings.

I had to add "Access-Control-Allow-Origin: chrome-extension://oabphaconndgibllomdcjbfdghcmenci"

To "Add Custom http headers" for it to work