Skip to content
This repository has been archived by the owner on May 15, 2020. It is now read-only.

Telnet too soon 61 10061 111 Connection refused

othrayte edited this page Jan 7, 2012 · 1 revision

This is a very annoying problem that is not actually the fault of TU. It appears mostly on ___ systems.
The symptoms include a lack of any scrobbling from TU and lots of messages in XBMCs log that read "NOTICE: Trakt Utilities: [Notification Service] Telnet too soon? (61) Connection refused" or "NOTICE: Trakt Utilities: [Notification Service] Telnet too soon? (10061) No connection could be made because the target machine actively refused it" or "[Notification Service] Telnet too soon? (111) Connection refused"

Possible solutions

Unfortunately this is a tricky issue to properly diagnose the origin of, here are some steps you might like to try.

  1. Make sure that the option "Allow programs on this system to control XBMC" is enabled, you can find it uner "System" > "Network" > "Services" > "Allow programs on this system to control XBMC".
  2. Check for this message in XBMCs log "ERROR: JSONRPC Server: Failed to bind serversocket"
  3. Check for rouge firewalls blocking the local port 9090, if nothing is blocking the port then try step 2.
  4. With XBMC running, use any telnet client to connect to the server, the address should be 'localhost' (127.0.0.1) and the port number is 9090. You should see messages from XBMC like these: Messages from XBMC over json if you don't see these try doing something in XBMC, let the screensaver enable or play something. If you don't see these messages then you need to contact someone from the XBMC dev team (or submit a trac ticket) and tell them that you can't connect to the "json notification service over TCP".

If the problem persists post a message in the forum thread here.

Clone this wiki locally