Forum Discussion

erinmausfd's avatar
erinmausfd
Newbie
2 years ago

Roku /keypress ECP command returning HTTP status code 401

Hi, I'm having a weird issue where one of the Roku Ultra devices I have is returning a 401 status code when trying to perform any keypress/keydown/keyup ECP commands. Any other ECP commands I tested...
Roku Developer Program
cyborg_helpplea's avatar
cyborg_helpplea
Binge Watcher
2 years ago
 
Repro (use your own IP and port number):

    const response = fetch("http://192.168.x.x:port_number/keypress/home", {
        method: "POST"
    }).then(response => {
        console.log("Response code:", response.status);
        if (!response.ok) {
            throw new Error('Network response was not ok');
          }
         
        console.log("Response code:", response.status);
        return response.text();
    }).then(data => {
        if (data) {
            return JSON.parse(data);
          } else {
            console.log('No data to parse');
          }
    }).catch(error => { console.error('Error:', error); }); 
        console.log("Roku Home button pressed");
        return response;
 
Output:
Roku Home button pressed
roku.js:21
Response code: 401
roku.js:6
Error: Error: Network response was not ok
 
 
I was able to reproduce the same with curl, and it affected all computers in my environment on the same day today.
JohnnyIV's avatar
JohnnyIV
Channel Surfer
2 years ago

A simple curl example:

curl -v -d '' "http://your-ip:8060/keypress/home"

Output

*   Trying n.n.n.n:8060...
* Connected to n.n.n.n (n.n.n.n) port 8060
> POST /keypress/home HTTP/1.1
> Host: n.n.n.n:8060
> User-Agent: curl/8.4.0
> Accept: */*
> Content-Length: 2
> Content-Type: application/x-www-form-urlencoded
>
< HTTP/1.1 401 Unauthorized
< Server: Roku/12.5.5 UPnP/1.0 Roku/12.5.5
< Content-Length: 0
<
* Connection #0 to host n.n.n.n left intact