starred/qBittorrent

Fork 0

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

qBittorrent-nox 4.6 i2p php tracker does not work and i2p peer list does not show in GUI #15078

New issue

Open

opened 2026-02-22 01:45:02 -05:00 by deekerman · 12 comments

deekerman commented

2026-02-22 01:45:02 -05:00

Owner

Originally created by @sp117f on GitHub (Oct 26, 2023).

qBittorrent & operating system versions

qBittorrent-nox: 4.6
OS: Unbuntu Desktop 22.04
Qt: 6.6.0
Libtorrent: 2.0.9.0

What is the problem?

i2p trackers that end with .php do not work. I am getting "invalid key".

EDIT: I am using i2pd if that matters.

Also, I do not see any peers on the Web GUI, but there is clearly downloading activity.

Steps to reproduce

Add an i2p tracker that ends with .php

Additional context

No response

Log(s) & preferences file(s)

No response

Originally created by @sp117f on GitHub (Oct 26, 2023). ### qBittorrent & operating system versions qBittorrent-nox: 4.6 OS: Unbuntu Desktop 22.04 Qt: 6.6.0 Libtorrent: 2.0.9.0 ### What is the problem? i2p trackers that end with .php do not work. I am getting "invalid key". EDIT: I am using i2pd if that matters. Also, I do not see any peers on the Web GUI, but there is clearly downloading activity. ### Steps to reproduce 1. Add an i2p tracker that ends with .php ![image](https://github.com/qbittorrent/qBittorrent/assets/149112407/92c79802-aeca-411a-a865-4e580deb69da) ### Additional context _No response_ ### Log(s) & preferences file(s) _No response_

deekerman added the

Confirmed bug

I2P

Has workaround

labels

2026-02-22 01:45:02 -05:00

deekerman commented

2026-02-22 01:45:07 -05:00

Author

Owner

@Pat-JK commented on GitHub (Oct 26, 2023):

i've been having this issue too. didn't realise the issue was related to .php announce urls but you seem to be correct, as those are the same kinds of trackers i'm having issues with

@Pat-JK commented on GitHub (Oct 26, 2023): i've been having this issue too. didn't realise the issue was related to .php announce urls but you seem to be correct, as those are the same kinds of trackers i'm having issues with

deekerman commented

2026-02-22 01:45:14 -05:00

Author

Owner

@luzpaz commented on GitHub (Oct 27, 2023):

@Pat-JK full version info that you can reproduce with ?

@luzpaz commented on GitHub (Oct 27, 2023): @Pat-JK full version info that you can reproduce with ?

deekerman commented

2026-02-22 01:45:14 -05:00

Author

Owner

@Pat-JK commented on GitHub (Oct 27, 2023):

It happens on every torrent using i2p. I don't have mixed mode enabled but it still occurs whether on or off.

Trackers whose announce url ends with announce.php (example: http://tracker2.postman.i2p/announce.php) result in "cannot reach peer" or "timed out" and a not working status, despite the tracker being up. if the url ends with /a (example: http://opentracker.dg2.i2p/a) it works as expected.

All trackers previously were working fine for me while using 4.6RC2, but the day 4.6.0 released the issue started happening. Oddly, the issue started before I actually updated to 4.6 final, and switching to RC2 doesn't resolve it.

EDIT: Using I2Pd 2.49.0

@Pat-JK commented on GitHub (Oct 27, 2023): It happens on every torrent using i2p. I don't have mixed mode enabled but it still occurs whether on or off. Trackers whose announce url ends with announce.php (example: http://tracker2.postman.i2p/announce.php) result in "cannot reach peer" or "timed out" and a not working status, despite the tracker being up. if the url ends with /a (example: http://opentracker.dg2.i2p/a) it works as expected. All trackers previously were working fine for me while using 4.6RC2, but the day 4.6.0 released the issue started happening. Oddly, the issue started before I actually updated to 4.6 final, and switching to RC2 doesn't resolve it. EDIT: Using I2Pd 2.49.0

deekerman commented

2026-02-22 01:45:14 -05:00

Author

Owner

@k4r4b3y commented on GitHub (Oct 28, 2023):

I started having the same problem as in the original post of this issue thread, since a week ago. I am unable to leech/seed torrents from Postman's tracker. But other I2P trackers without a php ending seems to work (able to seed/leech).

I am using i2pd package from debian/trixie repos, and I had this bug under qbittorrent-nox 4.6RC and qbittorrent-nox 4.6 (proper release).

Also, this issue thread seems to be relevant: https://github.com/qbittorrent/qBittorrent/issues/19625#issue-1904424597

Edit: "but the day 4.6.0 released the issue started happening." <--- this has exactly been my experience, as well.

@k4r4b3y commented on GitHub (Oct 28, 2023): I started having the same problem as in the original post of this issue thread, since a week ago. I am unable to leech/seed torrents from Postman's tracker. But other I2P trackers without a php ending seems to work (able to seed/leech). I am using i2pd package from debian/trixie repos, and I had this bug under qbittorrent-nox 4.6RC and qbittorrent-nox 4.6 (proper release). Also, this issue thread seems to be relevant: https://github.com/qbittorrent/qBittorrent/issues/19625#issue-1904424597 Edit: "but the day 4.6.0 released the issue started happening." <--- this has _exactly_ been my experience, as well.

deekerman commented

2026-02-22 01:45:15 -05:00

Author

Owner

@k4r4b3y commented on GitHub (Dec 2, 2023):

Are there any updates to this issue? Is the cause of the bug within qbittorrent, or is it caused from the libtorrent-rasterbar2.0?

@k4r4b3y commented on GitHub (Dec 2, 2023): Are there any updates to this issue? Is the cause of the bug within qbittorrent, or is it caused from the libtorrent-rasterbar2.0?

deekerman commented

2026-02-22 01:45:15 -05:00

Author

Owner

@k4r4b3y commented on GitHub (Jan 14, 2024):

Hello. I stumbled upon a solution on http://discuss.i2p forum. There, is a thread that explains how to setup qbittorrent 4.6 with i2p. Once I deployed the changes from that thread, my qbittorrent 4.6.2 was operational with i2p torrents.

Here is what I changed on my qbittorrent 4.6.2 (installed from debian trixie repos):

On qbittorrent settings below:
1: 127.0.0.1
2: 7656
3: 4444

2nd option is from i2pd's configuration. It is the SAM port of the i2pd daemon. 3rd option is also from i2pd's configuration. It is the http proxy port that i2pd daemon provides.

Then, make sure to checkmark ALL the options that are visible in the below screenshot:

Now, on the qbittorrent settings > advanced, also UN-CHECK Server-side request forgery (SSRF) mitigation option.

After these changes, restart your system, and you will have all the i2p trackers (including the ones ending in .php URLs) functional again.

@sp117f @Pat-JK can you verify if these works for you as well? If so, then, we can close this issue.

@k4r4b3y commented on GitHub (Jan 14, 2024): Hello. I stumbled upon a solution on http://discuss.i2p forum. There, is a thread that explains how to setup qbittorrent 4.6 with i2p. Once I deployed the changes from that thread, my qbittorrent 4.6.2 was operational with i2p torrents. Here is what I changed on my qbittorrent 4.6.2 (installed from debian trixie repos): On qbittorrent settings below: 1: 127.0.0.1 2: 7656 3: 4444 2nd option is from i2pd's configuration. It is the SAM port of the i2pd daemon. 3rd option is also from i2pd's configuration. It is the http proxy port that i2pd daemon provides. Then, make sure to checkmark ALL the options that are visible in the below screenshot: ![01q](https://github.com/qbittorrent/qBittorrent/assets/128297497/a9b65ed3-5442-4727-89ba-5d59dc1e43bf) Now, on the qbittorrent settings > advanced, also UN-CHECK **Server-side request forgery (SSRF) mitigation** option. ![02q](https://github.com/qbittorrent/qBittorrent/assets/128297497/2459a6f9-fbcd-4473-aaea-90fae1f562cd) After these changes, restart your system, and you will have all the i2p trackers (including the ones ending in .php URLs) functional again. @sp117f @Pat-JK can you verify if these works for you as well? If so, then, we can close this issue.

deekerman commented

2026-02-22 01:45:15 -05:00

Author

Owner

@fbievan commented on GitHub (Sep 12, 2024):

Hello. I stumbled upon a solution on http://discuss.i2p forum. There, is a thread that explains how to setup qbittorrent 4.6 with i2p. Once I deployed the changes from that thread, my qbittorrent 4.6.2 was operational with i2p torrents.

Here is what I changed on my qbittorrent 4.6.2 (installed from debian trixie repos):

On qbittorrent settings below: 1: 127.0.0.1 2: 7656 3: 4444

2nd option is from i2pd's configuration. It is the SAM port of the i2pd daemon. 3rd option is also from i2pd's configuration. It is the http proxy port that i2pd daemon provides.

Then, make sure to checkmark ALL the options that are visible in the below screenshot:

Now, on the qbittorrent settings > advanced, also UN-CHECK Server-side request forgery (SSRF) mitigation option.

After these changes, restart your system, and you will have all the i2p trackers (including the ones ending in .php URLs) functional again.

@sp117f @Pat-JK can you verify if these works for you as well? If so, then, we can close this issue.

I am also experencing this issue... the solution as described above does not fix the issue of the peer list not showing any I2P peers, you can also test this by turning on the WebUI in a desktop qbitorrent, looking at a torrent, and then looking at that same Peer list in the WebUI.... I think the webUI is misssing some type of dependency or something?

This solution would not be acceptable for people who crosseed with mixed mode, using both a proxy and I2P connection, like I do.

@fbievan commented on GitHub (Sep 12, 2024): > Hello. I stumbled upon a solution on http://discuss.i2p forum. There, is a thread that explains how to setup qbittorrent 4.6 with i2p. Once I deployed the changes from that thread, my qbittorrent 4.6.2 was operational with i2p torrents. > > Here is what I changed on my qbittorrent 4.6.2 (installed from debian trixie repos): > > On qbittorrent settings below: 1: 127.0.0.1 2: 7656 3: 4444 > > 2nd option is from i2pd's configuration. It is the SAM port of the i2pd daemon. 3rd option is also from i2pd's configuration. It is the http proxy port that i2pd daemon provides. > > Then, make sure to checkmark ALL the options that are visible in the below screenshot: ![01q](https://private-user-images.githubusercontent.com/128297497/296551934-a9b65ed3-5442-4727-89ba-5d59dc1e43bf.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjYxNjkyMDAsIm5iZiI6MTcyNjE2ODkwMCwicGF0aCI6Ii8xMjgyOTc0OTcvMjk2NTUxOTM0LWE5YjY1ZWQzLTU0NDItNDcyNy04OWJhLTVkNTlkYzFlNDNiZi5qcGc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwOTEyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDkxMlQxOTIxNDBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1hOWIyYmZiMDkxYmU1Zjg4YzY2ODZkZGZlZjc5ZWU4MjE1YWNhZjY0NGJjNmU1NGRmMjYyOGExMDczNTVjMjA4JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.ymTqkE9iZvXNcLYSA0nVpbpOyKkaSyFnwf5eWd9Cr0c) > > Now, on the qbittorrent settings > advanced, also UN-CHECK **Server-side request forgery (SSRF) mitigation** option. ![02q](https://private-user-images.githubusercontent.com/128297497/296552039-2459a6f9-fbcd-4473-aaea-90fae1f562cd.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjYxNjkyMDAsIm5iZiI6MTcyNjE2ODkwMCwicGF0aCI6Ii8xMjgyOTc0OTcvMjk2NTUyMDM5LTI0NTlhNmY5LWZiY2QtNDQ3My1hYWVhLTkwZmFlMWY1NjJjZC5qcGc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwOTEyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDkxMlQxOTIxNDBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iZTAwMjFkODhmNDg1Mjk5NGVmNjUxMjVjZmUxZDNiY2Q1YmRiMzExN2FiMWRhM2VlNzUwNWViZTgxZDhlY2ZlJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.4QxlamDDqWfJerRhxXpVYFsiVy5WWbJmfZPF4UxzRgk) > > After these changes, restart your system, and you will have all the i2p trackers (including the ones ending in .php URLs) functional again. > > @sp117f @Pat-JK can you verify if these works for you as well? If so, then, we can close this issue. I am also experencing this issue... the solution as described above does not fix the issue of the peer list not showing any I2P peers, you can also test this by turning on the WebUI in a desktop qbitorrent, looking at a torrent, and then looking at that same Peer list in the WebUI.... I think the webUI is misssing some type of dependency or something? This solution would not be acceptable for people who crosseed with mixed mode, using both a proxy and I2P connection, like I do.

deekerman commented

2026-02-22 01:45:15 -05:00

Author

Owner

@fbievan commented on GitHub (Sep 12, 2024):

Actually it seems doing the above solution, does fix the issue, forcing a reannouncement, and returning back to my normal settings, works... even survived a full restart...

tested on qBitTorrent v4.6.6

@fbievan commented on GitHub (Sep 12, 2024): Actually it seems doing the above solution, does fix the issue, forcing a reannouncement, and returning back to my normal settings, works... even survived a full restart... tested on qBitTorrent v4.6.6

deekerman commented

2026-02-22 01:45:15 -05:00

Author

Owner

@fbievan commented on GitHub (Sep 12, 2024):

Actually it seems doing the above solution, does fix the issue, forcing a reannouncement, and returning back to my normal settings, works... even survived a full restart...

however, we do need to figure out what causes this condition to happen....

and fix the other issue (no i2p peers showing up in peer list on qbittorrent-nox, which could be it's own seperate issue)

@fbievan commented on GitHub (Sep 12, 2024): > Actually it seems doing the above solution, does fix the issue, forcing a reannouncement, and returning back to my normal settings, works... even survived a full restart... however, we do need to figure out what causes this condition to happen.... and fix the other issue (no i2p peers showing up in peer list on qbittorrent-nox, which could be it's own seperate issue)

deekerman commented

2026-02-22 01:45:15 -05:00

Author

Owner

@fbievan commented on GitHub (Sep 12, 2024):

Actually it seems doing the above solution, does fix the issue, forcing a reannouncement, and returning back to my normal settings, works... even survived a full restart...

however, we do need to figure out what causes this condition to happen....

and fix the other issue (no i2p peers showing up in peer list on qbittorrent-nox, which could be it's own seperate issue)

It looks like webui refers to /api/v2/sync/torrentPeers endpoint, which does not have I2P peers with it... since it directly goes directly to PeerListWidget...

I do not know enough C++ to try to code this...

@fbievan commented on GitHub (Sep 12, 2024): > > Actually it seems doing the above solution, does fix the issue, forcing a reannouncement, and returning back to my normal settings, works... even survived a full restart... > > however, we do need to figure out what causes this condition to happen.... > > and fix the other issue (no i2p peers showing up in peer list on qbittorrent-nox, which could be it's own seperate issue) It looks like webui refers to /api/v2/sync/torrentPeers endpoint, which does not have I2P peers with it... since it directly goes directly to PeerListWidget... I do not know enough C++ to try to code this...

deekerman commented

2026-02-22 01:45:15 -05:00

Author

Owner

@fbievan commented on GitHub (Sep 13, 2024):

I think I'm actually experiencing a different issue

@fbievan commented on GitHub (Sep 13, 2024): I think I'm actually experiencing a different issue

deekerman commented

2026-02-22 01:45:15 -05:00

Author

Owner

@anikey-from-i2p commented on GitHub (Jan 3, 2025):

I think the problem is that there are two different problems reported in one issue. Maybe it is better to create a separate issue for I2P peers not being shown? (The initial author seems to have mixed up the two.)

Also, setting the HTTP proxy is not necessary at all. And all these b32/b64 trackers are ether obsolete or just mirror the ones already listed in human-readable form, so are also not necessary.

@anikey-from-i2p commented on GitHub (Jan 3, 2025): I think the problem is that there are two different problems reported in one issue. Maybe it is better to create a separate issue for I2P peers not being shown? (The initial author seems to have mixed up the two.) Also, setting the HTTP proxy is not necessary at all. And all these b32/b64 trackers are ether obsolete or just mirror the ones already listed in human-readable form, so are also not necessary.