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

error: could not listen for incoming connections

by tkalfaoglu on 2016/11/15 06:19:49 AM    
Hi. I recently started getting this error at tixati startup,
it actually keeps happening while it is running as well..

A pop-up shows:

Could not listen for incoming connections
Address: udp:0.0.0.0:30120
error: operation not permitted (1)

and it retries 30 seconds later by itself, I sometimes get the popup again.

Any ideas what to check?
Many thanks

PS: This is a fedora 24 machine running tixati 2.48
by tkalfaoglu on 2016/11/15 04:53:36 PM    
Here is what is logged at the home page:

listening on udp:0.0.0.0:30120 : Operation not permitted (1)
[06:38:08 PM]  listening on udp:0.0.0.0:30120
[06:38:10 PM]  socket closed while listening on udp:0.0.0.0:30120 : Operation not permitted (1)
[06:38:11 PM]  listening on udp:0.0.0.0:30120
[06:38:13 PM]  socket closed while listening on udp:0.0.0.0:30120 : Operation not permitted (1)
[06:38:14 PM]  listening on udp:0.0.0.0:30120
[06:38:15 PM]  socket closed while listening on udp:0.0.0.0:30120 : Operation not permitted (1)
[06:38:17 PM]  listening on udp:0.0.0.0:30120
[06:38:20 PM]  socket closed while listening on udp:0.0.0.0:30120 : Operation not permitted (1)
[06:38:23 PM]  listening on udp:0.0.0.0:30120
[06:38:29 PM]  socket closed while listening on udp:0.0.0.0:30120 : Operation not permitted (1)
[06:38:52 PM]  listening on udp:0.0.0.0:30120
[06:39:07 PM]  socket closed while listening on udp:0.0.0.0:30120 : Operation not permitted (1)
[06:39:30 PM]  listening on udp:0.0.0.0:30120
[06:39:47 PM]  socket closed while listening on udp:0.0.0.0:30120 : Operation not permitted (1)
[06:39:48 PM]  listening on udp:0.0.0.0:30120
[06:40:00 PM]  socket closed while listening on udp:0.0.0.0:30120 : Operation not permitted (1)
[06:40:29 PM]  listening on udp:0.0.0.0:30120
[06:40:53 PM]  socket closed while listening on udp:0.0.0.0:30120 : Operation not permitted (1)
[06:41:20 PM]  listening on udp:0.0.0.0:30120
[06:41:38 PM]  socket closed while listening on udp:0.0.0.0:30120 : Operation not permitted (1)
[06:41:38 PM]  listening on udp:0.0.0.0:30120
[06:41:39 PM]  socket closed while listening on udp:0.0.0.0:30120 : Operation not permitted (1)
[06:41:45 PM]  listening on udp:0.0.0.0:30120
[06:41:55 PM]  socket closed while listening on udp:0.0.0.0:30120 : Operation not permitted (1)
[06:41:57 PM]  listening on udp:0.0.0.0:30120
by Guest on 2016/11/15 11:16:44 PM    
Operation not permitted sounds like a permissions issue with your .\tixati executable (OR it something with the binding IPv4 IPv6 settings... not sure if it normally bind to localhost)
But unfortunately I do not use linux. so i would search/look at any linux setup instructions here.
by tkalfaoglu on 2016/11/16 09:07:59 AM    
Many thanks for the feedback. I don't understand what happened; I have been using tixati for years with no ill effects. Maybe I have too many files queued (no seeders), I have about 30 such files waiting.. Maybe it sends out too many UDP datagrams at once, and Linux buffers overflow?
by Guest on 2016/11/16 11:13:49 PM    
That is a possibility. Did this happen immediately after updating to 2.48 exe? With the same setup / settings can you get it to NOT ERROR on 2.47 ? That would be what I would do to verify bug status for the current stable version.
Then if not, and it still ERROR on 2.47 i would lessen/stop the transfers in queue. Queue doesn't really affect ports. DID you specify a specific ipv4 ipv6 bind IP/interface in your settings? For Windoes you have the option of the {} GUID, the named adapter "teredo tunnel interface" or the specific IP, which may or may not work (as posted elsewhere).
I tried ipv6 for instance and after a while ipv6 showed an error, meanwhile my ipv6 address list grows for my basic wifi adapter. So like i said maybe.

Are you relying on tixati's NAT_PMP mapping for your router to open the port? If you setup a rule on the device you can turn that off in the settings.
So check 1) version problem only 2.48 or earlier?
2) are you linking to a specific IPv4/ipv6 adapter IP, or are you using a proxy
3) is the routing rule setup by Tixati, or did you open the port on your firewall/router manually?

Please update anything you find out.
by hcbd on 2016/11/26 04:40:17 PM    
This worked for me (having the same problem)

Downgrade / use a kernel below 4.8.x (pick a 4.7.x one on fedora 24).

- my Nat-PMP/Upnp functions are off, i manually forward a port from my router to my ipaddress
- tried to bind Tixati to different interfaces, none solved the issue (empty field, local ipaddress or interface)
- i'm using no proxy or Socks
- please note that multiple ipaddresses are brigded on the same nic (because of VM's) and Tixati is running on the Hostsystem.
- running Fedora 25 + 4.8.8-300 kernel (which doesn't work)
- downgrading to v2.47 gives the same results

Keep up the good work

for more info check out my double post on this issue: https://forum.tixati.com/support/2989/
by Guest on 2016/11/27 11:14:01 AM    
i am having the same problem on linux with 2.48 after update on linux. i just press ignore for now and things seem to be working correctly. im sure this is on the fix list for the next version.




This web site is powered by Super Simple Server