Certificate replicating upon connection to 800xA History


We are trying to set up Canary to connect to one of our 800xA History severs,  This is our first install of Canary.

Upon connection it generates a new self signed certificate that gets rejected.  We accept the self signed certificate and put in the trusted directory and then when we reconnect it generates a new duplicate certificate which gets rejected again even though that certificate already exists in the trusted directory. 

Our integrator has filed a ticket, but thought I would check to see if anyone had come across this issue previously and if there is a workaround/solution.


Reply Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
print this pagePrint this page
Like Follow
  • 1 mth agoLast active
  • 17Views
  • 1 Following