Author Topic: incorrect common name for ssl  (Read 401 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
incorrect common name for ssl
« on: December 05, 2018, 08:46:00 AM »

  After the last update ( a day ago ) I required an SSL for a domain. After using the nice SSL Manager in the CWP Admin webpage i was unable to create the SSL however accessing the site the (https://www.sitename.com) without the warning being displayed in the browser ( incorrect common name ).

I then noticed the SSL Generated failed to update /usr/local/apache/conf.d/vhosts-ssl.conf with the newly created SSL for the sitename.com
( yes - i did reboot server )

i added the information manually (copied and paste ) from the file created in /usr/local/apache/conf.d/vhosts/sitename.conf
to /usr/local/apache/conf.d/vhosts-ssl.conf
and then everything worked properly.

---- should this not be handled automatically ?

Offline
*
Re: incorrect common name for ssl
« Reply #1 on: January 27, 2019, 12:50:56 AM »
I'm still having issues with this evening when the information is transferred over, the cert won't allow www.xxxxx.xx to be used.  Any ideas? On my other server prior to the PHP_FPM updates, it works perfectly.  Frustration has set in on setting up a new server. :(