• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Apache SSL Listen Error

M

md3vxx

Guest
Plesk 10.4.4 Update #9, CentOS 6.2 x64

We have modified /etc/httpd/conf.d/ssl.conf to only have Apache HTTPS listen on three of our IP addresses, e.g. -

Listen 222.11.33.91:443
Listen 222.11.33.92:443
Listen 222.11.33.93:443

And commented out the default:

Listen 443

When we restart Apache it fails to load:

[root@s2 conf.d]# /etc/init.d/httpd restart
Stopping httpd: [OK]
Starting httpd: [FAILED]

And /var/log/httpd/error_log states:

[error] Server should be SSL-aware but has no certificate configured [Hint: SSLCertificateFile] ((null):0)

We've been unable to find a solution for this problem.
 
If its un-commented the same error occurs.

How can I put a bug notice into Parallels regarding this issue?
 
It isn't necessarily a Plesk issue. You are modifying ssl.conf and by doing so apache won't start. You need to check the syntax of everything you have changed carefully.

Of course it could be that some other configuration file and your changes don't want to play together. Again this would not be a Plesk bug.

I'm not saying it ISN'T a Plesk bug ...just saying that on the face of it, it doesn't sound like it is.

Going back to the error, uncommenting the line isn't necesarily enough. You may need to make sure it points to the correct place.
 
You did common Apache but not Plesk configuration. Therefore use Apache documentation for proper configuration. This issue is not related to Plesk.
 
Since we have no issue with this configuration on two other boxes running CentOS 6.2 and WebMin for hosting management, it appears to be a Plesk 10 issue. We also have no issue with implementing this configuration in Plesk 9.

You mentioned "You did common Apache but not Plesk configuration" but no outline or suggestion or relevant documentation.
 
Hello, md3vxx. Thank you for reporting.

Since we have no issue with this configuration on two other boxes running CentOS 6.2 and WebMin for hosting management, it appears to be a Plesk 10 issue. We also have no issue with implementing this configuration in Plesk 9.

You are right. Plesk Service has accepted the issue. Bug fix has been scheduled for future updates.

As temporary workaround you can remove 4 strings from /usr/local/psa/admin/conf/templates/default/server.php:

# diff -u server.php.orig /usr/local/psa/admin/conf/templates/default/server.php
--- server.php.orig 2011-12-30 11:41:48.688797964 +0700
+++ /usr/local/psa/admin/conf/templates/default/server.php 2011-12-30 11:48:57.326811689 +0700
@@ -77,7 +77,3 @@
'ssl' => false,
'ipLimit' => $VAR->server->webserver->apache->vhostIpCapacity,
)) ?>
-<?php echo $VAR->includeTemplate('server/mailman.php', array(
- 'ssl' => true,
- 'ipLimit' => $VAR->server->webserver->apache->vhostIpCapacity,
-)) ?>

and re-generate configs:
# /usr/local/psa/admin/sbin/httpdmng --reconfigure-all

You mentioned "You did common Apache but not Plesk configuration" but no outline or suggestion or relevant documentation.

I'd recommend you to learn more about Apache configuration templates here http://download1.parallels.com/Ples...nistration-guide/index.htm?fileName=68625.htm
 
Back
Top