I've just tried the new Web Shell extension on my Keenetic Hero running KeeneticOS 5.2.A.1 (draft).
When I click the button in the menu, it fails to connect. I checked my logs and realized it might be related to my custom HTTP/HTTPS admin ports. I use non-standard ports for my router management:
ip http port 65080
ip http ssl port 65083
ip http ssl redirect
And these are the errors showing up in my logs:
2026/07/18 08:33:49 [error] 1710#0: *2166 upstream prematurely closed connection while reading response header from upstream, client: 10.101.0.17, server: , request: "GET /app/webshell/ws HTTP/1.1", upstream: "http://unix:/var/nginx/ttyd.socket:/ws", host: "10.101.0.1:65080"
Jul 18 08:33:51 web-shell [2026/07/18 08:33:51:1076] W: refuse to serve WS client from different origin due to the --check-origin option.
Jul 18 08:33:51 web-shell [2026/07/18 08:33:51:1078] W: User code denied connection
I think the backend tool (ttyd) blocks the connection because of the --check-origin option since the WebUI is running on a custom port (65080).
Hopefully, this can be fixed in future updates so it can automatically accept custom ports as well. I'm sharing my logs and screenshots just in case it helps the development team.
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
KYTECHNGAMING
Hello,
I've just tried the new Web Shell extension on my Keenetic Hero running KeeneticOS 5.2.A.1 (draft).
When I click the button in the menu, it fails to connect. I checked my logs and realized it might be related to my custom HTTP/HTTPS admin ports. I use non-standard ports for my router management:
ip http port 65080 ip http ssl port 65083 ip http ssl redirectAnd these are the errors showing up in my logs:
2026/07/18 08:33:49 [error] 1710#0: *2166 upstream prematurely closed connection while reading response header from upstream, client: 10.101.0.17, server: , request: "GET /app/webshell/ws HTTP/1.1", upstream: "http://unix:/var/nginx/ttyd.socket:/ws", host: "10.101.0.1:65080" Jul 18 08:33:51 web-shell [2026/07/18 08:33:51:1076] W: refuse to serve WS client from different origin due to the --check-origin option. Jul 18 08:33:51 web-shell [2026/07/18 08:33:51:1078] W: User code denied connectionI think the backend tool (
ttyd) blocks the connection because of the--check-originoption since the WebUI is running on a custom port (65080).Hopefully, this can be fixed in future updates so it can automatically accept custom ports as well. I'm sharing my logs and screenshots just in case it helps the development team.
Thanks!
1 answer to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.