# Deluge not downloading or connecting/finding to peers/seeders

**URL:** https://dietpi.com/forum/t/deluge-not-downloading-or-connecting-finding-to-peers-seeders/13291
**Category:** Troubleshooting
**Created:** [30 May 2022 16:42 UTC](https://dietpi.com/forum/t/deluge-not-downloading-or-connecting-finding-to-peers-seeders/13291 "2022-05-30T16:42:10Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![varunpan](https://dietpi.com/forum/user_avatar/dietpi.com/varunpan/32/1972_2.png) [@varunpan](https://dietpi.com/forum/u/varunpan)
#### Post date: [30 May 2022 16:42 UTC](https://dietpi.com/forum/t/deluge-not-downloading-or-connecting-finding-to-peers-seeders/13291/1 "2022-05-30T16:42:11Z")

</div>

#### Required Information

root@DietPi:~# cat /boot/dietpi/.version  
G\_DIETPI\_VERSION\_CORE=8  
G\_DIETPI\_VERSION\_SUB=5  
G\_DIETPI\_VERSION\_RC=1  
G\_GITBRANCH=‘master’  
G\_GITOWNER=‘MichaIng’

root@DietPi:~# echo $G\_DISTRO\_NAME $G\_RASPBIAN  
bullseye 1

root@DietPi:~# uname -a  
Linux DietPi 5.15.32-v7l+ #1538 SMP Thu Mar 31 19:39:41 BST 2022 armv7l GNU/Linux

root@DietPi:~# echo $G\_HW\_MODEL\_NAME  
RPi 4 Model B (armv7l)

root@DietPi:~# deluged --version  
deluged 2.0.3  
libtorrent: 1.2.9.0  
Python: 3.9.2  
OS: Linux 5.15.32-v7l+

When I load a torrent, it shows 0 seeders, peers and does not connect to anyone. I know the torrent had over 100 seeders and peers. PLEASE HELP! Im not sure where to start with this issue. I have googled but im not sure what I am looking for.

I just refreshed installed dietpi on my Pi and installed and setup deluge. I made sure that the Debian-deluged user in the dietpi, and root group just to make sure there isn’t a permission issue. Also the chmod for the download directory is set to 0777 for the same reason. I also checked that the pi is connected to the internet and there is no firewall setup that would block the traffic. I also forwarded the 6881 port on my router to make sure it isn’t getting blocked.

I am connected to a windscribe vpn using wireguard conf file. However, deluge did not work when I took down the wireguard (using wg-quick down wg0).

---

<div class="post-metadata">

### Author: ![varunpan](https://dietpi.com/forum/user_avatar/dietpi.com/varunpan/32/1972_2.png) [@varunpan](https://dietpi.com/forum/u/varunpan)
#### Post date: [30 May 2022 20:16 UTC](https://dietpi.com/forum/t/deluge-not-downloading-or-connecting-finding-to-peers-seeders/13291/2 "2022-05-30T20:16:25Z")

</div>

I was able to fix the issue by using a random incoming port.

I realized that the External IP was showing as N/A and found the following forum post that explained that there is an issue when NOT using a random incoming port: [Deluge 2.0.3 not able to get to network, 1.3.15 was working - Deluge Forum](https://forum.deluge-torrent.org/viewtopic.php?t=55691)

---

<div class="post-metadata">

### Author: ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)
#### Post date: [31 May 2022 06:00 UTC](https://dietpi.com/forum/t/deluge-not-downloading-or-connecting-finding-to-peers-seeders/13291/3 "2022-05-31T06:00:11Z")

</div>

Nasty, I’ll try to replicate.

Probably it’s this bug (seems upstream) where the listening IPs are concatenated falsely. Just strange that it survived so long without fix then: [https://bugs.debian.org/1000456](https://bugs.debian.org/1000456)

Could you try to apply this change to the Python script and see whether then defining an explicit port (range) works?