Skip to main content


self-hosted i2p+qbittorrent beginner quickstart


This entry was edited (7 months ago)
in reply to xabadak

Interesting, I've been looking for a easier i2p torrent application. Gonna try it out this summer.
in reply to xabadak

I really want to build an i2p router, and have started a couple times, but the lack of control of what goes through my hardware stops me every time. It's a cool project and, sadly, looking more necessary every year.

It's weird I don't have these hang ups for other systems. Running a meshcore node doesn't give me the willies. Just for i2p I worry how much csam is going through my router.

in reply to Fedegenerate

It's true, you never really know what will be going through your router. I guess I just got over it after a few years of struggling with VPNs and port-forwarding. Just felt like the noose was getting tighter, especially after Mullvad stopped providing the feature. My stance is that if I ever knew that such content was going through my PC I would block it, but if it's all encrypted then what can I do? Same reason why I support encrypted messaging apps - they can be used for harm but is that the fault of the tool? Though I recognize it's a complex issue.
in reply to xabadak

Agreed. I'll get over myself one day and build one. For now Airvpn supports port forwarding at an affordable (to me) price, so I let them deal with the moral dilemma.

It's coming though, i2p is where my server is headed, even if I keep a VPN up too.

in reply to Fedegenerate

It's weird that all the tier 1 ISPs have no such worries though.
in reply to Blackmist

It's not weird at all. They're share holder corpos, anti-morality is par for course. Corporations are not our friends.
in reply to xabadak

looks easy enough, will try, thank you.

tbh, looked at the thing some while back and noped out when I saw "java" in there; absolutely irrational, I know - just can't stand the thing. cool that there's an alternative.

in reply to glitching

It's not just the router. The officially recommended I2P torrent client, called I2PSnark, is also in Java and its a pain to get working in Docker. It's not a bad torrent client, just feels like the official I2P tools still don't have great support for modern Linux devops. Now that qBittorrent supports I2P the whole stack feels much more at home.
in reply to xabadak

Might test this out, this looks great. Mullvad is my VPN provider of choice for a lot of reasons, but recently ran into the port forwarding issue so I switched to Proton, a company that I'm very uncomfortable with given their CEO's politics and such. This would let me stick with the former without losing any functionality, if I'm following correctly
in reply to xabadak

This entry was edited (7 months ago)
in reply to shrewdcat

in reply to xabadak

Good info here. You will have to read the author's article to answer your questions, I marked as 'source' above. I did read on a more recent article that I2P can be a little slower than a VPN because, I guess it is decentralized, all those node paths the info has to travel?? Believe me, if something happens to the company that hosts my "lifetime" VPN purchase, I will most likely switch to I2P.
in reply to shrewdcat

It's also slower simply because it's basically a bunch of VPNs running on consumer hardware. Actual VPN providers can provide big powerful servers. This is why I think torrenting is a great fit for the slower speeds of I2P - waiting a little longer for a download is bearable, as opposed to waiting for a webpage to load.
in reply to xabadak

And in terms of torrenting specifically, torrents have to explicitly support I2P. You can't just take any clearnet torrent and expect it to work on I2P.


are you sure about that? for public torrents you just add the postman tracker and done. if libtorrent gets support for DHT over I2P, even that won't be needed

in reply to WhyJiffie

You're right I was thinking about it incorrectly. But I2P peers can only reach other I2P peers though right?
in reply to xabadak

hmm I'm not sure I understand you. qbittorrent allows you to set whether you want to also use I2P or only that, globally for all torrents. but I2P peers who are in mixed mode, they can work as a bridge, getting the pieces from internet peers and redistributing it on the I2P network
in reply to xabadak

A fair warning though, I2P is restricted in some countries.


And that list is almost identical with Naughty-no-gift-from-Santa list.

in reply to xabadak

Is there a way I can do this without docker? I just run Qbit on my regular windows computer and don't wanna delve into Docker. Would Love to share the 5k+ torrents I have on the I2p network.
in reply to xabadak

Thank you! I just randomly found your guide in another Lemmy post and this kind of setup has been in my to-do list after I became "pro" with gluetun and qbitorrent (inside Docker) and thought the same could be done for i2pd but haven't had the time.

I have some questions

  1. I have been very happy about qbitorrent finally opening to i2p but recently found out that because it is using libtorrent it doesn't support DHT for i2p (while the official i2psnark client does). Don't you think is better at this point to still use i2psnark (and you would have the commodity to also have the browser included?) despite being in Java...
  2. For some reason, I would still feel insecure in using i2p without a VPN. It is said there is no need, ok, but what if I still want to use it. I guess it shouldn't harm? Like affecting speed or other factors? I would like to remove as much as possible any chance of my ISP sniffing on my connections.

PS: I have an improvement for your guide 😁You could add an extra container with Mullvad-Browser (still from linuxserver) to access Postman.