I have successfully used Tribler in a virtual machine & container up to version 7.0.2. The latests builds (incl. version 7.1.0-rc2) unfortunately keep failing to build a circuit for actively seeded recent torrents. It looks like Tribler is able to find peers: (session_uptime 5:06:10, total_down 100.20 MB, total_up 129.75 MB)
DiscoveryCommunity 91 peers
TrustChainCommunity 7 peers
DHTDiscoveryCommunity 7 peers
TriblerTunnelCommunity 7 peers
MarketCommunity 15 peers
PopularityCommunity 15 peers
But in the logs I get a lot of
WARNING community:79 (Request) Request to Peer<ip_address:port, => timed out
It runs on a non-NATTED ip address and in the firewall rules I allow all RELATED and ESTABLISHED connections and all incoming TCP/UDP connections to ports 7759:7760 (as per FAQ). I’m running Tribler in a Kubuntu virtual machine (Linux kubuntu 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux). I hope someone can help me out to get this great piece of software to work as expected again…
I don’t know if it is relevant but after 5+ hours running Tribler there have only been 3 packets to UDP sport 7759:7760
Is the information in the Tribler FAQ (What ports does Tribler use?) still correct? I seems some options, where you could set the ports to something different from TCP/UDP 7759:7760, have been removed from the triblerd.conf.
What firewall rules are needed for NEW incoming connections?