![deluge client not incoming connections deluge client not incoming connections](https://i0.wp.com/www.techjunkie.com/wp-content/uploads/2018/05/deluge-connections.jpg)
#DELUGE CLIENT NOT INCOMING CONNECTIONS TORRENT#
The router needs to forward incoming torrent traffic to your pi based on the network port being used. We don't yet have a range capability but that might be just the job, if we had it, in this case. Regarding your problem, my answer assumed you are using a standard broadband router to connect to the internet.
![deluge client not incoming connections deluge client not incoming connections](http://www.susegeek.com/wp-content/uploads/2008/08/deluge4.png)
ĭoes Deluge only have the option to set a single port for this then? The Rock-on could have multiple ports set, but of course more ports makes for more UX complexity.
![deluge client not incoming connections deluge client not incoming connections](https://www.rapidseedbox.com/wp-content/uploads/Deluge_Unofficial_Guide_022_troubleshooting.png)
will have to use one port and one port only. So maybe we need a rockstor-doc pull request to add a "Rock-ons with write-ups" section for Deluge? And link to that from within the description of the Deluge Rock-on. This was recently done by in the following pull requests:Īlthough that example was a little more extreme as it concerned pre-install config, but still. One way this could go, if it's seen to be worth the effort, would be to have a supporting doc entry. We are also preparing to do a tidy soon where all non fully functional Rock-ons are likely to be pulled. I tried turning firewall off and see if it removes, but it did not work. I don't think this app is worth the exception and it's consequent risks. Ive been seeing the message 'No incoming connections' at the bottom of my Deluge program, but not in the web Deluge. The question is - do we go "double config" route whilst avoiding "-net=host" or go with "-net=host"?īut maybe better to have this double config, even though it's not in keeping with the Rock-on config 'easy' ethos (except in particular examples where it is unavoidable) than to pull the rock-on entirely though. I put in PIAs forward into the incoming ports rage (before that the port was blocked) I also put the TAP windows adapter IP in the Interface section of deluges options, but Im not sure if thats necessary.