Strict3443

joined 1 year ago
[–] Strict3443@lemmy.ml 1 points 1 year ago

Yes, I did exactly this when I2P support was first in beta. I have a docker stack with Gluetun as my network for all my *arr containers and I was able to still point my qBittorrent to my i2pd router and it worked just fine.

[–] Strict3443@lemmy.ml 1 points 1 year ago

Yes, absolutely. I have a VPS that runs a i2pd router and I can set my clients to point to my VPS and I am able to use the I2P network. In doing so, I had to make sure I forwarded the correct ports on my VPS so that it would reach the i2pd application. I will do a write up soon.

[–] Strict3443@lemmy.ml 0 points 1 year ago (2 children)

Guide for Linux: https://strict3443.codeberg.page/i2p-info/hugo/public/posts/how-to-use-i2p-on-qbittorrent-nox/

You can install i2pd with sudo apt install i2pd and then point your services towards your i2p router (Ex. 127.0.0.1) and you are good to go.

[–] Strict3443@lemmy.ml 1 points 1 year ago

What @supervent@lemmy.dbzer0.com said. Basically you get access to the I2P network (overlay on top of the regular internet) that provides anonymity and doesn't require any port forwarding. Thus, this allows every user to seed torrents without worrying about opening ports or getting letters in the mail.

The torrent space on I2P is still growing, there are some chads cross-seeding to the I2P network allowing for torrenting popular torrents over I2P.

 

cross-posted from: https://lemmy.ml/post/6915117

The release of qBittorrent v4.6.0 stable comes with I2P support. While experimental, we can still get a working torrent setup using qBittorrent now. qBittorrent-nox is the Web-UI only version, and currently it does not have configuration settings in the Web-UI for I2P settings. This guide will show you how to setup qBittorrent-nox and manually change the qBittorrent.conf file to allow for I2P torrenting!

Guide can be found here: https://strict3443.codeberg.page/i2p-info/hugo/public/posts/how-to-use-i2p-on-qbittorrent-nox/


qBittorrent Changelog: https://github.com/qbittorrent/qBittorrent/blob/release-4.6.0/Changelog

 

cross-posted from: https://lemmy.ml/post/4912475

https://codeberg.org/Strict3443/qbittorrent-i2p-vnc

I have created a Dockerfile which will compile the latest version of qBittorrent which has experimental I2P support into a docker container with VNC support. The reason for this is my server is headless and I wanted to use the v4.6.x version of qBittorrent, but the qbittorrent-nox version of v4.6.x does not have I2P options yet. So I had to build the GUI version on top of a VNC image.

In doing so, this will build a container that has VNC capabilities where you can utilize a desktop environment to setup the GUI version of qBittorrent with your I2P settings, and then just use the web-ui from there on.

Why?

I am a qBittorrent user and wanted to start downloading and cross-seeding torrents with I2P, so I built this image as a drop in replacement of my linuxserver/qbittorrent docker container and it just works.

Why don't you post the docker image?

I am not sure how yet, and I also left it as a Dockerfile so that you can build this on ARM or x86-64 depending on your needs

Note

This image can be quite heavy and take a long time to build, but until v4.6.x is out of beta, this will do.