This topic contains 7 replies, has 3 voices, and was last updated by 
MSPControl 6 months, 2 weeks ago.
-
Posts
-
When creating or deleting a Let’s Encrypt SSL on one website, it will alter the SSL of another website.
Because all are using share IP, the wrong website will appear when query a website.
In summary, the binding of another website will be altered when adding or deleting a SSL in a website.
I would consider this case very serious and hope to find out the bug soon.Same bug as https://mspcontrol.org/forums/topic/deleted-https-443-bindings/
1 user thanked author for this post.
Hi, I can see one issue where SNI is not selected in IIS binding when add SSL via MSCP.
Even though we have enable SNI in MSCP > SERVER > IIS.
This should be fixed in 1.0.0.6332+
Still not fixed 🙁
Hi, when I create a new SSL for a new website, even though I enable SNI in MSPControl > Server > IIS.
It doesn’t enable SNI in IIS, this will mess up other websites that have SNI and SSL installed.
Other website SSL will show as unsigned.
So the main problem here is, even though I enable SNI in the control panel’s setting, it doesn’t enable SNI in IIS when I create a new SSL account.
Same here …
This is fixed in latest.
You must be logged in to reply to this topic.