This topic contains 7 replies, has 3 voices, and was last updated by MSPControl 1 month, 2 weeks ago.
-
AuthorPosts
-
December 7, 2018 at 5:34 am #9054
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.Like0Be the first one to like this.Please wait...December 7, 2018 at 9:07 am #9055Same bug as https://mspcontrol.org/forums/topic/deleted-https-443-bindings/
Like0Be the first one to like this.Please wait...1 user thanked author for this post.
December 7, 2018 at 9:23 pm #9057Hi, 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.
Like0Be the first one to like this.Please wait...December 13, 2018 at 8:21 pm #9068This should be fixed in 1.0.0.6332+
Like0Be the first one to like this.Please wait...December 19, 2018 at 6:49 am #9088Still not fixed 🙁
Like0Be the first one to like this.Please wait...December 21, 2018 at 1:33 am #9097Hi, 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.
Like22 people like this.Please wait...December 21, 2018 at 6:46 am #9100Same here …
Like0Be the first one to like this.Please wait...January 6, 2019 at 10:18 pm #9131This is fixed in latest.
Like0Be the first one to like this.Please wait... -
AuthorPosts
You must be logged in to reply to this topic.