MiCollab Next Gen?

[NEPhoneGuy]

Support on Friday was telling me that my failed to connect to server error with the MiCollab desktop and web based client is because I need a third party i.e godaddy or the like cert and that the built in cert isn't good enough. This is for access on a local network only. The hostname resolves okay - seem fishy to anyone else?

[sarond]

I have heard that it needs a valid ssl cert but I don't deploy a lot of apps.

Can you use Letsencrypt? I know this might not be possible if you don't have a publicly accessible FQDN.

[NEPhoneGuy]

I have heard that it needs a valid ssl cert but I don't deploy a lot of apps.

Can you use Letsencrypt? I know this might not be possible if you don't have a publicly accessible FQDN.

Going to have to figure something out. This is actually for an inhouse system - need to get a good grasp on it so we can push it's use out to our customers. Just thought it was weird because I was just trying to get stuff to work internally before anything else

[VinceWhirlwind]

You need a 3rd party certificate if you're using MiCollab Mobile.
Check the MiCollab Server online help chapter called "About SSL Web Server Certificates".

[Tom2018]

for the inhouse you don't need a third party cert. But your Desktop-Client and browser must trust the served cert from MiCollab Server.
So you could create your own cert from your AD or similar and import the CA  to your Client (if not done yet).

A official third party cert and FQDN is needed if you want to deploy the MiCollab to your smartphone over the Mitel redirection server.

regards,
Tom