in my experience it happens with some downloads. If I remove that download the problem is gone.

Lex A.dam .NL

Hey guys, the problem you experience on w10 can be related to port reservation by OS. Just execute next commands to list all excluded port ranges:

UDP:
netsh interface ipv4 show excludedportrange protocol=udp

TCP:
netsh interface ipv4 show excludedportrange protocol=tcp

Same issue here.Win10-20H2 19042.928/Tixati v2.81(install) with default network/transfer/tracker settings. Issue SOLVED with modify Settings-Trackers-Multi-tracker announce mode from "All Groups" to "First working group". So far so good. Thanks for the help. Will keep reporting.

Windows 10, used the command prompt commands using netsh above to identify OS-reserved UDP ports.

Modified Tixati settings to not use the reserved ones and that worked for me to suppress the notifications.

Dammit Tixati forum, you ask me to type the green numbers but I'm red-green colorblind! At least I guessed right. 😂

This is obviously and ongoing problem. What, if anything is being done about it? I've had this issue for months and I am about done with Tixati because of it.

Damn. now i am getting this error too. I tried updating to the latest version they had same problem as before. I've set it the MULTI-TRACKER ANNOUNCE MODE to FIRST WORKING GROUP. Hope this works.

Hello everybody

Under Win10 2.84
I had this issue and then did this

Ran these commands to find any exclusion ports:    
netsh interface ipv4 show excludedportrange protocol=tcp
netsh interface ipv4 show excludedportrange protocol=tcp


I got 5329 for TCP. Changed the port to start at 6000
I still got the message Bad connection UDP:0.0.0.0:6969

so I did this:
*************************************************************************************
- Uncheck "Allow UDP tracker connections" in the settings under Transfers >> Trackers
*************************************************************************************

It has been running fine since

Seems that version 2.84 has fixed the problem of bad ports so far !!!

Thank you Team Tixati

Hello!

Still have this problem with latest Tixati on Win 10 (latest build) Tried all the suggestions in this thread without success.

Same here.
Latest build for windows 10 pro (21H1 OS Build 19043.1348)  and tixati (2.86)
Started happening for the first time ever today.
I have been using tixati for years and never had a single issue.

I have the same issue that started happening randomly for a week now
I am on windows 7 and i dont think its OS related

It appeared when I deleted a running torrent while not answering the popup for keeping/deleting the files.
It seems that torrent is not shown but also active so the program doesn't know what to do with it.

Once I re-added the same torrent and rechecked the torrent files, the error disappeared without any other actions.
So I think you should stop the torrent first, answer the popup and only then the torrent is considered removed from the program.

Having this problem all of a sudden after a reboot when my power went out. Bad access (10013). Multi-tracker group mode was already set to First working group so I tried All groups. Doesn't fix. Unticked Allow UDP tracker connections. Doesn't fix. Tried changing the port in Tixati and my router. Doesn't fix.

I was using an older version of Tixati (2.76 I think? Never had this or any problem on it) up until a week ago when I updated to 3.16.

Chiming in/bumping to report that I have been recently hit with the same error message since yesterday. (Tixati 3.19; Win 10 updated to the teeth.) Thankfully the connection itself seems not to be affected.

After reading the whole thread and seeing that there's no apparent solution, I've been selecting "ignore" when it pops up.

It seems to happen in 3.19 for UDP trackers.

Also, when it happens, a lot of UDP connections with peers just break.

Environment: a linux with 6.5.13 kernel