tracker error- operation cancelled
tracker error- operation cancelled
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.
Re: tracker error- operation cancelled
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
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
Re: tracker error- operation cancelled
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?
Re: tracker error- operation cancelled
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.
Re: tracker error- operation cancelled
Quote from IPTorrents Forum-
Will Deluge work without DHT and PEX? I don't know what they are so don't have a clue what this means.Probably want a different client here. You need DHT and PEX disabled here and you'll need those at that site.
Re: tracker error- operation cancelled
Deluge accounts for probably 30% of traffic on iptorrents, if there were a problem with deluge, everyone would be "reporting in".wgstarks wrote:Quote from IPTorrents Forum-Will Deluge work without DHT and PEX? I don't know what they are so don't have a clue what this means.Probably want a different client here. You need DHT and PEX disabled here and you'll need those at that site.
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?
Re: tracker error- operation cancelled
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.
Re: tracker error- operation cancelled
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:
If you don't know the name of the container, run
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 :
You now have the newest stable deluged running.
Create a username and password for logging in to deluge daemon by running:
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:
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
Code: Select all
docker ps
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
Create a username and password for logging in to deluge daemon by running:
Code: Select all
docker exec -it c_deluged deluged-pass.sh
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
Re: tracker error- operation cancelled
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.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:If you don't know the name of the container, runCode: Select all
docker stop container_name
find the correct container and then stop it.Code: Select all
docker ps
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
You now have the newest stable deluged running.Code: Select all
docker run -d \ --name c_deluged \ -p 50100:50100 \ -p 58846:58846 \ -v ~/deluge-test:/opt/deluge \ sinaptika/deluged
Create a username and password for logging in to deluge daemon by running: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 settingsCode: Select all
docker exec -it c_deluged deluged-pass.sh
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
Re: tracker error- operation cancelled
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?