I use Let's Encrypt on my inmotionhosting account to provide SSL to all of my many domains. My most important domain, firealarm.com, shows a conglomerate of all of my domain's SSL certificates when you go to view the site's certificate. Right now, the primary domain SSL certificate for firealarm.com is www.staneyeware.com, which is not correct and should not be shown.
I want the primary SSL for firealarm.com to only be the firealarm.com certificate, not any other domains. Is this something that can be fixed? Can I have these domains show only one (1) SSL and not multiple? See picture attached.
Yes, technically it is possible to have just domain names related to firealarm.com in their own certificate. But, how you do that is best addressed to your hosting company. They may not allow it with your account level or how they have their admin system structured.
I see you are using cPanel.
It is very common practice for such panels to combine multiple sites onto one single cert.
If that is a "problem" (can't see why) to you, you might want to speak with InMotion and see if they can get it to assign your site an individual cert.
I spoke to InMotion and they said that the reason they are bunched together is due to Let's Encrypt's protocols/method of assigning SSL's. They said in order to have individual SSL's for individual domains, which is what I want, then I would need to switch over to their cPanel SSL protocol which is slower, and less reliable than Let's Encrypt.
Any insight into that? There's nothing I can do with Let's Encrypt to change this?
I see what you said they said.
But none of that makes any sense.
LE doesn't control the request being made and can't combine multiple requests together into one cert.
If the names are on one cert, then they were requested together (in one request).
As for as a "slower protocol"... that sounds ridiculous.
There is only one protocol: ACME
How I interpret what they said is they have setup their automated cPanel system for Let's Encrypt to combine all the domain names from your account in one cert. And, if you want only certain names in a separate cert they can do it manually but this is less reliable and more time consuming. Perhaps even an extra charge.
I agree with Rudy. This is a choice your hosting service has made as to how they integrated Let's Encrypt in their system. Let's Encrypt makes certs the way you tell it to. Only your hosting service can change how they request the LE certs.
This all said, there is nothing wrong with your cert. It works perfectly fine just as it is for all the domain names within it.
I guess I need someone else from InMotion to assist because that is verbatim what was said to me. They said nothing regarding "requesting" the SSL's on their end. As far as being slower, they're referring to the Delivery Times shown in the attached screenshot from the cPanel/WHM Root settings. LE's is 5 seconds, cPanel's is 2 minutes, and they said that cPanel SSL has been slow in general.
This is the location where I would switch back to cPanel's SSL.