I have been seeding torrents through utorrent (on windows) with no issues. But through this community’s megathreads, I came across using qBittorrent, which seems more flexible and configurable.

But I’m having an issue seeding torrents over my favourite private trackers though. I’m on Linux, and no matter what I do, it flags an orange sign and hovering over it says “there is a configuration issue”. The DHT number is non zero, and I’m currently trying to seed on two trackers.

Can someone share a guide on qbittorrent on how to properly configure it. Or a place (IRC, Matrix) where they could assist me? I’ve search online but haven’t been lucky so far.

As a last resort, if there is a good alternative too, I’m ready to switch.

EDIT: thanks to everyone for comments and helping me out resolving this issue.

  • rambos@lemmy.worldEnglish
    5·
    1 year ago

    Im just guessing, but did you increase the number of active torrents? Any chance your firewall is blocking it? Try disabling firewall.

    Btw you dont need alternative, qbit is perfect especially if you want to use *arr stack (highly recommended), but you can try transmission

    • idkman@lemmy.dbzer0.comOPEnglish
      1·
      1 year ago

      If you mean torrent queue, it is disabled. The port I’m using is open in the firewall and the router. I’m using firewalld.

      I have been looking into *arr. I just need some time to implement it 😉

      • Brickfrog@lemmy.dbzer0.comEnglish
        1·
        1 year ago

        You are firewalled (not port forwarded / not connectable).

        Like the other commenter said you need to port forward your torrent client’s incoming connection port. You may need to log into your network router to do that.

        Also make sure your OS firewall is allowing your torrent client access to the internet.

        And also make sure to whitelist your torrent client in any anti-virus/malware software, sometimes those block torrent clients too.

        • idkman@lemmy.dbzer0.comOPEnglish
          1·
          1 year ago

          On my router config, under port forwarding, I’ve forwarded a port range of 9000-31000. Now qBittorrent is using 30000.

          For testing. I’ve stopped firewalld too. Still no luck.

          • CmdrShepard@lemmy.oneEnglish
            2·
            1 year ago

            You need to forward a single port not a whole range then in QBit set this port to that same port number.

          • Brickfrog@lemmy.dbzer0.comEnglish
            2·
            1 year ago

            Like the other commenter said you should only forward 1 port. Open a port forward for the port number specified in your torrent client’s settings for Incoming Connections.

            Also keep in mind some ISPs may not allow you to forward lower port numbers, you should aim for any port in the Ephemeral port range (49152-65535) see https://en.wikipedia.org/wiki/Ephemeral_port

            When you configure your router make sure you are forwarding both TCP and UDP. And when you’re doing it create a regular port forward, not something like port triggering which is something else.

            Test your port forward with any port test website to confirm it is working e.g. with the torrent client running browse to https://www.canyouseeme.org/ or similar & make sure the test is successful using the port number you forwarded.

            If none of the above works then you have something else blocking the port e.g. firewall or anti-virus/malware. Or there’s missing information you forgot to share e.g. maybe you’re using a proxy or VPN, maybe you’re using a ISP using carrier grade NAT (CGNAT) that cannot do port forwarding (https://en.wikipedia.org/wiki/Carrier-grade_NAT), maybe something else.

            EDIT: One other idea, enable your log in qBittorrent (click View / Log and make sure to enable all the checkboxes) this should add a “Execution Log” tab in your main qBittorrent window. Now quit qBittorrent, wait until the qBittorrent process is shut down, then start qBittorrent and review the log as it starts up. Maybe you’ll see new information in there you haven’t noticed before.

            • idkman@lemmy.dbzer0.comOPEnglish
              1·
              1 year ago

              Some good news. It appears that the tracker didn’t had anyone downloading the torrent while I was seeding it. Because I tried seeding a public torrent, and it worked without any issue (although it still states a warning of “no direct connection”).

              The executive log might just be handy. I was full of questions what is going without the software telling me what it isn’t able to.

              I’ll keep a look out. I saw a few megabytes of upload on the private tracker. Lol.