Kaseya Community

SSL Certificate

Posted by LegacyPoster

on Apr 7, 2009 11:25 PM

Good Morning All,

As per requested by the powers that be. I have emplimented a SSL Certificate for our Kaseya Server. It is now https://msp.webdomain.com

Which works fine when you go the the webdomain and all the machines appear to be checking in. However since then I cannot use Remote Control to get into any of the machines. I have changed all the info except the port # I have left this at 5721.

Should this be 443 as well now that msp.webdomain.com is secure?

Legacy Forum Name: SSL Certificate,
Legacy Posted By Username: jm-ctaccess

Posted by LegacyPoster

on Apr 7, 2009 11:35 PM

Nevermind.

The 5721 traffic was not flowing to the correct IP address on our server.

Helps if I check through everything first.

Legacy Forum Name: General Discussion,
Legacy Posted By Username: jm-ctaccess

Posted by LegacyPoster

on Apr 8, 2009 1:59 AM

It's always the little things right in front of you...

Legacy Forum Name: General Discussion,
Legacy Posted By Username: Leadfoot

Posted by LegacyPoster

on Apr 9, 2009 4:11 AM

We are looking at integrating Autotask with Kaseya. We want to make sure the communication between Autotask and Kaseya is secure. Autotask requires that the Certificate be a third party, or you will have to connect via http. How do you install a Third Party Certerfication Authority on your Kaseya Server so you can login to Kaseya with SSL enabled? Did you install a third party or self signed certificate on your Kaseya server Jeff?

Legacy Forum Name: General Discussion,
Legacy Posted By Username: bmccaulley

Use a wildcard ssl certificate or not????

SSL Certificate Expiry

Gifting Kaseya an SSL Certificate

Install SSL certificate on VSA

SSL Certificate causes high cpu utilization

SSL Certificate