Roku Developer Program

Join our online forum to talk to Roku developers and fellow channel creators. Ask questions, share tips with the community, and find helpful resources.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
renojim
Community Streaming Expert

Re: Port 8060

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
Roku Community Streaming Expert

Help others find this answer and click "Accept as Solution."
If you appreciate my answer, maybe give me a Kudo.

I am not a Roku employee.
0 Kudos
EnTerr
Roku Guru

Re: Port 8060

Oh. It's just timing out.
It connects first but then kicks you out within five seconds or so. "Type faster" :mrgreen:
0 Kudos
RokuKC
Roku Employee
Roku Employee

Re: Port 8060

"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. 🙂

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.
0 Kudos
renojim
Community Streaming Expert

Re: Port 8060

"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
Roku Community Streaming Expert

Help others find this answer and click "Accept as Solution."
If you appreciate my answer, maybe give me a Kudo.

I am not a Roku employee.
0 Kudos
EnTerr
Roku Guru

Re: Port 8060

"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 😛
0 Kudos