• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue IIS8.5 SSL Issue

MIchael Cockinos

New Pleskian
Hi Everyone,
I have recently installed Plesk Onyx on a Windows Server 2012 VM and configured WHMCS (eventually) to work with Plesk.

I have a strange problem with my SSL sites. I am unable to reach any SSL site using port 443 and the sites certificate, I can however reach if use port 8443 and select the correct certificate.

I have gone through everything I can think of including:
  1. Removing/Reinstalling the SSL certificate.
  2. Sifting through firewall rules. I have turned rules on and off and created new ones.
  3. running various command line tools to look for open ports etc.
  4. Tried difrerent browsers on different operating systems
And now I am pretty well stumped. No matter what I do, I can not connect to the server using 443.

For testing sake, please try https://www.redhot.com.au:8443 and https://www.redhot.com.au

You will see what I mean.

Any help in pointing me to the correct resource would be awesome.

Thanks in advance

Michael Cockinos
 
Hi MIchael Cockinos,

pls. note that the Plesk Control Panel has it's very own webserver called "sw-cp-server", while your hosted domains use either apache only, a combination of apache+nginx, or nginx only.

For your described issue, I did some investigations, which leads to to a problem with your used nameservers for your domain:


Pls. note, that the port 8443 is actually reserved for your Plesk Control Panel, while you get currently redirected to your hosted content for the domain "redhot.com.au" ( http ). This misconfiguration should be investigated by you as well. ;)
 
Hi and thanks for your reply,
I'm not sure why the DNS is reporting as such.

It doesn't explain why all the vhosts on the Windows IIS system won;t work on 443.
I used 8443 just as a test bed as I knew that was working *https://rh-wserv-003.redhot.com.au:8443) and I will remove that configuration from the IIS records.

Still I have the problem whereby I cannot connect to SSL443 for any domain (https://www.iluvboobs.com.au) and they only work on 80.

This is the probably the last and one of the most important steps to configure.

I can't find any irregularities in the windows logs either.
 
Hi MIchael Cockinos,

pls. note that the Plesk Control Panel has it's very own webserver called "sw-cp-server", while your hosted domains use either apache only, a combination of apache+nginx, or nginx only.

For your described issue, I did some investigations, which leads to to a problem with your used nameservers for your domain:


Pls. note, that the port 8443 is actually reserved for your Plesk Control Panel, while you get currently redirected to your hosted content for the domain "redhot.com.au" ( http ). This misconfiguration should be investigated by you as well. ;)
can someone help with this issue..................New configuration files for the Apache web server were not created due to the errors in configuration templates: Syntax error on line 48 of /etc/httpd/conf/plesk.conf.d/webmails/victorndaghakaonga.com_webmail.conf: SSLCertificateFile: file '/usr/local/psa/var/certificates/cert-eB6fzZ'
 
Back
Top