Skyline API AQMP failing to connect to socket

[JoshuaP · Accepted solution]

Double check that the server and client date and times are accurate.  If the times are significantly different some of the APIs will fail to validate the client certificate that is used to encrypt data over AMQP.

In addition, the client certificate validation will fail if the hostname/IP address the target is using to connect to the server is different than what is listed on the servers certificate.  If you have a DNS alias or some other IP address that the target is using that isn't native to the Win7 VM then you may need to manually add it to the SystemLink Server's RabbitMQ configuration similar to what I had to do for one of my AWS hosted servers I use for testing.

[simenfu]

All devices were set up with NTP, so the timestamps were only milliseconds apart. I did, however, try your second suggestion, which worked great. The server was set up with a DNS hostname, but I was under the impression that it would be sufficient for the client to simply be using that DNS. Turns out you were right and I needed to add the hostname to the RabbitMQ configuration. Shortly after doing so (and restarting the services on the server) I got a new error AMQP error: Peer verify failed., but this one disappeared after restarting the cRIO, and now it works perfectly.

Thanks! 

[rdecarre11]

This appears to have fixed my issue as well. I can now send messages using AMQP