Hello,
I cannot install or test an app on my LG webOS TV because the developer SSH connection on port 9922 is refused.
Device and environment
- TV model: LG 55NANO916NA
- webOS TV version: 5.6.2-21
- The TV reports no available software updates.
- Location: Tbilisi, Georgia
- Computer: Mac
- CLI:
@webos-tools/cli, run usingnpx
What works
- Developer Mode Status shows ON.
- The developer session has approximately 999 hours remaining.
- Key Server can be enabled.
- TCP port 9991 accepts connections.
ares-novacom --getkeysuccessfully downloads the private key.- The downloaded key decrypts correctly and passes an RSA integrity check.
What fails
TCP port 9922 immediately refuses connections. For example:
nc -vz 192.168.31.48 9991
Connection to 192.168.31.48 port 9991 succeeded!
nc -vz 192.168.31.48 9922
Connection refused
The CLI produces:
npx ares-device --device HomeTV --system-info
[Info] Set target device : HomeTV
ares-device ERR! [syscall failure]: connect ECONNREFUSED 192.168.31.48:9922
ares-install and ares-launch fail with the same error.
The configured SSH username is prisoner, and the port is 9922.
Troubleshooting already completed
- Disabled and re-enabled Developer Mode, allowing the TV to restart.
- Unplugged the TV from power and restarted it.
- Deleted and reinstalled the Developer Mode app. Its enabled state appeared to persist after reinstalling.
- Checked for TV software updates.
- Tested on two separate networks: home Wi-Fi and a phone hotspot. The Mac and TV were on the same network for each test.
- On both networks, port 9991 was accessible while port 9922 returned Connection refused.
- Removed and recreated the laptop’s device configuration with a name containing no spaces (
HomeTV). The error persisted.
Questions
- Is this a known issue with this model or webOS version?
- How can I diagnose why the developer SSH service is not listening on port 9922?
- Is there a supported way to restart or repair that service without a factory reset?
- Could LG Services Country, account region, or user-agreement state cause this behavior?
- What additional logs or version information should I provide?
Thank you.