Unable to open dev-debug console on port 9222

[GoogleCodeExporter]

What steps will reproduce the problem?
1. open http://chromcastip:9222/

What is the expected output? What do you see instead?
See something reasonable, not This webpage is not available...

What version of the product are you using? On what operating system?
Chromcast Firmware:19084

Please provide any additional information below.
I do have registered device in Google Cast SDK Developer Console. (checked even 
by google online support).
Tried soft/hard reset multiple times.
Tried different router with different ISP.
Have checked "Send this SN when checking for updates"
I can ping my chromecast IP, port scanner sees 8008,8009 is alive, but nothing 
on 9222.

Any help ?

Original issue reported on code.google.com by jbrucha...@gmail.com on 10 Oct 2014 at 11:20

[GoogleCodeExporter]

Have you already created your own app(s) and added them to your developer 
console?

If not, you'll need to follow these steps in order to be able to debug your 
app(s):

1) Log into your Google Cast Developer Console and create an app (note:  you 
don't have to publish it at this time).
2) Register your Chromecast device for that App ID.
3) Run the app.
4) Connect to your Chromecast device.
5) Then debug via port:9222.

Please check out the following resources for some additional information:

A) For app and device registration details:  
https://developers.google.com/cast/docs/registration
B) For more information on Debugging:  
https://developers.google.com/cast/docs/custom_receiver#debugging
C) Google Cast Developers G+ Community Post: 
https://plus.google.com/117916055521642810655/posts/THNdcXCwRUb

Original comment by ahug...@google.com on 10 Oct 2014 at 8:45

[GoogleCodeExporter]

Original comment by ahug...@google.com on 10 Oct 2014 at 8:46

• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

Hi there,

thanks a lot.

I did have my app registered. But i didn't realize that the debug console is 
visible only if a video is played (web page with player is visible)...

So plz close this issue as solved...

And maybe it could be enhancement to show at least something to avoid this 
misunderstanding...

Original comment by jbrucha...@gmail.com on 11 Oct 2014 at 4:35

[GoogleCodeExporter]

Our documentation on debugging states that you need to have your app running.

Original comment by anad...@google.com on 11 Oct 2014 at 4:38

• Changed state: Fixed

[GoogleCodeExporter]

Aha, 
my bad. Overlooked it...

TY again...

Original comment by jbrucha...@gmail.com on 11 Oct 2014 at 4:42

[GoogleCodeExporter]

I have encountered issues with not being able to connect to the debugger, 
despite my receiver app running and with a white-listed serial number. It used 
to work, but now, it rarely does. I've not been able to connect to the debugger 
for the past week.

I also get a lot of issues with my launched receiver not finding a ready state, 
and I have to re-connect via my Android Sender app to get it into the ready 
state.

Then, added to this, often messages cannot be sent, due to the Cast client 
being null, despite a successful connection to the CC.

Original comment by pcann...@gmail.com on 13 Jan 2015 at 4:59

[GoogleCodeExporter]

#6

I'd like to gather some additional information from you. Can you please submit 
a ticket via the Cast Developer Help Center:

https://support.google.com/cast-developer/#topic=3547309

and I'll follow-up with you.

Original comment by ahug...@google.com on 13 Jan 2015 at 11:05