Could not listen for incoming connection - Help and Support

Help and Support
Ask a question, report a problem, request a feature...
<< Back To Forum

Could not listen for incoming connection

Page 1 of 3 << < 1 2 3 > >>

by Guest on 2020/10/15 05:34:03 PM

Could not listen for incoming connection

UDP.0.0.0.0: 10032

Error: bad access ( 10013)

First time getting this error. Started over the last couple of days, happens every 15 minutes message pops up

by Guest on 2020/10/16 05:52:09 AM

what OS and what version of tixati?
where are you seeing this message?
can you connect to anyone in a torrent?
can you connect to any channels?
can you connect to the DHT?

by Guest on 2020/10/16 02:10:15 PM

what OS and what version of tixati? win10 2.76 I reinstalled 75 and 74 same problem
where are you seeing this message? small popup https://photos.app.goo.gl/YY4HpiGQgaoyGG1GA
can you connect to anyone in a torrent? up down... connects , transfers working , popup, all drops , retry, starts transfers again , 5 min repeat
can you connect to any channels? don't know
can you connect to the DHT? y

by Guest on 2020/10/16 02:12:07 PM

I also chgd ports multiple times

by Guest on 2020/10/16 11:26:48 PM

has anything about your system or OS (like updates) changed since the last time tixati ran without this popup?
has anything about your internet changed?
does it keep popping up no matter what option you select?
have you changed anything in the settings-->connection section?
has anything with your firewall or anti-virus changed?

by Guest on 2020/10/17 04:25:03 AM

i have the same issue.
nothing was changed other than upgrading to the latest version.
changing the options in the "Local ipv4 address or interface" did not help.

by Guest on 2020/10/17 03:00:52 PM

I too have the same problem, which started yesterday. No changes that I am aware of to my system (though Windows 10 does update in the background).

by Guest on 2020/10/18 04:36:01 PM

I also having the same issue, I've made no change to Tixati or Windows 10 settings, maybe it is a Windows 10 update causing it?

by Guest on 2020/10/18 10:19:06 PM

Same problem with ubuntu "Could not listen for incoming connections" port 18921, I tried changing the port and checked the port was open in Ubuntu. This occurred after updating to the latest version.

by Guest on 2020/10/18 11:00:31 PM

same problem here...after update

by Guest on 2020/10/19 05:17:59 AM

Also seeing the same issue on Linux with the latest version.

by Guest on 2020/10/19 09:10:43 PM

It seams like it is the problem with Multi-Tracker Announce Mode. When you select :First working group everything seems fine but when you choose :All groups than you get an error :Could not listen for incoming connections Adress: 0.0.0.0. Bad Access 10013.And in trackers for the file it says: UDP socket unavailable.Hope it helps to solve the problem:)

by Enertion on 2020/10/19 09:38:29 PM

https://imgur.com/sztCDn0

I am getting this too. linux-ck 5.7.19, Tixati 2.76. strace output:

socket(AF_INET, SOCK_DGRAM, IPPROTO_UDP) = 17
<snip>
sendto(17, "\0\0\4\27'\20\31\200\0\0\0\0\5\277\216Z", 16, MSG_DONTWAIT|MSG_NOSIGNAL, {sa_family=AF_INET, sin_port=htons(6969), sin_addr=inet_addr("255.255.255.255")}, 16) = -1 EACCES (Permission denied)

From `man 2 sendto`:

EACCES (For UNIX domain sockets, which are identified by pathname)
       <snip>
       (For UDP sockets) An attempt was made to send to a
       network/broadcast address as though it was a unicast address.

From `man 7 socket`:

SO_BROADCAST
       Set or get the broadcast flag.  When enabled, datagram sockets
       are allowed to send packets to a broadcast address.  This
       option has no effect on stream-oriented sockets.

AFAIK, either Tixati shouldn't be sending to 255.255.255.255:6969, or it should do something like this:

int broadcast_flag = 1;
setsockopt(udp_sock, SOL_SOCKET, SO_BROADCAST, &broadcast_flag, sizeof(broadcast_flag));

by Guest on 2020/10/22 10:44:50 AM

to everyone having this problem:
if you go back to version 2.75 does this still happen?

by Guest on 2020/10/25 03:30:20 AM

same problem. the software version is 2.7.3. os is win10.
and the problem happened this week. it's ok before. I do nothing to my software and my windows.

by Guest on 2020/10/31 05:56:50 AM

same issue from today. whether 2.64 or new 2.76

by Guest on 2020/10/31 06:28:36 AM

i have been having this issue with 3 versions of Tixati. I thought it was my VPN but it is not i believe its the latest update from MS but getting rid of the update is dam near impossible without redoing the whole system. I am going to see if i can get MS support to remove the update without a new clean install of win 10. Why is it that MS always has to screw with everything ..... UGH

by Guest on 2020/10/31 02:50:25 PM

for those having this problem with linux/ubuntu, what is the exact error you are getting?

by rocks911 on 2020/11/02 02:25:41 PM

I dont mean to hijack this thread at all, but I too have been dealing with this. I cant say though that it even disrupts exchange of p2p. Its hard to tell but it seems that things are going normally except for the message.
The exact pop-up message I get:

Could not listen for incoming connections
Address: UDP:0.0.0.0.35086
Error: Permission Denied (13)

Options include:

Change port Number Edit Connection Settings Retry(30) Ignore

A countdown is initiated with the counter next to Retry starting at 30 and counting down and then the error message goes away
entirely at the end of the countdown. It reappears randomly and I think that the UDP port indicated also changes from time to time.

I am running v2.75 on Ubuntu which is running on a Virtual Machine on my W10 PC

Its impossible to say what updating might have caused this. Lots of software updating all the time.

by rocks911 on 2020/11/02 04:40:55 PM

I can confirm that as Guest posted on 10/19
When you select :First working group everything seems fine but when you choose :All groups than you get an error

After adjusting that setting the issue went away. Fingers crossed.

Page 1 of 3 << < 1 2 3 > >>

Add Reply

<< Back To Forum