OK I have read a few posts in the forums about changing/securing the binding in IIS for SolidCP Portal.
The posts I read just were not clear on how to accomplish this in IIS.
Out of the box SolidCP Portal is binded to port 9001 and clients would need to use “http://IPADDRESS:9001” but that is not secure, puts the IP of the server out there and also makes the user have to remember to add the port to the url.
If Have a subdomain from a TLD I have hosted in SoldCP “loging.myTLD.com” and have already used LE to get a SSL cert for the subdomain. Can we use that subdomain to make SSL binding for the SolidCP Portal? I’m not sure how to do this because the binding is already being used for the subdomain.
I do not have any VPS’s or server farm, It is just 1 stand alone server with SolidCP runing on it (Server 2016)
Any advice / steps to follow to achieve this would be greatly appreciated
I understand your idea but please don’t believe that using a domain prevents the IP address of the server being public. This can easily be found by resolving the domain.
SolidCP is unable to set the portal domain. You can set this by making a custom domain and assigning a SSL but this has to be completed outside of the panel in IIS.
Thanks for the reply
Correct anyone can resolve the IP of the server, but I’m just trying to figure out how to use a custom domain for the panel login in IIS. Do I unbind the domain then bind it to the SolidCp portal in IIS?
Correct you would need to unbound the domain from the website and then bind it to the SolidCP Portal in IIS.
- Views1287 times
- Answers3 answers