PG3 node servers Not Loading in Polisy

[sumguy]

Good morning,

I am using a polisy pro. It is on 5.4.4 and has both PG2 and PG3 installed. I am currently using all of my node servers on PG2 without any issues. Today I tried to start migrating two of my node servers to PG3. (Plex Webhooks (slot 3) and Bond (slot 4)).

I deleted Plex and Bond off of PG2. I then installed them and configured them in the same slots on PG3. Both node servers connect and show multiple nodes. However, the two servers in PG3 will not install in Polisy. Slots 3 and 4 are empty. I have rebooted Polisy and also PG3. I've also deleted and reinstalled each node server. When I go into each node server and click the load profile button, I get the following error in the log. 

 

6/2/2022, 09:27:51 [pg3] error: Error: POST https://192.168.0.120:8443/rest/ns/profile/4/upload/nls/en_US.txt Failed :: TypeError: Converting circular structure to JSON --> starting at object with constructor 'Object' | property 'httpsAgent' -> object with constructor 'Agent' | property 'sockets' -> object with constructor 'Object' | ... | property 'errored' -> object with constructor 'Object' --- property 'config' closes the circle 6/2/2022, 09:27:51 [pg3] info: upload not successful

 

PG3 shows it is connected to Polisy. Not sure how to fix this. Any help would be greatly appreciated. Jason

[bpwwer]

You don't show enough of the log to be sure, but my guess is that there are a lot of 401 errors in there.  Which means that the ISY credentials in the PG3 ISY config are wrong.

Go to the ISY -> Edit Current ISY menu and update the ISY username and password then hit save.  

You'll have to delete and re-install the node servers as PG3 currently thinks they are installed on the ISY but they aren't.

[sumguy]

My credentials were already there but I entered them again and saved. Rebooted just for the heck of it. Deleted the two PG3 node servers and reinstalled the Bond node server. Still not showing up in my Polisy. I've attached the log from PG3. Let me know if you need anything else to help figure this out. I really appreciate the help. This has gone above my level of expertise. haha

 

 

pg3_6-2-2022_122128_PM.zip

[bpwwer]

It looks like you're trying to use https://192.168.0.120:8443 for the ISY IP address.  This should be http://192.168.0.120:8080

Trying to use a secure (https) connection from PG3 to the ISY won't work unless your ISY has a valid SSL certificate.  By default the ISY uses a self-signed SSL certificate for secure connections but most things will reject that now as self-signed certificates can't be validated.  Which is what happened here.  PG3 attempts to connect to the ISY, sees the self-signed certificate and aborts the connection since it can't verify that the certificate is legit.

[sumguy]

Argh! That was it! Thank you so much.

 It is odd because PG3 said it was connected and didn't give any IoP connection warnings like PG2 would. It also had the option to connect securely so I went with it. I'm just happy to have it working. Thanks again.

[bpwwer]

There are some connections that PG3 makes that are using SSL for a secure connection.  The connections between PG3 and the node servers are secure.  You can make use of secure connection between the UI and PG3 (but you have to manually trust the certificate).

Right now, the http client that PG3 uses wants to validate the certificate by default, but because you don't interact with PG3 core directly, you can't tell it to trust the ISY's self signed certificate. 

Also, if your ISY had a certificate that was issued by a known certificate authority, then it could be authenticated by PG3 automatically and the secure connection would work.