Skip Navigation
qbittorrent

qBittorrent

  • With UPnP disabled. Do you need to port forward the same port with TCP and UDP?

    I disabled UPnP for security reasons and want to port forward qBittorrent.

    Lets say the port I chose is 8999, do I need to port forward 8999 TCP and 8999 UDP? Or can I just port forward 8999 TCP? Or can I just port forward 8999 UDP?

    And WTF is uTP? There no option to port forward uTP ports in my router or VPN.

    1
  • How to Use I2P on qBittorrent-nox v4.6.0

    strict3443.codeberg.page How to Use I2P on qBittorrent-nox

    Setup I2P Router with SAM Enabled Step 1: Start your I2P router, either with i2pd or I2P java edition. Step 2: Ensure the SAM service is enabled on your I2P router Setup Qbittorrent-nox Step 1: Download the correct version of Qbittorrent-nox from https://github.com/userdocs/qbittorrent-nox-static/re...

    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

    0
  • qBittorrent v4.6.0 Release - Sun Oct 22th 2023

    qBittorrent v4.6.0 Release

    Sun Oct 22th 2023

    qBittorrent v4.6.0 was released today with a lot of new features and bug fixes. Here are some of the most notable changes for end users:

    Features:

    • Added experimental I2P support
    • Provided a UI editor for the default theme
    • Made various UI theming improvements
    • Implemented a torrent tags editing dialog
    • Revamped the "Watched folder options" and "Automated RSS downloader" dialogs
    • Allowed the use of another icons in dark mode
    • Allowed adding new torrents to the queue top
    • Allowed filtering the torrent list by save path
    • Exposed the 'socket send/receive buffer size' options
    • Exposed the 'max torrent file size' setting
    • Exposed the 'bdecode limits' settings
    • Added options to adjust the behavior of merging trackers to an existing torrent
    • Added an option to stop seeding when a torrent has been inactive
    • Allowed the use of a proxy per subsystem
    • Expanded the scope of the "Proxy hostname lookup" option
    • Added a shortcut for the "Ban peer permanently" function
    • Added an option to auto hide zero status filters
    • Allowed disabling confirmation of Pause/Resume All
    • Added an alternative shortcut CTRL+E for CTRL+F
    • Showed filtered port numbers in logs
    • Added a button to copy library versions to the clipboard

    Bug fixes:

    • Ensured ongoing storage moving jobs will be completed when shutting down
    • Refactored many areas to call non UI blocking code
    • Made various improvements to the SQLite backend
    • Improved startup window state handling
    • Used the tray icon from the system theme only if the option is set
    • Inhibited system sleep while torrents are moving
    • Used the hostname instead of domain name in the tracker filter list
    • Visually validated the input path in the torrent creator dialog
    • Disabled symlink resolving in the Torrent creator
    • Changed the default value for file pool size and stop tracker timeout settings
    • Logged when duplicate torrents are being added
    • Inhibited suspend instead of screen idle
    • Ensured the file name is valid when exporting torrents
    • Opened "Save path" if the torrent has no metadata
    • Prevented a torrent from starting unexpectedly in an edge case with a magnet
    • Made the "Add new torrent" dialog more ergonomic

    WebUI:

    • Added a log viewer
    • Allowed specifying the session cookie name in the WebAPI
    • Improved sync API performance
    • Added filelog settings
    • Added multi-file renaming
    • Added an "Add to top of queue" option
    • Implemented subcategories
    • Set "SameSite=None" if CSRF Protection is disabled
    • Showed only hosts in the tracker filter list
    • Set Connection status and Speed limits tooltips
    • Set Cross Origin Opener Policy to same-origin
    • Fixed the response for the HTTP HEAD method
    • Preserved the network interfaces when the connection is down
    • Added an "Add Tags" field for RSS rules
    • Fixed a missing error icon

    RSS:

    • Added a "Rename rule" button to the RSS Downloader
    • Allowed editing the RSS feed URL
    • Allowed assigning priority to an RSS download rule

    Search:

    • Used python isolate mode
    • Bumped the python version minimum requirement to 3.7.0

    Other:

    • Enabled DBUS cmake option on FreeBSD
    • Made numerous code improvements and refactorings

    For more information, please see the official changelog: https://www.qbittorrent.org/news.

    2
  • 9to5linux.com qBittorrent 4.6 Released with Initial I2P Support, Torrent Tags Editing, and More - 9to5Linux

    qBittorrent 4.6 open-source BitTorrent client is now available for download with initial I2P support, new options, UI improvements, and more.

    qBittorrent 4.6 Released with Initial I2P Support, Torrent Tags Editing, and More - 9to5Linux
    0
  • qBittorrent w/ I2P Support in Docker

    codeberg.org qbittorrent-i2p-vnc

    Dockerfile to compile the latest version of qBittorrent which has experimental I2P support into a docker container with VNC support.

    qbittorrent-i2p-vnc

    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.

    1
  • qBittorrent Wiki page

    github.com Home

    qBittorrent BitTorrent client. Contribute to qbittorrent/qBittorrent development by creating an account on GitHub.

    Home
    2
1 Active user