All my devices(dev mode enabled) if left un-used for a week, don’t connect to the 8080 port even after updating their software and re-booting.
Different browser, different network no luck. Wierdly :8060 port works, but not the 8080 or 80.
You’re saying that, if you open a browser to http://rokuip (without a port), that doesn’t work?
Port 8080 is for telnet, so http://rokuip:8080 will not work in a browser. You’d need to connect to that using a command like telnet rokuip 8080 or telnet rokuip 8085
If none of that works, then I’d recommend disabling developer mode, rebooting, and then re-enabling developer mode.
It is because the Roku does not have authorization yet. You need to first connect to the portal. Http://roku-ip-here and get the package portal showing. You need to give a password to get that far. After that the ports will work.
You only need to do this if the Roku loses power or the device has rebooted. You may never notice if you are always pushing new packages. But you will notice when you are just debugging.
The portal must be passed through first and given a password before telnet will work.
The portal must be passed through first and given a password before telnet will work.
I don’t think that’s accurate. You need to enable developer mode on the device (by using this process). That’s how you set the password. It’s not set through the device portal, it’s required to access the device portal though.
But I’ve never seen telnet blocked due to not logging into the device website. Typically it’s blocked because dev mode isn’t enabled in the first place.
The device is already in DEV mode. You have already set a password.
Reboot your Roku.
Do not go to the http://Roku-ip-here first thing on restarting. Instead just start your DEV application (telnet will only work on your own app) and try to telnet. It will not work. Now visit the URL (http://Roku-ip-here and login) and then telnet works.
This is so done Roku can block DEV mode on your device. Which will then block that portal from loading. Which then blocks telnet. They had to do this because the DEV mode is used as a side-loading piracy method by unscrupulous developers.
