Hi, I had been running an old version of Deluge for several years without issue but earlier this year I updated to 2.1.1 and ever since - none of my torrents will do anything. They say downloading but no traffic is moved at all, lower right corner says "Port Issue"
I am not using any P2P features just torrents, so port forwarding and such should not be necessary. I noticed the default setting for incoming and outgoing ports was set to random and the interface boxes are null. What needs to be done here? Every post I read about ports were all associated with VPNs and I am not using one.
Help?
Torrenting No Longer Works After Upgrade (Port Issue)
-
- New User
- Posts: 3
- Joined: Fri Oct 04, 2024 9:27 pm
Re: Torrenting No Longer Works After Upgrade (Port Issue)
The port issue is likely unrelated to your downloads not working, that is signifying an open port for incoming connections. Because you aren't actually doing any torrenting, I'm not sure if this is even true or not. I would suggest you use the test active port button to check this, if this tests OK then that error is irrelevant.
What is usually the cause here is that there are permissions or disk free space issues, basically deluge is unable to write to the disk.
Without any context as to what behavior you're seeing besides "it's not working" - there's not much I can speculate on.
Does the torrent download for a second or two when you start and then stall? Do you see any announce traffic in the trackers information? Have you tried checking the logs? How are you running Deluge - Docker? Natively? Your OS is listed as windows, is that where Deluge is running or are you using the thin client to a server?
There's tons of details that would help us better assist you in figuring out this issue, but you unfortunately provided only that you aren't using a VPN and "torrenting doesn't work" :(
I would suggest you not only give us the context, but check the logs. If you do not know how to log - simply running Deluge (or the daemon if remote) with the additional "-l C:\logfile.txt -L DEBUG" flags should provide you with tons of logging around your instance and thus some form of an error in all likelihood.
What is usually the cause here is that there are permissions or disk free space issues, basically deluge is unable to write to the disk.
Without any context as to what behavior you're seeing besides "it's not working" - there's not much I can speculate on.
Does the torrent download for a second or two when you start and then stall? Do you see any announce traffic in the trackers information? Have you tried checking the logs? How are you running Deluge - Docker? Natively? Your OS is listed as windows, is that where Deluge is running or are you using the thin client to a server?
There's tons of details that would help us better assist you in figuring out this issue, but you unfortunately provided only that you aren't using a VPN and "torrenting doesn't work" :(
I would suggest you not only give us the context, but check the logs. If you do not know how to log - simply running Deluge (or the daemon if remote) with the additional "-l C:\logfile.txt -L DEBUG" flags should provide you with tons of logging around your instance and thus some form of an error in all likelihood.
-
- New User
- Posts: 3
- Joined: Fri Oct 04, 2024 9:27 pm
Re: Torrenting No Longer Works After Upgrade (Port Issue)
The active port is 0, so when tested I just get an exclamation in a black triangle.
Disk is not full, plenty of room left and the directory is valid.
This is all it does and will never download even 0.01% - not even the clear text names just the hashes. Deluge is native on Win10.
0 trackers load.
If you tell me the details you need I will provide, but nothing has changed other than the version of Deluge.
I will attempt posting the logs if I can retrieve them.
Disk is not full, plenty of room left and the directory is valid.
This is all it does and will never download even 0.01% - not even the clear text names just the hashes. Deluge is native on Win10.
0 trackers load.
If you tell me the details you need I will provide, but nothing has changed other than the version of Deluge.
I will attempt posting the logs if I can retrieve them.
Last edited by PinkFloydEffect on Fri Oct 04, 2024 10:02 pm, edited 1 time in total.
Re: Torrenting No Longer Works After Upgrade (Port Issue)
This would lead me to believe you are using public trackers with magnets, and if you have DHT, PEX, etc all turned off, this is going to not be able to resolve the magnet to any peers.
I told you what information would be helpful, and if you're going to provide screenshots with no meaningful data - like the stuff I listed - there is really no point in posting them.
Also there is no "Port 0" - it is set to random and that is OUTGOING port. Port issue is for INCOMING port - like I said. Yours is set to 6881 in your screenshot if you uncheck the random box.
I told you what information would be helpful, and if you're going to provide screenshots with no meaningful data - like the stuff I listed - there is really no point in posting them.
Also there is no "Port 0" - it is set to random and that is OUTGOING port. Port issue is for INCOMING port - like I said. Yours is set to 6881 in your screenshot if you uncheck the random box.
-
- New User
- Posts: 3
- Joined: Fri Oct 04, 2024 9:27 pm
Re: Torrenting No Longer Works After Upgrade (Port Issue)
I do not use magnet links but I copy and paste the hashes into Deluge, is that any different?
Yes, you did, and I provided everything except the logs. I am trying to obtain them as I already stated.
In that case 6881 is not working than. If you uncheck random it still says 0 and fails the test.
These are all enabled, cannot find the others you mentioned.
Yes, you did, and I provided everything except the logs. I am trying to obtain them as I already stated.
In that case 6881 is not working than. If you uncheck random it still says 0 and fails the test.
These are all enabled, cannot find the others you mentioned.
Last edited by PinkFloydEffect on Fri Oct 04, 2024 11:07 pm, edited 5 times in total.
-
- New User
- Posts: 3
- Joined: Fri Oct 04, 2024 9:27 pm
Re: Torrenting No Longer Works After Upgrade (Port Issue)
I am unable to get the flags to work. What am I doing wrong? I am still migrating away from GUI unfortunately and do not know the proper syntax.
PS C:\windows\system32> CD C:\Program_Files\Deluge
CD : Cannot find path 'C:\Program_Files\Deluge' because it does not exist.
At line:1 char:1
+ CD C:\Program_Files\Deluge
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (C:\Program_Files\Deluge:String) [Set-Location], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.SetLocationCommand
PS C:\windows\system32> CD C:\ProgramFiles\Deluge
CD : Cannot find path 'C:\ProgramFiles\Deluge' because it does not exist.
At line:1 char:1
+ CD C:\ProgramFiles\Deluge
+ ~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (C:\ProgramFiles\Deluge:String) [Set-Location], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.SetLocationCommand
PS C:\windows\system32> CD C:\Program Files\Deluge
Set-Location : A positional parameter cannot be found that accepts argument 'Files\Deluge'.
At line:1 char:1
+ CD C:\Program Files\Deluge
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Set-Location], ParameterBindingException
+ FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.SetLocationComman
PS C:\windows\system32> CD C:\Program_Files\Deluge
CD : Cannot find path 'C:\Program_Files\Deluge' because it does not exist.
At line:1 char:1
+ CD C:\Program_Files\Deluge
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (C:\Program_Files\Deluge:String) [Set-Location], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.SetLocationCommand
PS C:\windows\system32> CD C:\ProgramFiles\Deluge
CD : Cannot find path 'C:\ProgramFiles\Deluge' because it does not exist.
At line:1 char:1
+ CD C:\ProgramFiles\Deluge
+ ~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (C:\ProgramFiles\Deluge:String) [Set-Location], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.SetLocationCommand
PS C:\windows\system32> CD C:\Program Files\Deluge
Set-Location : A positional parameter cannot be found that accepts argument 'Files\Deluge'.
At line:1 char:1
+ CD C:\Program Files\Deluge
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Set-Location], ParameterBindingException
+ FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.SetLocationComman
Last edited by PinkFloydEffect on Fri Oct 04, 2024 11:07 pm, edited 1 time in total.
Re: Torrenting No Longer Works After Upgrade (Port Issue)
What do you mean you copy paste the hashes into Deluge, you either need to have a .torrent file - which would generally have some sort of tracker in it that would show up in your Trackers list, or it would be a magnet and generally use DHT/PEX.
What you are showing here shows a 0 size and no trackers that I can see, which leads me to believe there is no torrent file associated with any of these. The infohash does not contain tracker or peer information."Copy pasting the hash" - if you mean infohash, is not how torrents work.
Also, read the error in your PowerShell. You need to check your path. Are you just guessing the paths? The first one is probably correct. It has a space - so you will need to put quotations around C:\....\deluge.exe -and the parameters outside of them - but it seems like the issue is clear already.
What you are showing here shows a 0 size and no trackers that I can see, which leads me to believe there is no torrent file associated with any of these. The infohash does not contain tracker or peer information."Copy pasting the hash" - if you mean infohash, is not how torrents work.
Also, read the error in your PowerShell. You need to check your path. Are you just guessing the paths? The first one is probably correct. It has a space - so you will need to put quotations around C:\....\deluge.exe -and the parameters outside of them - but it seems like the issue is clear already.
-
- New User
- Posts: 3
- Joined: Fri Oct 04, 2024 9:27 pm
Re: Torrenting No Longer Works After Upgrade (Port Issue)
If you look on torrent sites there is a file hash listed in text within the description somewhere. I simply copy it to clipboard. Go to add infohash in Deluge and paste it from clipboard, click add and your done. No link was used and no torrent file was downloaded. I have literally been doing this for over a decade to avoid downloading anything at all from torrent sites. The infohash has always pulled all the tracker information in automagically, the name would change from the infohash to the file name once it connected to 1 peer/tracker.
I am not guessing the directory, I migrated to it using the gui and copied it from the explorer bar at the top. The closest I got was this:
PS C:\windows\system32> CD C:\Program Files\Deluge
Set-Location : A positional parameter cannot be found that accepts argument 'Files\Deluge'.
At line:1 char:1
+ CD C:\Program Files\Deluge
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Set-Location], ParameterBindingException
+ FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.SetLocationCommand
I am not guessing the directory, I migrated to it using the gui and copied it from the explorer bar at the top. The closest I got was this:
PS C:\windows\system32> CD C:\Program Files\Deluge
Set-Location : A positional parameter cannot be found that accepts argument 'Files\Deluge'.
At line:1 char:1
+ CD C:\Program Files\Deluge
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Set-Location], ParameterBindingException
+ FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.SetLocationCommand
Re: Torrenting No Longer Works After Upgrade (Port Issue)
I'm aware of what the SHA-1 infohash is used for, and you would typically want to use the full magnet URL to add this. You can copy this from the site without "downloading anything" - however I'm not sure what you think you are protecting by not downloading from torrent sites while simultaneously being in the swarms.
As I said, this is not working for you. Given that I have no further information, I can either deduce that
1. these infohashes are associated with specific trackers and not on the DHT and thus you are not retrieving metadata. This would require you to use the actual magnet URL which would contain further information perhaps, or the .torrent file which would contain trackers or
2. You're deluge instance is bound to a bad interface or blocked from connectivity somehow. or lastly
3. You are mistakenly assuming that every infohash can simply be added to deluge in this way. This is not the case. The torrent would have to be on the DHT for this to be functional.
I'm not sure what the case may be, but I do know that what you are doing is not working and there are easy ways to test whether it is your client, the torrent you're adding or something else.
1. Go try and download a ubuntu (or any linux distro) ISO via a .torrent file. DOWNLOAD THE TORRENT FILE. See if there is connectivity within the client at all.
2. Turn on logging.
3. Download the .torrent file for one of these torrents if 1. funtions and see if it works.
4. Check the logs for what is different, errors, warnings, etc. Surrounding the failing download.
As I said, this is not working for you. Given that I have no further information, I can either deduce that
1. these infohashes are associated with specific trackers and not on the DHT and thus you are not retrieving metadata. This would require you to use the actual magnet URL which would contain further information perhaps, or the .torrent file which would contain trackers or
2. You're deluge instance is bound to a bad interface or blocked from connectivity somehow. or lastly
3. You are mistakenly assuming that every infohash can simply be added to deluge in this way. This is not the case. The torrent would have to be on the DHT for this to be functional.
I'm not sure what the case may be, but I do know that what you are doing is not working and there are easy ways to test whether it is your client, the torrent you're adding or something else.
1. Go try and download a ubuntu (or any linux distro) ISO via a .torrent file. DOWNLOAD THE TORRENT FILE. See if there is connectivity within the client at all.
2. Turn on logging.
3. Download the .torrent file for one of these torrents if 1. funtions and see if it works.
4. Check the logs for what is different, errors, warnings, etc. Surrounding the failing download.
Re: Torrenting No Longer Works After Upgrade (Port Issue)
My guy, if your path has a space in it you have to surround the entire path with quotation marks. That's been the case for command line forever.PinkFloydEffect wrote: ↑Fri Oct 04, 2024 11:23 pm If you look on torrent sites there is a file hash listed in text within the description somewhere. I simply copy it to clipboard. Go to add infohash in Deluge and paste it from clipboard, click add and your done. No link was used and no torrent file was downloaded. I have literally been doing this for over a decade to avoid downloading anything at all from torrent sites. The infohash has always pulled all the tracker information in automagically, the name would change from the infohash to the file name once it connected to 1 peer/tracker.
I am not guessing the directory, I migrated to it using the gui and copied it from the explorer bar at the top. The closest I got was this:
PS C:\windows\system32> CD C:\Program Files\Deluge
Set-Location : A positional parameter cannot be found that accepts argument 'Files\Deluge'.
At line:1 char:1
+ CD C:\Program Files\Deluge
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Set-Location], ParameterBindingException
+ FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.SetLocationCommand
Untitled.jpg
CD "C:\Program Files\Deluge"
