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

  • ѕєχυαℓ ρσℓутσρє@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 year ago

    Question: Can I keep it connected to some VPN layer like gluetun, and still make I2P work? Ideally, it should route all the clearnet traffic through gluetun and the I2P traffic through i2pd.

    From the instructions, it looks like it should be possible, just confirming.

    • Strict3443OP
      link
      fedilink
      English
      arrow-up
      7
      ·
      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.