• 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

Problems Installing Plesk 9.0.1

K

kcjames

Guest
I have installed Plesk 9.0.1 (full install) on a clean install of fc8 (web server).

Didn't see any issues during install. I just have the temp license installed for testing.

Nothing in the logs is indicating where the problem may be. httpd is running, psa is running, yet I can not browse to the IP or hostname and I can not browse to the admin interface.

The only weird issues are in the /var/log/httpd/error_log. They are as follows:

[Wed Mar 11 09:53:35 2009] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Wed Mar 11 09:53:35 2009] [warn] Init: SSL server IP/port conflict: atmail.webmail:443 (/etc/httpd/conf.d/zzz_atmail_vhost.conf:48) vs. horde.webmail:443 (/etc/httpd/conf.d/zzz_horde_vhost.conf:41)
[Wed Mar 11 09:53:35 2009] [warn] Init: SSL server IP/port conflict: default-192-168-1-2:443 (/etc/httpd/conf.d/zz010_psa_httpd.conf:78) vs. horde.webmail:443 (/etc/httpd/conf.d/zzz_horde_vhost.conf:41)
[Wed Mar 11 09:53:35 2009] [warn] Init: You should not use name-based virtual hosts in conjunction with SSL!!
[Wed Mar 11 09:53:35 2009] [notice] Apache/2.2.6 (Unix) DAV/2 mod_jk/1.2.15 PHP/5.2.6 mod_python/3.3.1 Python/2.5.1 mod_ssl/2.2.6 OpenSSL/0.9.8b mod_perl/2.0.3 Perl/v5.8.8 configured -- resuming normal operations
[Wed Mar 11 10:14:07 2009] [notice] caught SIGTERM, shutting down
[Wed Mar 11 10:14:08 2009] [notice] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Wed Mar 11 10:14:08 2009] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Wed Mar 11 10:14:08 2009] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Wed Mar 11 10:14:08 2009] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Wed Mar 11 10:14:08 2009] [warn] Init: SSL server IP/port conflict: atmail.webmail:443 (/etc/httpd/conf.d/zzz_atmail_vhost.conf:48) vs. horde.webmail:443 (/etc/httpd/conf.d/zzz_horde_vhost.conf:41)
[Wed Mar 11 10:14:08 2009] [warn] Init: SSL server IP/port conflict: default-192-168-1-2:443 (/etc/httpd/conf.d/zz010_psa_httpd.conf:78) vs. horde.webmail:443 (/etc/httpd/conf.d/zzz_horde_vhost.conf:41)
[Wed Mar 11 10:14:08 2009] [warn] Init: You should not use name-based virtual hosts in conjunction with SSL!!
[Wed Mar 11 10:14:08 2009] [notice] Digest: generating secret for digest authentication ...
[Wed Mar 11 10:14:08 2009] [notice] Digest: done
[Wed Mar 11 10:14:08 2009] [notice] mod_bw : Memory Allocated 0 bytes (each conf takes 28 bytes)
[Wed Mar 11 10:14:08 2009] [notice] mod_bw : Version 0.8 - Initialized [0 Confs]
[Wed Mar 11 10:14:08 2009] [notice] mod_python: Creating 4 session mutexes based on 256 max processes and 0 max threads.
[Wed Mar 11 10:14:08 2009] [notice] mod_python: using mutex_directory /tmp
[Wed Mar 11 10:14:08 2009] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Wed Mar 11 10:14:08 2009] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Wed Mar 11 10:14:08 2009] [warn] Init: SSL server IP/port conflict: atmail.webmail:443 (/etc/httpd/conf.d/zzz_atmail_vhost.conf:48) vs. horde.webmail:443 (/etc/httpd/conf.d/zzz_horde_vhost.conf:41)
[Wed Mar 11 10:14:08 2009] [warn] Init: SSL server IP/port conflict: default-192-168-1-2:443 (/etc/httpd/conf.d/zz010_psa_httpd.conf:78) vs. horde.webmail:443 (/etc/httpd/conf.d/zzz_horde_vhost.conf:41)
[Wed Mar 11 10:14:08 2009] [warn] Init: You should not use name-based virtual hosts in conjunction with SSL!!
[Wed Mar 11 10:14:08 2009] [notice] Apache/2.2.6 (Unix) DAV/2 mod_jk/1.2.15 PHP/5.2.6 mod_python/3.3.1 Python/2.5.1 mod_ssl/2.2.6 OpenSSL/0.9.8b mod_perl/2.0.3 Perl/v5.8.8 configured -- resuming normal operations

I'm lost. I have tried everything I can think of and the few search results I have been able to locate have been of no help.

Please help!
 
Sorry for double post. took so long for original I thought moderator /dev/null'd it.
 
Well I figured the problem out. Figures it was simplem, but I assumed parallels knew to setup iptables correctly, apparently not.

So iptables blockes all inbound traffic regardless of what the module config in the plesk cp says. I have to stop iptables to even access the server.

Any clues what I need to do to fix this issue so iptables will use the plesk rules, I don't really use iptables except on my plesk servers, so I am a newbie at using it.
 
and a kb search shows that is apprently a known bug they just don't tell anyone about or put in the documentation... so I had to turn of iptables, configure firewall, click activate, then preview and run the shell script from the command prompt.

For some reason it booted my ssh connection. I was able to relogin via ssh so no problems, and iptables is now running properly.

Seems like a major bug to be ignoring...
 
Back
Top