• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Reseller owned SSL logins to 8443

R

rspurlock

Guest
Hi all,

I couldn't find this answered anywhere but did find lots of folks wanting to change from 8443 to 443. I can keep 8443 but what I'm looking for is a way to load a reseller's SSL Cert so it shows when they send their customers to log in at their reseller url. An example:

reseller's URL: reseller.com
plesk server url: plesk01.plesk.com

My shared clients log in at https://plesk01.plesk.com:8443
The reseller's clients need to log in at https://www.reseller.com:8443

AND not get the SSL security warning and not get my ssl cert info. Basically how do I keep it separate and have it show up correctly based on the domain?

Possible?

I've tried this in the vhost_ssl.conf

ServerAlias admin.servername.com
SSLProxyEngine on
ProxyRequests off
ProxyPass / https://admin.servername.com:8443/
ProxyPassReverse / https://admin.servername.com:8443/

This allows the reseller's customer to go to something like https://admin.reseller.com and get the real cert, but it dies when going into the phpmyadmin. So how do I get around this little problem?

TIA,

Rob
 
Anyone?

Has no one come across this problem and/or found a resolution?

Will swsoft have more reseller tuning for future versions?
 
Assign the reseller their own Exclusive IP. Then put the reseller's domain on that IP. Then install an SSL certificate on the reseller's domain and assign it to the Exclusive IP. (You might also like to arrange for all the domains that the reseller adds to be on that same IP -[ in that case don't make the IP exclusive - make it Shared, but make the reseller's domain the Default for that IP ]- in order to keep them "separate" from your own.)

You'll need more than one IP for this obviously!

Please see http://forum.swsoft.com/showthread.php?s=&threadid=30857

Faris.
 
Hi Faris,

Thanks for the response but adding an ssl cert isn't the problem. what I'm trying to accomplish is a customer's cert for admin login (ie port 8443). The server, no matter what URL you add in for admin login will load the default server ssl cert when you log in via port 8443.

While setting up an ssl proxy for each domain is fine, it craps out when going into phpmyadmin.

Thoughts or is the a future possible "to do" item for swsoft?

Rob
 
Ah! I see what you mean. I've duplicated your issue. This is new to me. I assumed it just worked, even though 8443 and 80 are different webservers.

Have you tried uploading the cert into the admin certificate repository as well as the domain's certificate repository, then selecting the domain and clicking on Setup?

It might be worth trying that, and making the domain with the secure cert the default one for that IP.

Faris.
 
Back
Top