starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

-IP-address- "was blocked due to your IP filter" when not using any filter #153

New issue

Closed

opened 2026-02-21 14:54:34 -05:00 by deekerman · 9 comments

deekerman commented

2026-02-21 14:54:34 -05:00

Owner

Originally created by @KalleAnka on GitHub (Oct 20, 2012).

I'm seeing blocks every minute in the execution log. Sometimes it can be up to ten minutes between blocks, sometimes under a minute.

IP-filter is not checked under Options-->Connection-->IP Filtering.

Running qBittorrent v3.0.6 on Windows 2003 x64 SP2.
Have seen this since 2.9.7.

Have tried to check the checkbox, apply, uncheck, apply. No difference.

There is a similar bug report on launchpad: https://bugs.launchpad.net/qbittorrent/+bug/962911

Originally created by @KalleAnka on GitHub (Oct 20, 2012). I'm seeing blocks every minute in the execution log. Sometimes it can be up to ten minutes between blocks, sometimes under a minute. IP-filter is not checked under Options-->Connection-->IP Filtering. Running qBittorrent v3.0.6 on Windows 2003 x64 SP2. Have seen this since 2.9.7. Have tried to check the checkbox, apply, uncheck, apply. No difference. There is a similar bug report on launchpad: https://bugs.launchpad.net/qbittorrent/+bug/962911

deekerman closed this issue

2026-02-21 14:54:36 -05:00

deekerman commented

2026-02-21 14:54:40 -05:00

Author

Owner

@General-TerroR commented on GitHub (Nov 9, 2012):

Same happening on my Windows 2003 R2 x86 SP2 along with another bug.

@General-TerroR commented on GitHub (Nov 9, 2012): Same happening on my Windows 2003 R2 x86 SP2 along with another bug.

deekerman commented

2026-02-21 14:54:40 -05:00

Author

Owner

@gandalftools commented on GitHub (Dec 25, 2012):

Same Win Xp 3.0.6.

@gandalftools commented on GitHub (Dec 25, 2012): Same Win Xp 3.0.6.

deekerman commented

2026-02-21 14:54:40 -05:00

Author

Owner

@epicgit commented on GitHub (Feb 9, 2013):

This bug is critical is blocking my connections!!!

http://imgly.net/iiM

@epicgit commented on GitHub (Feb 9, 2013): This bug is critical is blocking my connections!!! http://imgly.net/iiM

deekerman commented

2026-02-21 14:54:40 -05:00

Author

Owner

@tekko commented on GitHub (Feb 9, 2013):

try http://qbforums.shiki.hu/index.php?topic=1580.msg4904#msg4904

@tekko commented on GitHub (Feb 9, 2013): try http://qbforums.shiki.hu/index.php?topic=1580.msg4904#msg4904

deekerman commented

2026-02-21 14:54:40 -05:00

Author

Owner

@epicgit commented on GitHub (Feb 9, 2013):

Hi tekko
I don’t have any loopback in the blocked list.

At the qBittorrent.conf (brand new installation)

[Preferences]
...
IPFilter\Enabled=false
...
IPFilter\File=

...

@epicgit commented on GitHub (Feb 9, 2013): Hi tekko I don’t have any loopback in the blocked list. At the qBittorrent.conf (brand new installation) [Preferences] ... IPFilter\Enabled=false ... IPFilter\File= ...

deekerman commented

2026-02-21 14:54:40 -05:00

Author

Owner

@humpity commented on GitHub (Apr 18, 2013):

http://qbforums.shiki.hu/index.php?topic=1810.0
Quote from: Dayman:
"Libtorrent automatically blocks peers which send bad data or attempt to take slots by opening a connection and sending nothing."

@humpity commented on GitHub (Apr 18, 2013): http://qbforums.shiki.hu/index.php?topic=1810.0 Quote from: Dayman: "Libtorrent automatically blocks peers which send bad data or attempt to take slots by opening a connection and sending nothing."

deekerman commented

2026-02-21 14:54:40 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Apr 21, 2013):

And a bit more explanation from the libtorrent author himself(from a bug I created):

There are many reasons peers are blocked. peers that are banned are not allowed to connect again, so they're blocked. This is probably the case you're seeing. There are other ways of blocking peers, other than the ip filter. For instance, if you disable utp or tcp, if you're running over i2p and a non-i2p connection tries to connect, if you're using a proxy and disallow connections that circumvent it, etc.

Taken from this: https://code.google.com/p/libtorrent/issues/detail?id=464&start=100

To sum it up. This isn't a bug. Some peers intentionally send bad data in order to disrupt the downloading of a certain torrent. These peers are automatically blocked and there's nothing we can do about it. It shouldn't have any negative impact on the health of a torrent.

@sledgehammer999 commented on GitHub (Apr 21, 2013): And a bit more explanation from the libtorrent author himself(from a bug I created): > There are many reasons peers are blocked. peers that are banned are not allowed to connect again, so they're blocked. This is probably the case you're seeing. There are other ways of blocking peers, other than the ip filter. For instance, if you disable utp or tcp, if you're running over i2p and a non-i2p connection tries to connect, if you're using a proxy and disallow connections that circumvent it, etc. Taken from this: https://code.google.com/p/libtorrent/issues/detail?id=464&start=100 To sum it up. This isn't a bug. Some peers intentionally send bad data in order to disrupt the downloading of a certain torrent. These peers are automatically blocked and there's nothing we can do about it. It shouldn't have any negative impact on the health of a torrent.

deekerman commented

2026-02-21 14:54:40 -05:00

Author

Owner

@5moufl commented on GitHub (Jun 28, 2020):

I don’t want to open a new issue for this question: could the message be more clear with details about why a particular IP was blocked (reason and related torrent)?

@5moufl commented on GitHub (Jun 28, 2020): I don’t want to open a new issue for this question: could the message be more clear with details about why a particular IP was blocked (reason and related torrent)?

deekerman commented

2026-02-21 14:54:40 -05:00

Author

Owner

@FranciscoPombal commented on GitHub (Jun 28, 2020):

I don’t want to open a new issue for this question: could the message be more clear with details about why a particular IP was blocked (reason and related torrent)?

Maybe, but please don't necro old closed threads, open a new feature request for that.

@FranciscoPombal commented on GitHub (Jun 28, 2020): > I don’t want to open a new issue for this question: could the message be more clear with details about why a particular IP was blocked (reason and related torrent)? Maybe, but please don't necro old closed threads, open a new feature request for that.

deekerman referenced this issue

2026-02-21 15:20:49 -05:00

Search in searched items #842

deekerman referenced this issue

2026-02-21 22:12:32 -05:00

Editing search results #11996