-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Still can't connect with qbittorrent v4.0.2 #1026
Comments
show me a screen capture of your qBt webui settings page. |
is it not connecting or does dtv simply state it can't connect? i left qbittrrent 4.0.3 installed cause regardless of the message in dtv it does pass the torrent info to qbt, and qbt downloads the torrent just fine. |
if you use your chrome browser to access the qBt webui, by pasting |
It returns Invalid Request |
maybe something has grabbed port 8080 but has not released it for qBt to use (the old utorrent?). |
That makes sense as utorrent was set to port 8080 and I haven't uninstalled it yet. |
I believe the torrent downloaded to the specified folder. |
QBT was working fine with DTV for a long time up until a little over month ago. changed modem and set network from public (not sure why it was set to that) to private and after that nothing. Changed network back to public nothing. Uninstalled both dtv and qbt several time still not connecting. Error: {"data":"","status":401,"config":{"method":"POST","transformRequest":[null],"transformResponse":[null],"headers":{"Content-Type":"application/x-www-form-urlencoded","X-Forwarded-Host":"chrome-extension://bagblfnohpiddokbpaacecffdboomafe","Accept":"application/json, text/plain, /"},"url":"http://localhost:8080/login","data":"username=admin&password=*****"},"statusText":"Unauthorized"} |
@crashwave Yes, qBt made a change in 4.0.3 that broke the DuckieTV qBt client interface. qbittorrent/qBittorrent@b827761 fixes this problem, which will be included in the next qBt release, whenever that gets published. |
@spmilden so did you succeed in connecting qBt 4.0.2 with DTV once you switched ports? |
@garfield69 I did but the downloads still went to the default drive and folder rather than to the path specified. It's a bit of a pain to manually move the finished downloads to the proper folders so Plex can recognize the shows and download the metadata for them but it's not a huge deal. I'll have some time to play around with other clients in a few days. If I figure it out I'll let you know. Thanks for following up! |
Thanks - I'll give it a shot and let you know. |
but you have already downloaded HtGAwM s04e01 before, so unless you deleted the torrent and files, qBt could cheat and claim the download was done already.... have you tried it with a never downloaded before torrent? |
Thinking about this some more, I'm beginning to wonder if qBt hasn't glitched it's config somehow, either when you backtracked down from 4.0.3 to 4.0.2, or because of a bug that treats some of the settings you previously made unchangeable or some such weirdness. |
Thanks -unfortunately no change. BTW I'm not committed to qbt if you have better luck with a different client. |
Oh well, seeing as you cannot get qBt to work for you (works for me so I don't know what is going on), then you might as well try out one of the other clients that support dl-paths. |
I just tried BiglyBT, Transmission, Vuze and Deluge with the same result, i.e., went to the default dl folder. I exited each client and dtv then restarted. Puzzling... So none of the clients will accept changing the dl folder from dtv. My assumption is that that problem exists with dtv since it's the common thing. What about doing a clean install of dtv? If so is there a way to save the list of shows so I don't have to reselect each of them without potentially contaminating the install? |
So for some reason the torrent clients are rejecting your choice of drive... and you say there is nothing in the logs of any of the torrent clients that gives an explanation? |
I have a media server with five 2 tb drives - all are internal NTFS so there is no difference between the G and I drives. I'll try setting the dl path to C and see what happens. Any thoughts as to what I might check re my system set up? There's nothing I did when installing Windows 7 other than standard set up. |
So DTV and the torrent clients are running on this windows media server and therefore the G drive is a locally accessed drive? |
Using the C drive as the default dl made no difference. All of the drives are locally accessed. Sorry but I don't know how to access the WEBUI via Chrome. |
ok. which torrent client are you using now? what is the port number in the torrent client webui setup panel? |
Vuze and the port is 9091 |
I'll give it a try and let you know. |
I can't get Transmission to completely load. I've uninstalled and reinstalled it twice with the same result. Can I perform the test with qbt or another client? |
It worked just fine! What now? |
now we are going to see if using a duckietv chrome browser extension works, so we can check if the problem is isolated to your standalone or not.
|
Not sure about how to "connect your DTV extension to it"? Do you mean set qbt as the torrent client? |
DTV is my shorthand for DuckieTV. Assuming that you last use of the standalone was set to trying to use transmission, the backup you imported to your chrome extension DTV will now also be set to use that client connection. So all I meant was set up DTV to use the qBt 3.2+ client integration so you can connect with your qBt client. |
I understood DTV. I just wasn't clear about connecting the DTV extension to it. I did so and it goes to the default folder rather than the specified dl path. BTW I unchecked the setting in qbt under the Downloads section "Display torrent content and some options" as it requires user input before it will start the download. If I check it I have the option of setting the dl path each time which defeats the intention of automating the process. Other than that my settings in qbt are exactly the same as yours. |
WAIT. That does not sound right. That option only comes into effect if you submit a torrent via the qBt GUI. |
It is enabled - should it be disabled? |
Aha!!!! turn it off and try your test again. |
That did it! Thank you - thank you!!! Now I assume I can go back to the standalone, uncheck the same setting and not need to use Chrome. Yes/no? BTW I get an I/O error from qbt. This is from the log file: "(N) 2018-02-06T22:14:47 - An I/O error occurred, 'NCIS.S15E14.HDTV.x264-LOL[eztv].mkv' paused. NCIS.S15E14.HDTV.x264-LOL[eztv].mkv open (G:\TV Shows\NCIS\NCIS.S15E14.HDTV.x264-LOL[eztv].mkv) error: The process cannot access the file because it is being used by another process" When the error shows the torrent Status shows Stalled. I never had this happen with utorrent and the only change to my system is Chrome and qbt. Any ideas on how to find out what the offending process is? |
\o/
Yes. use the Trash bin on the Chrome Extensions manager to remove the now redundant testing DTV extension.
Geesh :-b If it's not one thing its another ;-) |
I had the same thought about Plex so stopped the server but it didn't make any difference. I then suspected antivirus but stopping that made no difference either. I just changed the setting in qbt you suggested but it didn't make any difference. I searched online for the error and it seems to be a common problem with qbt going back to 2013 with no solutions that I've found so far. Any recommendation for another bt client other than Transmission which I can't get to load properly that will allow dtv to set the dl path? |
Try BiglyBT. |
I think I figured out what was causing the I/O error. I stopped all of Cyberlink Power DVD's processes and the I/O error hasn't reappeared. Now that qbt seems to be working properly I'll hold off making any other changes. Thanks again for your help and patience. |
What build of DuckieTV are you using (Standlone / Chrome Extension (New Tab / Browser Action))
...Standalone
What version of DuckieTV are you using (Stable 1.1.x / Nightly yyyymmddHHMM)
...Nightly V201801140130
What is your Operating System (Windows, Mac, Linux, Android)
...Windows
Describe the problem you are having and steps to reproduce if available
...Sorry to bug you again. I uninstalled v4.0.3 and installed v4.0.2 but still can't connect.
Attach any DuckieTV statistics or Developer Console logs if available
...Failed to load resource: the server responded with a status of 400 (ERROR)
app.js:3724 qBittorrent 3.2+ connect error! Object
(anonymous) @ app.js:3724
spmilden:*******@localhost:8080/version/api Failed to load resource: net::ERR_CONNECTION_REFUSED
deps.js:2354 qBittorrent 3.2+ Connect call failed.
(anonymous) @ deps.js:2354
app.js:3724 qBittorrent 3.2+ connect error! qBittorrent 3.2+ Connect call failed.
(anonymous) @ app.js:3724
The text was updated successfully, but these errors were encountered: