n8ur9irl Posted January 25, 2023 Share Posted January 25, 2023 When using ISY launcher and selecting Polyglot V3 (PG3), Chrome attempts to connect to: 192.168.1.153:3000 and returns “This site cannot be reached "client ID is not valid" Link to comment
bpwwer Posted January 25, 2023 Share Posted January 25, 2023 If this is a new eisy, you should first update the system. Go to the Admin Console, select the Configuration tab and select the Upgrade Packages button. This can take some time depending on how much needs to be updated, it could take as long as 30 minutes. Also, PG3 uses a self-signed certificate so the browser will flag that as not secure and you have to explicitly trust it's certificate to get the page to load. I can't tell from your post what is happening. "This site cannot be reached" is typically because the PG3 isn't running, but I don't know where "client ID is not valid" is coming from. That could be related to the certificates. Link to comment
n8ur9irl Posted January 25, 2023 Author Share Posted January 25, 2023 Thank you for your reply. I wasn't waiting long enough for Eisy to update. I'm not sure how you are supposed to tell when it is finished but it did take a long time. Link to comment
asbril Posted January 26, 2023 Share Posted January 26, 2023 (edited) I had notice in PG3 that I needed to do a restart. When I did, and waited for a while, I could no longer acces PG3. node servers have stopped working. I rebooted the eisy and also did an Update in the Admin. Console, but still not working. Any suggestions ? Edited January 26, 2023 by asbril Link to comment
asbril Posted January 26, 2023 Share Posted January 26, 2023 7 minutes ago, asbril said: I had notice in PG3 that I needed to do a restart. When I did, and waited for a while, I could no longer acces PG3. node servers have stopped working. I rebooted the eisy and also did an Update in the Admin. Console, but still not working. Any suggestions ? Resolved by power cycling the eisy. Link to comment
bpwwer Posted January 26, 2023 Share Posted January 26, 2023 PG3x has more external system level dependencies than PG3. When doing an update, most of those dependencies are also shutdown and restarted. If any of the external dependencies don't restart, then PG3x won't start. We don't have a good way for users to check all the systems so for now, power cycling the eisy is probably the best way to reset everything. 1 Link to comment
Recommended Posts