I was asked by another user on a torrent site if I had noticed that ever since 2.17+ if I had been getting incoming connections with Tix.

I hadn't noticed or paid attention before but I decided to start looking in 2.24 and after going though a few of my very active torrents with tons of peers, I have not 1 single incoming connection or peer listed as incoming, and the client has been running for 24hrs+.


Port are forwarded as always (manually not UPNP) and checked/confirmed open by "canyouseeme" and really the only change has been upgrading Tix. I can see the TCP and UDP ports bound to the IPv4 and v6 addresses in Resource Monitor and showing allowed, not restricted.

Anyone else seeing this?

My Tix is running on Windows 2012 r2 x64

Everything is fine for me.  I just started a new torrent 10 minutes ago and just looked at the Link column for all the peers, and have a healthy mix of incoming outgoing tcp udp.  I'm on Linux.

Did you check your windows firewall?

I am the same guest from last reply.

10 minutes later, I see that 80% of my connections are incoming.  So it's definitely working right here.

How about the numbers in the bottom-right of the Home view?  Increasing?

Are you sure you're not getting the little arrow-ball incoming/outgoing icons mixed up?  I sometimes get busy torrents that eventually have almost all connections incoming.

Resource Monitor is showing "allowed, not restricted" so firewall is not an issue.

Also canyouseeme reports the ports open for Ipv4, anouther site reports open for Ipv6


Received is at 2.7Mil, 10-20 Negotiating, and "Placed" is 0.


Every arrow is going out to the top right from the ball (even hovered over one just now, its outgoing), and Everything is DHT, PEX or Tracker, NONE say Incoming, and its multiple torrents with 300+ peers.


The other person that brought this to my attention is running Windows 10 x64

I find in 2.24 that setting "Incoming Peer Connection Encryption" to "Encrypted only" doesn't allow ANY incoming connections. Even with another Tixati client (2.16) "Outgoing Peer Connection Encryption" set for "Encrypted only" all you get is "Remote disconnected" when you try to connect to the 2.24 client.

2.24 has to be set to "Allow either" or no incoming connections at all.

So the other user seems to have figured out what conditions cause it.




Incoming Peer Connection Encryption set to Encrypted Only is breaking incoming connections.

Bump, as its kind of a big problem.