Hi Developer Forum,
I can’t seem to access the developer console on both my work XD and home XDS box on port 8085. When I go to the URL, it just loads and loads and loads, with the screen completely white. I tried resetting to factory on my home box to no avail. Any ideas here?
I’m really hoping I can resolve this issue ASAP because it has put a stop to all development efforts for me.
Did you re-enable developer mode? It was disabled in 4.8, so devs would have to accept the new developer agreement: http://sdkdocs.roku.com/display/RokuSDK … ease+Notes
I was never prompted to re-enable, and installing packages works just fine. I just can’t bring up the dev console when I go to :8085 in my browser, which has worked the last few weeks.
In your browser? You need to connect to 8085 in telnet/command prompt, or using Putty or something. I’ve never connected to 8085 in a browser. btw - 8085 only works while a channel is running on your target roku.
Thanks for your prompt replies - feeling like a total noob over here haha. I telnetted in on the mac terminal but I’m not getting anything log-wise. Do I need to type in a command to enable the log? Thanks again!
What I mean is, I type this in:
telnet 8085
Then it says:
Trying …
Connected to
Then I try typing in commands like
bt
?HELLO WORLD
and it returns nothing. Any ideas here?
You won’t see any output on that port until you run a side-loaded channel. After the channel is running, you can type ctrl-C to break into the brightscript debugger.
–Mark
Thanks everyone! I’m back up and running over here. Much appreciated.
“destruk” wrote:
In your browser? You need to connect to 8085 in telnet/command prompt, or using Putty or something. I’ve never connected to 8085 in a browser. btw - 8085 only works while a channel is running on your target roku.
Connecting to port 8085 works fine for me using a browser – if all you’re looking for is the debug output. Sometimes I find it more convenient than using telnet from the Windows command prompt if I want to examine large debug output strings.
“belltown” wrote:
“destruk” wrote:
In your browser? You need to connect to 8085 in telnet/command prompt, or using Putty or something. I’ve never connected to 8085 in a browser. btw - 8085 only works while a channel is running on your target roku.
Connecting to port 8085 works fine for me using a browser – if all you’re looking for is the debug output. Sometimes I find it more convenient than using telnet from the Windows command prompt if I want to examine large debug output strings.
Care to elaborate? How are you accessing port 8085 via a browser? That doesn’t work for me (nor would I expect it to).
“TheEndless” wrote:
“belltown” wrote:
“destruk” wrote:
In your browser? You need to connect to 8085 in telnet/command prompt, or using Putty or something. I’ve never connected to 8085 in a browser. btw - 8085 only works while a channel is running on your target roku.
Connecting to port 8085 works fine for me using a browser – if all you’re looking for is the debug output. Sometimes I find it more convenient than using telnet from the Windows command prompt if I want to examine large debug output strings.
Care to elaborate? How are you accessing port 8085 via a browser? That doesn’t work for me (nor would I expect it to).
I side-load a channel, then using a web browser type: http://192.168.0.4:8085/ in the location bar. The browser then displays all the debug output (print statements, etc.) The browser window is automatically updated as more debug output is generated.
It works for me using Roku firmware 3.1 build 1017. It works better with Firefox and Chrome. With Internet Explorer, the linefeeds are not handled properly.
Works on a Roku 2 as well (using Firefox), although I don’t see any advantage over using a Telnet client.
-JT
“belltown” wrote:
I side-load a channel, then using a web browser type: http://192.168.0.4:8085/ in the location bar. The browser then displays all the debug output (print statements, etc.) The browser window is automatically updated as more debug output is generated.It works for me using Roku firmware 3.1 build 1017. It works better with Firefox and Chrome. With Internet Explorer, the linefeeds are not handled properly.
That doesn’t work for me on my Roku 1 or my Roku 2, no matter which browser I try. Maybe you have some plugin installed in your browser that enables it…
“TheEndless” wrote:
“belltown” wrote:
I side-load a channel, then using a web browser type: http://192.168.0.4:8085/ in the location bar. The browser then displays all the debug output (print statements, etc.) The browser window is automatically updated as more debug output is generated.It works for me using Roku firmware 3.1 build 1017. It works better with Firefox and Chrome. With Internet Explorer, the linefeeds are not handled properly.
That doesn’t work for me on my Roku 1 or my Roku 2, no matter which browser I try. Maybe you have some plugin installed in your browser that enables it…
No plugins installed, at least not for Chrome and IE. I can also access port 8085 using the Windows Mobile browser on my HP iPAQ PDA running Windows CE 4.20.
“belltown” wrote:
“TheEndless” wrote:
“belltown” wrote:
I side-load a channel, then using a web browser type: http://192.168.0.4:8085/ in the location bar. The browser then displays all the debug output (print statements, etc.) The browser window is automatically updated as more debug output is generated.It works for me using Roku firmware 3.1 build 1017. It works better with Firefox and Chrome. With Internet Explorer, the linefeeds are not handled properly.
That doesn’t work for me on my Roku 1 or my Roku 2, no matter which browser I try. Maybe you have some plugin installed in your browser that enables it…
No plugins installed, at least not for Chrome and IE. I can also access port 8085 using the Windows Mobile browser on my HP iPAQ PDA running Windows CE 4.20.
Figured it out. It wouldn’t connect for me, because I was already connected via telnet. Interesting that it works via http…
