Wildcard SSL Certificate on Wildcard Subdomain in Plesk showing wrong certificate

[Pandy_Legend]

I have a new Plesk 12 installation. I have configured a domain (example.com) with hosting that also requires wildcard subdomains.

To achieve this I had to create a vhost.conf file with...

ServerAlias *.example.com

This works and I can go to http://anything.example.com with no issue.

I purchased a wildcard SSL certificate for *.example.com and successfully installed it.

If I go to https://example.com it works perfectly and shows the correct certificate, however if I go to https://anything.example.com it tells me the connection is untrusted, when I view the certificate, it shows the Parallels Plesk self certified certificate and not my purchased certificate.

I created a vhost_ssl.conf with

ServerAlias *.example.com
ServerAlias *.example.com:443 #tried with and without this line

If I add an exception in the browser, then I am taken to the correct place, albeit with the incorrect certificate.

Of course I have executed httpdmng --reconfigure-domain example.com and also tried a full reboot.

In summary:

http://example.com - works

http://anything.example.com - works

https://example.com works with my certificate

https://anything.example.com has Parallels certificate but routes to correct page

 

[IgorG]

I don't understand your manipulations with vhost_ssl.conf. I have used following scenario on my test server:

- Create domain domain.com
- Create subdomain *.domain.com
- Create certificate *.domain.com
- Assigned certificate on domain.com
- Assigned certificate on *.domain.com
- Check:
а. https://domain.com
б. https://mwa-ha.domain.com

In both cases I see certificate *.domain.com

No manipulations with vhost configs. All was done in Plesk UI.

 

[Pandy_Legend]

I don't wish to create a separate subdomain in Plesk - it is one hosting space. Same folder on the server. i.e. http://domain.com===http://mwa-ha.domain.com.
I originally tried to create a domain alias in Plesk, but this doesn't allow wildcards.
The manipulations with the vhost files were based on numerous suggestions to do so whilst Googling.

 

[Sergey_Ugdyzhekov]

You can specify the same document root for your subdomain.
http://example.com -> /httpdocs
http://*.example.com -> /httpdocs

 

[Pandy_Legend]

Will that not cause conflicts? Seems a little unnecessary to have two entries in the list for what is effectively the same thing.
Perhaps something to consider for the next release - wildcard domain alias?

 

[Pandy_Legend]

Seems to have worked, though got emailed an error:
Unable to generate the web server configuration file on the host <thsrvweb01.mydomain.com> because of the following errors:

Template_Exception: [Wed Dec 17 08:58:08.457227 2014] [so:warn] [pid 3639] AH01574: module actions_module is already loaded, skipping [Wed Dec 17 08:58:08.458114 2014] [so:warn] [pid 3639] AH01574: module auth_digest_module is already loaded, skipping [Wed Dec 17 08:58:08.458897 2014] [so:warn] [pid 3639] AH01574: module authz_user_module is already loaded, skipping [Wed Dec 17 08:58:08.460375 2014] [so:warn] [pid 3639] AH01574: module headers_module is already loaded, skipping [Wed Dec 17 08:58:08.460668 2014] [so:warn] [pid 3639] AH01574: module logio_module is already loaded, skipping [Wed Dec 17 08:58:08.461820 2014] [so:warn] [pid 3639] AH01574: module suexec_module is already loaded, skipping [Wed Dec 17 08:58:08.462244 2014] [so:warn] [pid 3639] AH01574: module dav_module is already loaded, skipping [Wed Dec 17 08:58:08.462255 2014] [so:warn] [pid 3639] AH01574: module dav_fs_module is already loaded, skipping

httpd: Syntax error on line 361 of /etc/httpd/conf/httpd.conf: Syntax error on line 8 of /etc/httpd/conf.d/zz010_psa_httpd.conf: Syntax error on line 119 of /etc/httpd/conf/plesk.conf.d/vhosts/mydomain.com.conf:

file: /usr/local/psa/admin/plib/Template/Writer/Webserver/Abstract.php

line: 75

code: 0

Please resolve the errors in web server configuration templates and generate the file again.