restore domain fails on SSL feature

1 post / 0 new
#1 Tue, 12/15/2015 - 12:36
ckwsp101

restore domain fails on SSL feature

Hi,

Production VIrtualmin 4.1.8gp/Centos 6.7

On new server Virtualmin 4.18.gpl/Centos 7.1

I am trying to import a production virtual domain to a new server. All domain features exported on production server. On new server import errors out on SSL feature. Legacy server used ip based SSL. New server starting with single shared ip. Only support SNI aware browsers. Any advice on how to determine what is wrong?

From Restore Virtual Servers

Apache SSL webserver configuration and certificate

 Creating SSL certificate and private key ..
.. openssl failed! OpenSSL error creating private key :
 
Generating a 2048 bit RSA private key
............................................+++
.............................................+++
writing new private key to '/tmp/.webmin/327034_2434_12_restore.cgi'
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [XX]:State or Province Name (full name) []:Locality Name (eg, city) [Default City]:Organization Name (eg, company) [Default Company Ltd]:Organizational Unit Name (eg, section) []:Common Name (eg, your name or your server's hostname) []:Email Address []:string is too long, it needs to be less than  64 bytes long
Email Address []:problems making Certificate Request
 
Adding new SSL virtual website ..
.. certificate file is not valid : Data does not start with line -----BEGIN CERTIFICATE-----
 
 
Applying web server configuration ..
.. done
 
.. failed! See the progress output above for the reason why.

See attached for complete log.

Could be corrupt virtual domain configuration on production server. On the new server attempt to enable the SSL feature on the partially restored domain results in a similar error Other domains moved to the new server with fewer issues.