it has also happened to me ever since I updated to 2.76
2

what settings did you adjust

I'm also facing same issue. Looks like tixati can't listen on port 5xxxx. Might be some configuration issue with windows.

I tried several things.
First I changed the port at TIXATI several times, it didn't help.
I switched off the firewall defender, it took a little longer but the error came back.
I am getting the impression that every time TIXATI reaches a particulair amount of downloads, maybe connections in the download row, the error appears, but i am not sure about it.
In 2016 something like this was happen caused by a newer version of LINUX, downgrading to a older version helped as far as i could read.
But i am using WINDOWS 10.
Which means this could be caused by an update of WINDOWS.
I do not remember if there was an update a short time before, but i know there are a lot frequently.

Every news about a solution is very welcome, because the fault message is very annoying...

Linux Tixati 2.76 now 2.78 getting this popup but only at startup of the program.  

Would like to stop the popup alltogether and never have to answer it.

Tried setting multi-tracker announce to first working group but popup still appears at program launch.

Ideas?

I didn't know this is also happen with LINUX.
This means it IS! probably a TIXATi bug. because I am using Windows 10.
TIXATI developers - PLEASE try your best to solve this bug!

Yes, go to Tixati Settings -> Transfers -> Trackers

Make sure Multi-tracker announce mode is First working group

I tried this setting: changing the transfer setting to Multi-tracker announce mode allready before - but no changes, still the same fault message.

I hoped after installing the new version of TIXATI (2.78), but unfortunately no changes

Please TIXZTI developers try your best to solve the problem...

I have the same issue.

Possible solutions until the issue is fixed:

- Remove all UDP trackers from your torrents
- Uncheck "Allow UDP tracker connections" in the settings under Transfers >> Trackers

If you need a list of HTTP(s) public trackers, see (link removed by Mod - Link was not working)

Tixati Settings -> Transfers -> Trackers was the solution at the end.

It took a while before the message was disappearing but this is the solution.

Thanks for the information.

Starting today this is also happening for me on v2.78 (win10).
I changed no settings and installed no new software or updates except for Windows Defender definitions.
Checked if anything changed with the router, forwarding rules, firewall, restarted and so on, no change.
Never had any trouble with Tixati before.
Very odd..
Setting the tracker group doesn't seem to change anything either.

[17:56:17]  error listening on udp:192.168.1.***:**** : Bad access (10013)
[17:56:17]  error listening on udp:[2001:2002:51ea:1e85:d827:****:****:****]:**** : Bad access (10013)

I changed my port(s) several times, getting same bad access.  since the installation of the latest version (2.78), running on Windows 10.  I can't recall when it started, b/c I've been out of commission due to illness.  However, today was my first day to be fully "awake" and I changed my port again, and now on my home screen it says everything is ok, will monitor it.  

I've changed no settings other than port.

OK, as I'm typing this, the error popped back up, however, I just clicked re-try and it worked again.  port and status says listening / ok.

[11:11:34 AM]  socket closed while listening on udp:**.***.*.**:***** : Bad access (10013)
[11:11:39 AM]  listening on udp:**.***.*.**:*****
[11:11:39 AM]  socket closed while listening on udp:**.***.*.**:***** : Bad access (10013)
[11:11:42 AM]  listening on **.***.*.**:*****

seems about every 6 minutes the socket closes and error message pops and I just hit retry and it starts ok again, for roughly 6 to 10 minutes.


Tixati 2.78
Windows 10

I'll try the no udp idea and see if it changes... do that later...

Ok, just to follow up.

About every 6 to 10 minutes, I kept getting the error message about bad port access.  it would work but then stop.

so I went into Settings / Trackers and unchecked "allow UDP Tracker Connections" <- only this one, I didn't change anything else and for now it's working, home screen is listening to my assigned port and status is ok.

Some suggested to change the multi-tracker announce mode, but I didn't change that, it's still set to default of "all groups".

Of course UDP trackers are offline, but the http trackers seems to be working ok.

Will report back later if anything changes.

Just had this issue come up today, with Tixati 2.63 running on Windows 10 Pro (build 1909, version 18363.1198).

I just updated Tixati to 2.78, but it made no difference.

I also feel it may have to do with a silent update from Microsoft... but if other report the same issues under Ubuntu, perhaps we're using the same trackers, and there's a problematic update on their side ?

After a day of usage, as long as the UDP trackers is offline, everything works.  I've had it off for 24 hours (+) and its working ok, just can't use UDP.

Everything else, appears to be working fine.

Tixati v2.78
Windows v10 (+ latest windows updates)

I have been having the same issue (socket closed while listening on tixati Permission denied (13)) on Ubuntu 18 since October. Disabling UDP trackers does resolve the issue. There may have been a kernel update that started this but it looks like some Windows users are having the same issue.

Let me know of any info needed to help debug

Tixati 2.79, Windows 10 Pro 10.0.19042 Build 19042

Same issue here, "10013 bad access" or "UDP socket unavailable" for almost every tracker in trackers list at any given port range and port number.
Tixati is the only network app I'm currently running, so it has nothing to conflict with.

If I turn all the udp trackers off the app would be unusable for me.

go to Tixati Settings -> Transfers -> Trackers

Make sure Multi-tracker announce mode is First working group

This worked for me : Fully patched Win 10
NordVPN using Openvpn
Longterm Tixati User :
Current version : 2.73

Tried the First working group; that did not work. Found on Reddit that it could be a problem with a port greater than 40000 as those are random and can be used by apps/Windows 10 but when I lowered that under, still and issue. Never had this problem until the last few versions and I just updated to this one, this week. Now, tomorrow, I could log in and everything could be fine. It's never consistent.

is socket error