-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remote management inaccessible on ChromeOS #14
Comments
related issue: https://code.google.com/p/chromium/issues/detail?id=435404 |
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 |
Additional details reported by a user:
|
Confirmed working by changing the port to 8080 from a remote device. |
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. |
"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." |
@backslashgithub thanks for reporting these bugs. I'll be investigating for the next release. |
Hello. I want to report similar results to @backslashgithub |
This issue was moved to https://discuss.kiosk.cook.company/t/remote-management-inaccessible-on-chromeos/93 |
Documented issue with ChromeOS: https://code.google.com/p/chromium/issues/detail?id=233052
The text was updated successfully, but these errors were encountered: