+- CQC Community Support Forum (https://cqccommunity.com)
+-- Forum: Community General Discussion (https://cqccommunity.com/forumdisplay.php?fid=1)
+--- Forum: CQC Community Support for CQC-based automation systems. (https://cqccommunity.com/forumdisplay.php?fid=2)
+--- Thread: Anyone Having Issues wtih the Native Echo from NishanF (/showthread.php?tid=22)
Anyone Having Issues wtih the Native Echo from NishanF - kblagron - 08-27-2024
Once I had set up NishanF's native Echo setup, it has worked great until now.
Now it is failing while accepting security context. I will have to dig around the wayback machine to see if I can find some of the setup info NishanF wrote. It may be that AWS has changed something on their side to cause the error. I was using a secure port (non-standard) to send the info back to CQC, but apparently something has changed.
It could also be the CQC machine, but since I have updates turned off, I find it hard to believe something would change there.
RE: Anyone Having Issues wtih the Native Echo from NishanF - kblagron - 08-27-2024
I figured it out by going to AWS and seeing the logs which showed the server certificate had expired. Windows Server had already created a new one, but didn't delete the old one. CQC was seeing the old one. Once I deleted the old one, everything started working. Hopefully this will help someone - Probably me in about a year when the current certificate expires :-)