Hey all, ran into a weird issue with my Ubuntu server running qbittorrent-nox I can’t seem to figure out.

When Qbittorrent is running, I can’t load some sites. How I discovered this was Jackett was failing tests to my trackers. Sometimes all trackers would fail, other times only a couple would.

From the server I ran a curl to the tracker URLs and confirmed they were not loading.

Pcap shows the TLS hello go out, but no response from the server.

Once I kill the qbittorrent process, everything works.

Wondering if anyone has any ideas or has seen this issue before.

Things I’ve tried:

  • Disabled ipv6
  • Changed Qbit UI port
  • Paused Torrents
  • re-installed openssl
  • rebooted about 150 times and counting

Qbit version is 4.5.5 Ubuntu 22.04.3 headless running on Esxi

Appreciate any ideas!

Edit: So after much frustration and some other weird things, restored to a previous snapshot and the issue seems to have resolved. Appreciate all the troubleshooting ideas and responses!

  • ElderWendigo
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 year ago

    Do you currently have a bunch of active torrents, each with a bunch of connected peers? What’s your network topology like? Aging combo modem/wifi/router? Have you tried limiting the total number of connected peers in your torrent manager? Torrents can really clog up a network. Sometimes routing too many connections overwhelmed my old router, forcing a reboot before any traffic could get through again.

    • ZeroCoolerOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 year ago

      Sorry, to clerify: this server is the only one effected. The rest of my network is working perfectly fine.

      All other internet traffic is running without a problem, it’s only http/https traffic on this one server running Qbit and Jackett.

      Thanks for the response!