Debugging via port 9222 does not work anymore

[GoogleCodeExporter]

*What steps will reproduce the problem?*

1. Register an unpublished receiver app
2. Add Chromecast stick to whitelist and waited for at least 15 minutes
3. Make sure to run development and test devices all on the same local network 
without client isolation
4. Start receiver app using a custom Android app
5. Wait until receiver app shows up (works fine, by the way)
6. Try to debug receiver app using Google Chrome browser and the URL 
http://<CAST-IP>:9222

*What is the expected output? What do you see instead?*

I expect to see a minimalistic web page containing the debug session links as 
it used to work just yesterday. Today I always get "This webpage is not 
available", no matter what I am trying to do.

I tried the following steps several times:

- Double/triple/quadruple check the correctness of the IP-address of the cast 
stick. No mistake there, I enter the correct URL into Chrome all the time.

- Rebooted stick several times. That used to fix the problem in the past, but 
since today it doesn't work anymore.

- Removed stick from whitelist in developer console and added it again - waited 
for 15 minutes. Still does not work.

- Restarted wireless router several times. Does not work.

- Performed factory reset on cast stick and reconfigured everything. Does not 
work.

*What version of the product are you using? On what operating system?*

Chromecast firmware version: 27946
Android Mediarouter version: v7:21.0.+
Android Play Services version: 6.5.87
Cast receiver app library version: 2.0.0

*Please provide any additional information below.*

The receiver app is hosted on a local web server that is running on the same 
local network. The receiver app starts just fine and everything is operational. 
I can interact with the receiver app using my Android app, however, debugging 
does not work anymore since today.
The accessibility of the debug port was also very shaky in the past. More often 
that not I got the "Webpage not available" error message, but as other 
developers on Stackoverflow pointed out, rebooting the stick used to fix the 
problem for me so far until today.

Original issue reported on code.google.com by dev.nobu...@gmail.com on 18 Mar 2015 at 8:21

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I could also verify using an nmap port scan that port 9222 is not open while my 
receiver app is running.

Original comment by dev.nobu...@gmail.com on 19 Mar 2015 at 5:28

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

My Chromecast stick is at a point where I can debug my receiver app again after 
rebooting the device. However, every single time the receiver app closes and I 
reopen it, I cannot debug it any more. I have to reboot the stick in order to 
enable port 9222 again.

Original comment by dev.nobu...@gmail.com on 19 Mar 2015 at 7:41

[GoogleCodeExporter]

Can you submit a feedback report and prefix it with "Issue 537"?
https://support.google.com/chromecast/answer/3187017?hl=en

Original comment by jonathan...@google.com on 19 Mar 2015 at 10:23

• Changed state: NeedInfo

[GoogleCodeExporter]

Thanks for the response. I used the Chrome browser extension for Chromecast to 
send feedback and attached the Chromecast log.

Original comment by dev.nobu...@gmail.com on 19 Mar 2015 at 10:41

[GoogleCodeExporter]

Thanks, we'll let you know if we need any additional information.

Original comment by jonathan...@google.com on 23 Mar 2015 at 5:40

• Changed state: Acknowledged

[GoogleCodeExporter]

I am also experiencing this problem and have submitted feedback as requested by 
Leon Nichols and Ali Nadaff in 
https://plus.google.com/u/0/+JimRenkel2014/posts/P7VQ8jppuKJ?cfem=1

Jim Renkel

Original comment by jim.ren...@gmail.com on 29 Mar 2015 at 11:23

[GoogleCodeExporter]

yesterday it worked for some reasons but today it again does not work :(

the actual debugging was running on
https://chrome-devtools-frontend.appspot.com/serve_rev/@188559/inspector.html?ws
=*IP*:9222/devtools/page/*UUID*

also i had to click on the shield to load "unsafe scripts". 

The Version of my device hasn't changed (still 27946)

Original comment by kujans...@gmail.com on 11 Apr 2015 at 7:43

[GoogleCodeExporter]

Has there been any progress on this issue? I haven't been able to do any 
receiver development / debugging for some time now.

Would it help you if I sent you the Chromecast stick that's "stuck"? I'm 
planning on buying another one, hoping that I'll be able to do receiver 
development on it, so I could spare this one that's "stuck".

Thanks in advance,
Jim Renkel

Original comment by jim.ren...@gmail.com on 12 Apr 2015 at 1:55

[GoogleCodeExporter]

@Jim: doing factory resets up to 3 times in a row gets my Chromecast into a 
state where I can debug my receiver app again for a single session - until the 
app closes or crashes. After that I need to do several factory resets again.
It's a pain but currently the only way to keep on working on my app. Maybe that 
will also work for you.

Original comment by dev.nobu...@gmail.com on 13 Apr 2015 at 5:44

[GoogleCodeExporter]

@dev.nobu...: Thank you for the tip. I may give it a try, but it sounds like it 
would be faster, and less expensive in time, to just drive to BestBuy, buy 
another Chromecast stick for development and testing, and use the "stuck" stick 
for non-development testing, or maybe even use it for real. :-( Again, thanks 
for the tip.

Original comment by jim.ren...@gmail.com on 14 Apr 2015 at 1:21

[GoogleCodeExporter]

Hi,
I only have this problem (debugging via port 9222) when the Chromecast is
connected to a bad wifi or with some wifi routers, I don't have this
problem with good wifi without interference, e.g when I using Wi-FI hotspot
on my Android phone. On bad wifi it helps to remove the Chromecast and let
it cold down for a while (30 minutes). The problem began to arise after
Google added the function Guest Mode to Chromecast. I have also reports
from customers that they have increase of wifi issues with Chromecast after
Google added Guest Mode.

Original comment by patrik.c...@magine.com on 14 Apr 2015 at 11:17

[GoogleCodeExporter]

I have the same problem. Because of my server I had timeouts when trying to 
launch receiver app via Android sender. I have changed the server to VPS and it 
works OK. The problem is with debugging as stated above. I can connect via 9222 
only ones. When the app crashes or sth makes senders disconnect so that the app 
is teared down, I cannot connect enymore via Google Chrome on port 9222. I get 
ERR_CONNECTION_REFUSED I need to do a factory reset, setup everything from 
scracth and then I can debug...for one session. 

Original comment by tomek.ig...@gmail.com on 15 Apr 2015 at 10:24

[GoogleCodeExporter]

Just stumbled upon this problem as well this night when trying to debug my app 
again. It just won't work, even though I didn't change *anything* from last 
time I debugged it. What's up with all these stability issues you guys are 
having? With the connection, now with the debugger...

Original comment by bogdan.z...@gmail.com on 18 Apr 2015 at 8:12

[GoogleCodeExporter]

We have more customer issues about Wifi connection problems with our App 
(MagineTV) after Chromecast firmware update 27946. I hope Google have noticed 
this and working on a solution (in stealth mode I guess). We using our Google 
contacts to make them aware of the problem.

Original comment by patrik.c...@magine.com on 20 Apr 2015 at 8:16

[GoogleCodeExporter]

Went and bought a new Chromecast stick, installed it, and I am able to debug my 
app on it.

So apparently, the old Chromecast stick somehow got "poisoned".

I repeat my offer: if it would help you guys solve this problem, I will gladly 
ship the problem Chromecast stick to you.

Original comment by jim.ren...@gmail.com on 21 Apr 2015 at 2:23

[GoogleCodeExporter]

Same Here. I takes 2-5 reboots to get the debuger going.
ERR_CONNECTION_REFUSED... WTF???

If I buy a new Chromecast stick will it "burn out"? How soon?

Original comment by sergey.m...@gmail.com on 25 Apr 2015 at 3:27

[GoogleCodeExporter]

Same here... Cannot manage to debug, at all.

Original comment by szatmari...@gmail.com on 10 Jun 2015 at 3:36

[GoogleCodeExporter]

After disabling the Chromecast guest mode from the Android app, the debug 
console now works again.

Original comment by hector.m...@gmail.com on 12 Jun 2015 at 2:10

[GoogleCodeExporter]

In our most recent Chromecast firmware release, this issue should be corrected. 
Please ensure your device is updated to the latest firmware version, >=31432, 
and if debugging on port :9222 is still not working, please file a feedback 
report from the Chromecast app saying "port 9222 debug not working" after you 
see the failure.

Original comment by jonathan...@google.com on 19 Jun 2015 at 12:36

• Changed state: Fixed