tracker error- operation cancelled

General support for problems installing or using Deluge
Post Reply
User avatar
wgstarks
Member
Member
Posts: 26
Joined: Thu Jun 29, 2017 11:06 pm
Location: North Carolina USA

tracker error- operation cancelled

Post by wgstarks »

I've been trying to get Deluge setup to use IP Torrents, but everything I add to the que fails. The torrent gets added but I just get a tracker error "empirehost.me: Error: Operation canceled". No idea how to fix this. The deluged log shows that the torrent was added. Doesn't show any errors.
shamael
Compulsive Poster
Compulsive Poster
Posts: 667
Joined: Sat Oct 08, 2016 9:28 am

Re: tracker error- operation cancelled

Post by shamael »

Hi,

From my experience this is a tracker issue, not Deluge. I face this situation with unhealthy tracker ( e.g. overloaded servers). The request to update the stats is refused by the tracker address. Maybe it's not the full picture but on my side it was nothing related with my Deluge setup
User avatar
wgstarks
Member
Member
Posts: 26
Joined: Thu Jun 29, 2017 11:06 pm
Location: North Carolina USA

Re: tracker error- operation cancelled

Post by wgstarks »

Seems to happen with every torrent I try from IPtirrents though. I must have tried at least 20. Don't think there all using the same tracker?
shamael
Compulsive Poster
Compulsive Poster
Posts: 667
Joined: Sat Oct 08, 2016 9:28 am

Re: tracker error- operation cancelled

Post by shamael »

I'm not familiar wit this tracker but if it's a private or semi-private one all torrents will rely on the same tracker address. You can easely check on some torrents you have. If a single tracker is used you can nail it down with a test on the tracker url (without passkey, just the HTTP address) and a curl loop telling you the returned HTTP header of the tracker. Or try with a different tracker to see the difference if any.
User avatar
wgstarks
Member
Member
Posts: 26
Joined: Thu Jun 29, 2017 11:06 pm
Location: North Carolina USA

Re: tracker error- operation cancelled

Post by wgstarks »

Quote from IPTorrents Forum-
Probably want a different client here. You need DHT and PEX disabled here and you'll need those at that site.
Will Deluge work without DHT and PEX? I don't know what they are so don't have a clue what this means.
Tvich
Member
Member
Posts: 33
Joined: Thu Apr 27, 2017 6:36 pm

Re: tracker error- operation cancelled

Post by Tvich »

wgstarks wrote:Quote from IPTorrents Forum-
Probably want a different client here. You need DHT and PEX disabled here and you'll need those at that site.
Will Deluge work without DHT and PEX? I don't know what they are so don't have a clue what this means.
Deluge accounts for probably 30% of traffic on iptorrents, if there were a problem with deluge, everyone would be "reporting in".
You can enable/disable DHT and Peer Exchange under Edit/Preferences Network Section. You don't need to and it won't matter.

Can you share some more details about your setup?
User avatar
wgstarks
Member
Member
Posts: 26
Joined: Thu Jun 29, 2017 11:06 pm
Location: North Carolina USA

Re: tracker error- operation cancelled

Post by wgstarks »

I have Deluge running in a docker on my unRAID system. Using PIA (VPN) and Privoxy (proxy). I've checked the deluged logs but they aren't very verbose. They show that the torrents are added to the que, but nothing after that. I currently have DHT and PEX disabled, but don't see any difference if they are enabled. Glad to furnish any more details you need. Thanks for the help with this.
Tvich
Member
Member
Posts: 33
Joined: Thu Apr 27, 2017 6:36 pm

Re: tracker error- operation cancelled

Post by Tvich »

What image do you use for deluge? Where did you get it?
How are openvpn and privoxy set up? Also in a container?
What I would do:
Pull a different image and run it without vpn, just to confirm, that something is wrong with your vpn setting :)

Use ssh to access unraid:
Stop the container:

Code: Select all

docker stop container_name
If you don't know the name of the container, run

Code: Select all

docker ps
find the correct container and then stop it.
Above can probably also be done from the unraid web interface ?

Now run this, It should not take long on a normal internet connection, the image is 28MB :

Code: Select all

mkdir ~/deluge-test

Code: Select all

docker pull sinaptika/deluged

Code: Select all

docker run -d \
--name c_deluged \
-p 50100:50100 \
-p 58846:58846 \
-v ~/deluge-test:/opt/deluge \
sinaptika/deluged
You now have the newest stable deluged running.
Create a username and password for logging in to deluge daemon by running:

Code: Select all

docker exec -it c_deluged deluged-pass.sh
Connect with the client to your unraid host on port 58846. Add a torrent from private tracker. See that everything works fine. Go fix your vpn/proxy settings :)

Cleanup:

Code: Select all

docker stop c_deluged

Code: Select all

docker rm c_deluged

Code: Select all

docker rmi sinaptika/deluged

Code: Select all

rm -rf ~/deluge-temp
User avatar
wgstarks
Member
Member
Posts: 26
Joined: Thu Jun 29, 2017 11:06 pm
Location: North Carolina USA

Re: tracker error- operation cancelled

Post by wgstarks »

Tvich wrote:What image do you use for deluge? Where did you get it?
How are openvpn and privoxy set up? Also in a container?
What I would do:
Pull a different image and run it without vpn, just to confirm, that something is wrong with your vpn setting :)

Use ssh to access unraid:
Stop the container:

Code: Select all

docker stop container_name
If you don't know the name of the container, run

Code: Select all

docker ps
find the correct container and then stop it.
Above can probably also be done from the unraid web interface ?

Now run this, It should not take long on a normal internet connection, the image is 28MB :

Code: Select all

mkdir ~/deluge-test

Code: Select all

docker pull sinaptika/deluged

Code: Select all

docker run -d \
--name c_deluged \
-p 50100:50100 \
-p 58846:58846 \
-v ~/deluge-test:/opt/deluge \
sinaptika/deluged
You now have the newest stable deluged running.
Create a username and password for logging in to deluge daemon by running:

Code: Select all

docker exec -it c_deluged deluged-pass.sh
Connect with the client to your unraid host on port 58846. Add a torrent from private tracker. See that everything works fine. Go fix your vpn/proxy settings :)

Cleanup:

Code: Select all

docker stop c_deluged

Code: Select all

docker rm c_deluged

Code: Select all

docker rmi sinaptika/deluged

Code: Select all

rm -rf ~/deluge-temp
Thanks. On the road starting tomorrow but I'll give this a shot as soon as I get back next week and see what happens.
User avatar
wgstarks
Member
Member
Posts: 26
Joined: Thu Jun 29, 2017 11:06 pm
Location: North Carolina USA

Re: tracker error- operation cancelled

Post by wgstarks »

It looks like a problem with the proxy settings. Setting proxy to none allows the torrent to download. What setting should I be using here?
Post Reply