Search

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.