remote management inaccessible on ChromeOS

Question

remote management inaccessible on ChromeOS

matt-cook opened this issue 10 years ago · comments

Matthew Cook commented 10 years ago

Documented issue with ChromeOS: https://code.google.com/p/chromium/issues/detail?id=233052

Matthew Cook · Answer 1 · Tue Jan 06 2015 06:20:07 GMT+0800 (China Standard Time)

related issue: https://code.google.com/p/chromium/issues/detail?id=435404

Matthew Cook · Answer 2 · Tue Jan 06 2015 06:26:53 GMT+0800 (China Standard Time)

For now it appears the only solution is to switch to developer mode: http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/asus-chromebox#TOC-Developer-Mode

and open the port manually via: https://code.google.com/p/chromium/issues/detail?id=233052#c6

Matthew Cook · Answer 3 · Tue Jan 05 2016 01:58:45 GMT+0800 (China Standard Time)

Additional details reported by a user:

By changing the Remote Administration Host address to the wlan0 IPv4 option and changing the Port from 80 to 8080, I was able to get it to work. The standard loopback address on port 8080 won’t work, nor will the IPv4 wlan0 address on port 80.

taneth111 · Answer 4 · Tue Jan 12 2016 08:32:36 GMT+0800 (China Standard Time)

Confirmed working by changing the port to 8080 from a remote device.

Matthew Cook · Answer 5 · Wed Feb 10 2016 05:41:00 GMT+0800 (China Standard Time)

Confirmed working on 8080 here as well. Did NOT work with 80 or 82. I don't see any documentation on which ports are blocked or how to tell if opening the port was successful: https://developer.chrome.com/apps/sockets_tcpServer

Default will be changed to 8080.

backslashgithub · Answer 6 · Wed Feb 22 2017 23:39:45 GMT+0800 (China Standard Time)

"By changing the Remote Administration Host address to the wlan0 IPv4 option and changing the Port from 80 to 8080, I was able to get it to work."
I can log in and edit and save, only when i want to restart kiosk crashes on the remote host.(the change was made but only kiosk crashed)
also i did not get the daily restart to work(did this on kiosk app installed .

Matthew Cook · Answer 7 · Wed Mar 22 2017 10:57:46 GMT+0800 (China Standard Time)

@backslashgithub thanks for reporting these bugs. I'll be investigating for the next release.

Michael Velasquez · Answer 8 · Fri Jun 02 2017 07:26:33 GMT+0800 (China Standard Time)

Hello. I want to report similar results to @backslashgithub
I have Remote Administration working on an ASUS Chromebit on port 8080 on both my local network and from outside my network with port forwarding. I can log in, edit and save. When I Restart, the Kiosk Remote Admin page shows a "Restarting" message and then comes back up again, but Kiosk doesn't restart on the Chromebit. It doesn't crash, but nothing happens. If I manually restart Kiosk on the Chromebit, my edited URL displays so it is being saved. I tested using Remote Admin via Chrome on OS X 10.11.6 and Safari on OS X 10.6.8 (those are just the OS versions I have on hand). Thank you.

Matthew Cook · Answer 9 · Tue Oct 17 2017 04:39:20 GMT+0800 (China Standard Time)

This issue was moved to https://discuss.kiosk.cook.company/t/remote-management-inaccessible-on-chromeos/93