Port 8060

Archived
1

Hi

I have a Roku 4200 running on the locat network:
172.150.1.195

I am timing out when I try to telnet on port 8060
telnet 172.150.1.195 8060

And I get nothing using a GET to from the browser
http://172.150.1.195:8060/query/apps

This used to work for me.

Has there been some restriction added in later firmware?

Thanks for any advice
James

2

You could try taking it out of Developer Mode then re-enabling Developer Mode.

3

What’s 8060 for?

4

8060 is the ECP port. I don’t think you can telnet to 8060, so that failed connection is probably expected.

5

“TheEndless” wrote:
8060 is the ECP port. I don’t think you can telnet to 8060, so that failed connection is probably expected.
Nah. If destruk can http to 8085, am i any worse not to telnet 8060? :mrgreen:
$ telnet 192.168.1.25 8060
Trying 192.168.1.25…
Connected to roku-2xs.gateway.pace.com.
Escape character is ‘^]’.
GET /query/apps HTTP/1.0

HTTP/1.1 200 OK
Server: Roku UPnP/1.0 MiniUPnPd/1.4
Content-Length: 2492
Cache-Control: no-cache
Content-Type: text/xml; charset=“utf-8”

Connection closed by foreign host.
$
@jamesrdelaney - is the Roku PING-able?
Is the client you are trying to connect from also on 172.150.1.*?
What’s the firmware# ?

6

“EnTerr” wrote:

“TheEndless” wrote:
8060 is the ECP port. I don’t think you can telnet to 8060, so that failed connection is probably expected.
Nah. If destruk can http to 8085, am i any worse not to telnet 8060? :mrgreen:
$ telnet 192.168.1.25 8060
Trying 192.168.1.25…
Connected to roku-2xs.gateway.pace.com.
Escape character is ‘^]’.
GET /query/apps HTTP/1.0
Now that’s curious. I actually tried it before posting and got a failed connection. Testing just now, I got the same. I’m testing on my Roku 4, though, so maybe it’s locked down in 7.0…?

7

EnTerr, what firmware are you on? I couldn’t connect to any of three different boxes running three different versions of firmware.

-JT

8

“renojim” wrote:
EnTerr, what firmware are you on? I couldn’t connect to any of three different boxes running three different versions of firmware.i checked on 6.2.3468, 6.2.3675
“TheEndless” wrote:
Now that’s curious. I actually tried it before posting and got a failed connection. Testing just now, I got the same. I’m testing on my Roku 4, though, so maybe it’s locked down in 7.0…?You guys are scaring me. I doubt the Co will do something so dickish as intentionally blocking the whole of ECP w/o warning. Does “Roku by Roku” app work with your players? How about remoku.tv and other apps?

9

When I try to telnet to a roku4 on 8060 it sitas there, control-C returns -
HTTP/1.1 400 Bad Request
Server: Roku UPnP/1.0 MiniUPnPd/1.4
Content-Length: 0
Connection to host lost.

So it probably ‘connects’ or it wouldn’t know it was a roku server, but just doesn’t handshake. 8060 does the same thing on my roku3 too.

10

“EnTerr” wrote:

“renojim” wrote:
EnTerr, what firmware are you on? I couldn’t connect to any of three different boxes running three different versions of firmware.i checked on 6.2.3468, 6.2.3675
“TheEndless” wrote:
Now that’s curious. I actually tried it before posting and got a failed connection. Testing just now, I got the same. I’m testing on my Roku 4, though, so maybe it’s locked down in 7.0…?You guys are scaring me. I doubt the Co will do something so dickish as intentionally blocking the whole of ECP w/o warning. Does “Roku by Roku” app work with your players? How about remoku.tv and other apps?
Yes, ECP still works. I’m using PuTTY to try and connect, so maybe it’s sending a character the telnet connection doesn’t like.

11

I tried telnet under Debian and I basically get the same thing for all three devices:

root@debian:~# telnet 192.168.0.108 8060
Trying 192.168.0.108...
Connected to 192.168.0.108.
Escape character is '^]'.
Connection closed by foreign host.

And yes, ECP still works.

-JT

12

Oh. It’s just timing out.
It connects first but then kicks you out within five seconds or so. “Type faster” :mrgreen:

13

“EnTerr” wrote:
Oh. It’s just timing out.
It connects first but then kicks you out within five seconds or so. “Type faster” :mrgreen:

EnTerr is right, as usual. :slightly_smiling_face:

The ECP server is not intended to support interactive telnet connections.
But if you can send a valid HTTP request quickly, as in EnTerr’s example, it should work.
Your telnet client would have to be in passive mode (not sending control sequences, for example), for that to work.

Using curl / wget / etc. would probably be easier, depending on what you are trying to do.

14

“EnTerr” wrote:
Oh. It’s just timing out.
It connects first but then kicks you out within five seconds or so. “Type faster” :mrgreen:
Ah, you’re right! I’m not sure I’ll ever use this, but I guess it’s nice to know it’s there.

-JT

15

“renojim” wrote:
I’m not sure I’ll ever use this, but I guess it’s nice to know it’s there.
I’ve been known to do such hooliganisms when troubleshooting web connections (browsers are so complicated these days, a tab may get wedged with not much help from “inspect”). Not to sell myself long though: i can barelly utter HTTP/1.0 - not 1.1 :face_with_tongue: