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

Closed
matt-cook opened this Issue Jan 5, 2015 · 9 comments

Comments

Projects
None yet
4 participants
@matt-cook
Member

matt-cook commented Jan 5, 2015

@matt-cook matt-cook added the bug label Jan 5, 2015

@matt-cook

This comment has been minimized.

Show comment
Hide comment
Member

matt-cook commented Jan 5, 2015

@matt-cook

This comment has been minimized.

Show comment
Hide comment
@matt-cook
Member

matt-cook commented Jan 5, 2015

@matt-cook

This comment has been minimized.

Show comment
Hide comment
@matt-cook

matt-cook Jan 4, 2016

Member

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.

Member

matt-cook commented Jan 4, 2016

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

This comment has been minimized.

Show comment
Hide comment
@taneth111

taneth111 Jan 12, 2016

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

taneth111 commented Jan 12, 2016

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

@matt-cook matt-cook modified the milestones: 5.5.2, 5.6.0 Feb 9, 2016

@matt-cook

This comment has been minimized.

Show comment
Hide comment
@matt-cook

matt-cook Feb 9, 2016

Member

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.

Member

matt-cook commented Feb 9, 2016

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

This comment has been minimized.

Show comment
Hide comment
@backslashgithub

backslashgithub Feb 22, 2017

"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 .

backslashgithub commented Feb 22, 2017

"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 .

@matt-cook

This comment has been minimized.

Show comment
Hide comment
@matt-cook

matt-cook Mar 22, 2017

Member

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

Member

matt-cook commented Mar 22, 2017

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

@matt-cook matt-cook reopened this Mar 22, 2017

@michaelvelasquez

This comment has been minimized.

Show comment
Hide comment
@michaelvelasquez

michaelvelasquez Jun 1, 2017

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.

michaelvelasquez commented Jun 1, 2017

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.

@matt-cook

This comment has been minimized.

Show comment
Hide comment

@matt-cook matt-cook closed this Oct 16, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment