1

Topic: iRedAdmin won't display, can't access

After installing iRedMail-0.6.1.tar.bz2 on CentOS 5.5, I can't access iRedAdmin, roundcube,phpldapadmin,phpmyadmin are all ok.  I've set settings.ini debug=True, but nothing appears on logs.  Here are my logs:

/var/log/httpd/ssl_error_log

[Sun Sep 05 04:02:14 2010] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Sun Sep 05 17:01:51 2010] [error] [client 127.0.0.1] Premature end of script headers: iredadmin.py
[Sun Sep 05 17:01:51 2010] [error] [client 127.0.0.1] Premature end of script headers: iredadmin.py
[Sun Sep 05 17:01:51 2010] [error] [client 112.198.143.44] Premature end of script headers: iredadmin.py
[Sun Sep 05 17:01:51 2010] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Sun Sep 05 17:02:02 2010] [error] [client 127.0.0.1] File does not exist: /var/www/html/favicon.ico
[Sun Sep 05 17:02:05 2010] [error] [client 127.0.0.1] File does not exist: /var/www/html/favicon.ico
[Sun Sep 05 17:08:38 2010] [error] [client 127.0.0.1] Premature end of script headers: iredadmin.py
[Sun Sep 05 17:08:38 2010] [error] [client 127.0.0.1] Premature end of script headers: iredadmin.py
[Sun Sep 05 17:08:38 2010] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Sun Sep 05 17:10:17 2010] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Sun Sep 05 17:10:17 2010] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Sun Sep 05 17:32:35 2010] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)



/var/log/httpd/access_log

::1 - - [05/Sep/2010:17:08:38 +0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache (internal dummy connection)"
::1 - - [05/Sep/2010:17:08:38 +0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache (internal dummy connection)"
127.0.0.1 - - [05/Sep/2010:17:10:24 +0800] "GET /favicon.ico HTTP/1.1" 404 304 "-" "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100726 CentOS/3.6-3.el5.centos Firefox/3.6.7"
::1 - - [05/Sep/2010:17:32:35 +0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache (internal dummy connection)"
::1 - - [05/Sep/2010:17:32:35 +0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache (internal dummy connection)"
112.198.143.44 - - [05/Sep/2010:17:10:41 +0800] "GET /iredadmin HTTP/1.1" 500 639 "-" "Mozilla/5.0 (Windows NT 6.1; rv:2.0b4) Gecko/20100818 Firefox/4.0b4"
112.198.143.44 - - [05/Sep/2010:17:17:48 +0800] "GET /iredadmin HTTP/1.1" 500 639 "-" "Mozilla/5.0 (Windows NT 6.1; rv:2.0b4) Gecko/20100818 Firefox/4.0b4"
127.0.0.1 - - [05/Sep/2010:17:12:40 +0800] "GET /iredadmin HTTP/1.1" 500 629 "-" "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100726 CentOS/3.6-3.el5.centos Firefox/3.6.7"
::1 - - [05/Sep/2010:17:32:35 +0800] "OPTIONS * HTTP/1.0" 200 - "-" "Apache (internal dummy connection)"



/etc/httpd/logs/error_log

[Sun Sep 05 17:10:17 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Sep 05 17:10:17 2010] [notice] Digest: generating secret for digest authentication ...
[Sun Sep 05 17:10:17 2010] [notice] Digest: done
[Sun Sep 05 17:10:17 2010] [notice] mod_python: Creating 4 session mutexes based on 256 max processes and 0 max threads.
[Sun Sep 05 17:10:17 2010] [notice] Apache configured -- resuming normal operations
[Sun Sep 05 17:10:24 2010] [error] [client 127.0.0.1] File does not exist: /var/www/html/favicon.ico
[Sun Sep 05 17:32:35 2010] [notice] Graceful restart requested, doing restart
[Sun Sep 05 17:32:35 2010] [error] [client 112.198.143.44] Premature end of script headers: iredadmin.py
[Sun Sep 05 17:32:35 2010] [error] [client 112.198.143.44] Premature end of script headers: iredadmin.py
[Sun Sep 05 17:32:35 2010] [error] [client 127.0.0.1] Premature end of script headers: iredadmin.py
[Sun Sep 05 17:32:35 2010] [notice] Digest: generating secret for digest authentication ...
[Sun Sep 05 17:32:35 2010] [notice] Digest: done
[Sun Sep 05 17:32:35 2010] [notice] mod_python: Creating 4 session mutexes based on 256 max processes and 0 max threads.
[Sun Sep 05 17:32:35 2010] [notice] Apache configured -- resuming normal operations


Please help me on my setup.


Thanks and More Power to iRedMail.....

2

Re: iRedAdmin won't display, can't access

[Sun Sep 05 17:01:51 2010] [error] [client 127.0.0.1] Premature end of script headers: iredadmin.py

Seems there's something wrong in your apache config file.
Can you please post your /etc/httpd/conf.d/iredadmin.conf?
Also, can you please set "LogLevel debug" in /etc/httpd/conf/httpd.conf to get more detail of Apache?

3

Re: iRedAdmin won't display, can't access

/etc/httpd/conf.d/iredadmin.conf


#
# Note: Uncomment below two lines if you want to make iRedAdmin accessable via HTTP.
#
#WSGIScriptAlias /iredadmin /var/www/iredadmin/iredadmin.py/
#Alias /iredadmin/static /var/www/iredadmin/static/

WSGISocketPrefix /var/run/wsgi
WSGIDaemonProcess iredadmin user=iredadmin threads=15
WSGIProcessGroup iredadmin

AddType text/html .py

<Directory /var/www/iredadmin/>
    Order deny,allow
    Allow from all
</Directory>

# Used to enable compress web contents during transfer.
DeflateCompressionLevel 3
AddOutputFilter DEFLATE html xml php js css
<Location />
SetOutputFilter DEFLATE
BrowserMatch ^Mozilla/4 gzip-only-text/html
BrowserMatch ^Mozilla/4\.0[678] no-gzip
BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
SetEnvIfNoCase Request_URI \.(?:gif|jpe?g|png)$ no-gzip dont-vary
SetEnvIfNoCase Request_URI .(?:exe|t?gz|zip|bz2|sit|rar)$ no-gzip dont-vary
SetEnvIfNoCase Request_URI .(?:pdf|mov|avi|mp3|mp4|rm)$ no-gzip dont-vary
Header append Vary User-Agent env=!dont-vary
</Location>

4

Re: iRedAdmin won't display, can't access

Here are the logs after turning on httpd.conf, loglevel debug


[Sun Sep 05 18:52:24 2010] [notice] Graceful restart requested, doing restart
[Sun Sep 05 18:52:24 2010] [notice] Digest: generating secret for digest authentication ...
[Sun Sep 05 18:52:24 2010] [notice] Digest: done
[Sun Sep 05 18:52:24 2010] [debug] util_ldap.c(2021): LDAP merging Shared Cache conf: shm=0x2b9b9e0cc0f8 rmm=0x2b9b9e0cc150 for VHOST: XXX.XXX.com.ph
[Sun Sep 05 18:52:24 2010] [info] APR LDAP: Built with OpenLDAP LDAP SDK
[Sun Sep 05 18:52:24 2010] [info] LDAP: SSL support available
[Sun Sep 05 18:52:24 2010] [notice] mod_python: Creating 4 session mutexes based on 256 max processes and 0 max threads.
[Sun Sep 05 18:52:24 2010] [info] Init: Seeding PRNG with 256 bytes of entropy
[Sun Sep 05 18:52:24 2010] [info] Init: Generating temporary RSA private keys (512/1024 bits)
[Sun Sep 05 18:52:24 2010] [info] Init: Generating temporary DH parameters (512/1024 bits)
[Sun Sep 05 18:52:24 2010] [debug] ssl_scache_shmcb.c(374): shmcb_init allocated 512000 bytes of shared memory
[Sun Sep 05 18:52:24 2010] [debug] ssl_scache_shmcb.c(554): entered shmcb_init_memory()
[Sun Sep 05 18:52:24 2010] [debug] ssl_scache_shmcb.c(576): for 512000 bytes, recommending 4265 indexes
[Sun Sep 05 18:52:24 2010] [debug] ssl_scache_shmcb.c(619): shmcb_init_memory choices follow
[Sun Sep 05 18:52:24 2010] [debug] ssl_scache_shmcb.c(621): division_mask = 0x1F
[Sun Sep 05 18:52:24 2010] [debug] ssl_scache_shmcb.c(623): division_offset = 96
[Sun Sep 05 18:52:24 2010] [debug] ssl_scache_shmcb.c(625): division_size = 15997
[Sun Sep 05 18:52:24 2010] [debug] ssl_scache_shmcb.c(627): queue_size = 2136
[Sun Sep 05 18:52:24 2010] [debug] ssl_scache_shmcb.c(629): index_num = 133
[Sun Sep 05 18:52:24 2010] [debug] ssl_scache_shmcb.c(631): index_offset = 8
[Sun Sep 05 18:52:24 2010] [debug] ssl_scache_shmcb.c(633): index_size = 16
[Sun Sep 05 18:52:24 2010] [debug] ssl_scache_shmcb.c(635): cache_data_offset = 8
[Sun Sep 05 18:52:24 2010] [debug] ssl_scache_shmcb.c(637): cache_data_size = 13853
[Sun Sep 05 18:52:24 2010] [debug] ssl_scache_shmcb.c(650): leaving shmcb_init_memory()
[Sun Sep 05 18:52:24 2010] [info] Shared memory session cache initialised
[Sun Sep 05 18:52:24 2010] [info] Init: Initializing (virtual) servers for SSL
[Sun Sep 05 18:52:24 2010] [info] Server: Apache/2.2.3, Interface: mod_ssl/2.2.3, Library: OpenSSL/0.9.8e-fips-rhel5
[Sun Sep 05 18:52:24 2010] [debug] mod_wsgi.c(9108): mod_wsgi (pid=14888): Reset default group for daemon process group 'iredadmin' to gid=48.
[Sun Sep 05 18:52:24 2010] [debug] mod_wsgi.c(8070): mod_wsgi (pid=14888): Socket for 'iredadmin' is '/var/run/wsgi.14888.2.1.sock'.
[Sun Sep 05 18:52:24 2010] [info] mod_wsgi (pid=16556): Starting process 'iredadmin' with uid=503, gid=48 and threads=15.
[Sun Sep 05 18:52:24 2010] [notice] Apache configured -- resuming normal operations
[Sun Sep 05 18:52:24 2010] [info] Server built: Aug 30 2010 12:28:40
[Sun Sep 05 18:52:24 2010] [debug] prefork.c(991): AcceptMutex: sysvsem (default: sysvsem)
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1854): proxy: grabbed scoreboard slot 0 in child 16557 for worker proxy:reverse
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1873): proxy: worker proxy:reverse already initialized
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1967): proxy: initialized single connection worker 0 in child 16557 for (*)
[Sun Sep 05 18:52:24 2010] [info] mod_wsgi (pid=16557): Attach interpreter ''.
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1854): proxy: grabbed scoreboard slot 0 in child 16558 for worker proxy:reverse
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1873): proxy: worker proxy:reverse already initialized
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1967): proxy: initialized single connection worker 0 in child 16558 for (*)
[Sun Sep 05 18:52:24 2010] [info] mod_wsgi (pid=16558): Attach interpreter ''.
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1854): proxy: grabbed scoreboard slot 0 in child 16559 for worker proxy:reverse
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1873): proxy: worker proxy:reverse already initialized
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1967): proxy: initialized single connection worker 0 in child 16559 for (*)
[Sun Sep 05 18:52:24 2010] [info] mod_wsgi (pid=16559): Attach interpreter ''.
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1854): proxy: grabbed scoreboard slot 0 in child 16560 for worker proxy:reverse
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1873): proxy: worker proxy:reverse already initialized
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1967): proxy: initialized single connection worker 0 in child 16560 for (*)
[Sun Sep 05 18:52:24 2010] [info] mod_wsgi (pid=16560): Attach interpreter ''.
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1854): proxy: grabbed scoreboard slot 0 in child 16561 for worker proxy:reverse
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1873): proxy: worker proxy:reverse already initialized
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1967): proxy: initialized single connection worker 0 in child 16561 for (*)
[Sun Sep 05 18:52:24 2010] [info] mod_wsgi (pid=16561): Attach interpreter ''.
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1854): proxy: grabbed scoreboard slot 0 in child 16562 for worker proxy:reverse
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1873): proxy: worker proxy:reverse already initialized
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1967): proxy: initialized single connection worker 0 in child 16562 for (*)
[Sun Sep 05 18:52:24 2010] [info] mod_wsgi (pid=16562): Attach interpreter ''.
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1854): proxy: grabbed scoreboard slot 0 in child 16563 for worker proxy:reverse
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1873): proxy: worker proxy:reverse already initialized
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1967): proxy: initialized single connection worker 0 in child 16563 for (*)
[Sun Sep 05 18:52:24 2010] [info] mod_wsgi (pid=16563): Attach interpreter ''.
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1854): proxy: grabbed scoreboard slot 0 in child 16564 for worker proxy:reverse
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1873): proxy: worker proxy:reverse already initialized
[Sun Sep 05 18:52:24 2010] [debug] proxy_util.c(1967): proxy: initialized single connection worker 0 in child 16564 for (*)
[Sun Sep 05 18:52:24 2010] [info] mod_wsgi (pid=16564): Attach interpreter ''.

5

Re: iRedAdmin won't display, can't access

So far so good.
Any log when you access iRedAdmin via web browser?

6

Re: iRedAdmin won't display, can't access

That was all the logs when I access iRedAdmin on my browser.  No error's or whatever message was display on my browser.

7

Re: iRedAdmin won't display, can't access

Any Idea what's wrong with my configuration?

8

Re: iRedAdmin won't display, can't access

Could you please give me output of below commands?

# ls -l /var/www/
# ls -l /var/www/iredadmin/

Also, can you please try to run iRedAdmin with below command:

# cd /var/www/iredadmin/
# python iredadmin.py

It will listen on port 8080, you can access it LOCALLY on your server with lynx or other web browser. If you want to access port 8080 remotely, please make sure you have this port open in iptables rules. You can simplify it by stop iptables service for testing, and start it again after testing:

# /etc/init.d/iptables stop

9

Re: iRedAdmin won't display, can't access

# ls -l /var/www/
drwxr-xr-x  9 root      root      4096 Sep  6 13:01 awstats
drwxr-xr-x  2 root      root      4096 Aug 31 00:32 cgi-bin
drwxr-xr-x  3 root      root      4096 Sep  3 16:23 error
drwxr-xr-x  2 root      root      4096 Sep  3 16:50 html
drwxr-xr-x  3 root      root      4096 Sep  3 16:23 icons
lrwxrwxrwx  1 root      root        24 Sep  3 16:51 iredadmin -> /var/www/iRedAdmin-0.1.3
drwxr-xr-x  8 iredadmin iredadmin 4096 Sep  5 19:06 iRedAdmin-0.1.3
drwxr-xr-x 14 root      root      4096 Sep  3 16:25 manual
lrwxrwxrwx  1 root      root        29 Sep  3 16:51 phpldapadmin -> /var/www/phpldapadmin-1.2.0.5
drwxr-xr-x 11 root      root      4096 Jan 30  2010 phpldapadmin-1.2.0.5
lrwxrwxrwx  1 root      root        41 Sep  3 16:51 phpmyadmin -> /var/www/phpMyAdmin-2.11.10-all-languages
drwxr-xr-x 10 root      root      4096 Sep  3 16:51 phpMyAdmin-2.11.10-all-languages
lrwxrwxrwx  1 root      root        28 Sep  3 16:51 roundcubemail -> /var/www/roundcubemail-0.3.1
drwxr-xr-x 11 root      root      4096 Oct 31  2009 roundcubemail-0.3.1
drwxr-xr-x  2 webalizer root      4096 Sep  4 04:02 usage

10

Re: iRedAdmin won't display, can't access

# ls -l

-rwxr-xr-x  1 iredadmin iredadmin   55 May 16 00:26 AUTHORS
-rwxr-xr-x  1 iredadmin iredadmin 1443 May 16 00:26 ChangLog
drwxr-xr-x  3 iredadmin iredadmin 4096 Sep  6 12:52 controllers
drwxr-xr-x  3 iredadmin iredadmin 4096 Sep  3 16:51 docs
drwxr-xr-x 11 iredadmin iredadmin 4096 Sep  3 16:51 i18n
-rwxr-xr-x  1 iredadmin iredadmin  349 May 16 00:26 INSTALL
-rwxr-xr-x  1 iredadmin iredadmin 1444 May 16 00:26 iredadmin.py
drwxr-xr-x  3 iredadmin iredadmin 4096 Sep  6 12:52 libs
-rw-------  1 iredadmin iredadmin 3667 Sep  4 09:23 settings.ini
-rwxr-xr-x  1 iredadmin iredadmin 3614 May 16 00:26 settings.ini.sample
drwxr-xr-x  4 iredadmin iredadmin 4096 Sep  3 16:51 static
drwxr-xr-x  3 iredadmin iredadmin 4096 May 16 00:26 templates

11

Re: iRedAdmin won't display, can't access

I already stop any firewall services

12

Re: iRedAdmin won't display, can't access

Did you try to run iRedAdmin with below command:

# cd /var/www/iredadmin/
# python iredadmin.py

When you access http://your_server:8080/, what's the output message on your terminal?

13

Re: iRedAdmin won't display, can't access

We have the same issue with a new installation: CentOS 5.5 and iRedMail 0.6.1
After installation iRedAdmin does not start, nothing is displayed.
I tried the command:

# cd /var/www/iredadmin/
# python iredadmin.py

Output:

[url]http://0.0.0.0:8080/[/url]

With the browser on the local machine I accessed this address and I got the error message:

ldap.INVALID_CREDENTIALS

I checked the LDAP credentials in /var/www/iredadmin/settings.ini and the settings were ok. Then I tried to look in the phpLdapAdmin, but after login nothing was shown. I was prompted: 'This base entry does not exist.Create it?'
There was no structure/tree at all in de LDAP.

How can I solve this ?

14

Re: iRedAdmin won't display, can't access

You can populate LDAP tree with /path/to/iRedMail-x.y.z/conf/ldap_init.ldif. This file is generated during installation.

15 (edited by knockers 2010-09-08 16:45:51)

Re: iRedAdmin won't display, can't access

Thank you, we are getting a step further now....
I imported the tree in LDAP, I started iredadmin.py manually again, as before. With the browser on the server I now see the iRedAdmin login screen.
I stopped the iredadmin.py script and tried to access iRedAdmin from my pc -> https://<server_ip>/iredadmin
Still nothing is displayed......

When I enable http I can access the iRedAdmin login screen with http://<server_ip>:8080

Why is https not functioning now and can I access it through http, although not enabled in iredamin.conf ?

16

Re: iRedAdmin won't display, can't access

You should check apache error log first. it should be /var/log/httpd/error_log or /var/log/httpd/ssl_error_log. Post related log content here so that others can help you troubleshoot this issue.

17

Re: iRedAdmin won't display, can't access

I had checked those log files before, and I checked again now, but no log entries in the files when I access https://<server_ip>/iredadmin
In the access_log and the ssl_access_log files no log entries either...

Where can I start looking for the error ?
When I install using iRedOS this functions out-of-box, I thought with the separate installation of iRedMail this would also be the case.

18

Re: iRedAdmin won't display, can't access

Can you login into iRedAdmin with http://<server ip>:8080/? If it works, iRedAdmin should be ok, the problem is apache config.
Maybe you can try to restart apache for a test? Also, can you paste config in /etc/httpd/conf.d/iredadmin.conf and /etc/httpd/conf.d/ssl.conf?

if no log, i don't know how to troubleshoot it.

19

Re: iRedAdmin won't display, can't access

If I enable http, I can access http://<server_ip>:8080

iredadmin.conf

#
# Note: Uncomment below two lines if you want to make iRedAdmin accessable via HTTP.
#
#WSGIScriptAlias /iredadmin /var/www/iredadmin/iredadmin.py/
#Alias /iredadmin/static /var/www/iredadmin/static/

WSGISocketPrefix /var/run/wsgi
WSGIDaemonProcess iredadmin user=iredadmin threads=15
WSGIProcessGroup iredadmin

AddType text/html .py

<Directory /var/www/iredadmin/>
    Order deny,allow
    Allow from all
</Directory>

# Used to enable compress web contents during transfer.
DeflateCompressionLevel 3
AddOutputFilter DEFLATE html xml php js css
<Location />
SetOutputFilter DEFLATE
BrowserMatch ^Mozilla/4 gzip-only-text/html
BrowserMatch ^Mozilla/4\.0[678] no-gzip
BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
SetEnvIfNoCase Request_URI \.(?:gif|jpe?g|png)$ no-gzip dont-vary
SetEnvIfNoCase Request_URI .(?:exe|t?gz|zip|bz2|sit|rar)$ no-gzip dont-vary
SetEnvIfNoCase Request_URI .(?:pdf|mov|avi|mp3|mp4|rm)$ no-gzip dont-vary
#Header append Vary User-Agent env=!dont-vary
</Location>

ssl.conf

#
# This is the Apache server configuration file providing SSL support.
# It contains the configuration directives to instruct the server how to
# serve pages over an https connection. For detailing information about these 
# directives see <URL:http://httpd.apache.org/docs/2.2/mod/mod_ssl.html>
# 
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.  
#

LoadModule ssl_module modules/mod_ssl.so

#
# When we also provide SSL we have to listen to the 
# the HTTPS port in addition.
#
Listen 443

##
##  SSL Global Context
##
##  All SSL configuration in this context applies both to
##  the main server and all SSL-enabled virtual hosts.
##

#
#   Some MIME-types for downloading Certificates and CRLs
#
AddType application/x-x509-ca-cert .crt
AddType application/x-pkcs7-crl    .crl

#   Pass Phrase Dialog:
#   Configure the pass phrase gathering process.
#   The filtering dialog program (`builtin' is a internal
#   terminal dialog) has to provide the pass phrase on stdout.
SSLPassPhraseDialog  builtin

#   Inter-Process Session Cache:
#   Configure the SSL Session Cache: First the mechanism 
#   to use and second the expiring timeout (in seconds).
#SSLSessionCache        dc:UNIX:/var/cache/mod_ssl/distcache
SSLSessionCache         shmcb:/var/cache/mod_ssl/scache(512000)
SSLSessionCacheTimeout  300

#   Semaphore:
#   Configure the path to the mutual exclusion semaphore the
#   SSL engine uses internally for inter-process synchronization. 
SSLMutex default

#   Pseudo Random Number Generator (PRNG):
#   Configure one or more sources to seed the PRNG of the 
#   SSL library. The seed data should be of good random quality.
#   WARNING! On some platforms /dev/random blocks if not enough entropy
#   is available. This means you then cannot use the /dev/random device
#   because it would lead to very long connection times (as long as
#   it requires to make more entropy available). But usually those
#   platforms additionally provide a /dev/urandom device which doesn't
#   block. So, if available, use this one instead. Read the mod_ssl User
#   Manual for more details.
SSLRandomSeed startup file:/dev/urandom  256
SSLRandomSeed connect builtin
#SSLRandomSeed startup file:/dev/random  512
#SSLRandomSeed connect file:/dev/random  512
#SSLRandomSeed connect file:/dev/urandom 512

#
# Use "SSLCryptoDevice" to enable any supported hardware
# accelerators. Use "openssl engine -v" to list supported
# engine names.  NOTE: If you enable an accelerator and the
# server does not start, consult the error logs and ensure
# your accelerator is functioning properly. 
#
SSLCryptoDevice builtin
#SSLCryptoDevice ubsec

##
## SSL Virtual Host Context
##

<VirtualHost _default_:443>

# General setup for the virtual host, inherited from global configuration
#DocumentRoot "/var/www/html"
#ServerName [url=http://www.example.com:443]www.example.com:443[/url]

# Use separate log files for the SSL virtual host; note that LogLevel
# is not inherited from httpd.conf.
ErrorLog logs/ssl_error_log
TransferLog logs/ssl_access_log
LogLevel warn

#   SSL Engine Switch:
#   Enable/Disable SSL for this virtual host.
SSLEngine on

#   SSL Protocol support:
# List the enable protocol levels with which clients will be able to
# connect.  Disable SSLv2 access by default:
SSLProtocol all -SSLv2

#   SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate.
# See the mod_ssl documentation for a complete list.
SSLCipherSuite ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW

#   Server Certificate:
# Point SSLCertificateFile at a PEM encoded certificate.  If
# the certificate is encrypted, then you will be prompted for a
# pass phrase.  Note that a kill -HUP will prompt again.  A new
# certificate can be generated using the genkey(1) command.
SSLCertificateFile /etc/pki/tls/certs/iRedMail_CA.pem

#   Server Private Key:
#   If the key is not combined with the certificate, use this
#   directive to point at the key file.  Keep in mind that if
#   you've both a RSA and a DSA private key you can configure
#   both in parallel (to also allow the use of DSA ciphers, etc.)
SSLCertificateKeyFile /etc/pki/tls/private/iRedMail.key

#   Server Certificate Chain:
#   Point SSLCertificateChainFile at a file containing the
#   concatenation of PEM encoded CA certificates which form the
#   certificate chain for the server certificate. Alternatively
#   the referenced file can be the same as SSLCertificateFile
#   when the CA certificates are directly appended to the server
#   certificate for convinience.
#SSLCertificateChainFile /etc/pki/tls/certs/server-chain.crt

#   Certificate Authority (CA):
#   Set the CA certificate verification path where to find CA
#   certificates for client authentication or alternatively one
#   huge file containing all of them (file must be PEM encoded)
#SSLCACertificateFile /etc/pki/tls/certs/ca-bundle.crt

#   Client Authentication (Type):
#   Client certificate verification type and depth.  Types are
#   none, optional, require and optional_no_ca.  Depth is a
#   number which specifies how deeply to verify the certificate
#   issuer chain before deciding the certificate is not valid.
#SSLVerifyClient require
#SSLVerifyDepth  10

#   Access Control:
#   With SSLRequire you can do per-directory access control based
#   on arbitrary complex boolean expressions containing server
#   variable checks and other lookup directives.  The syntax is a
#   mixture between C and Perl.  See the mod_ssl documentation
#   for more details.
#<Location />
#SSLRequire (    %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
#            and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
#            and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
#            and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
#            and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20       ) \
#           or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
#</Location>

#   SSL Engine Options:
#   Set various options for the SSL engine.
#   o FakeBasicAuth:
#     Translate the client X.509 into a Basic Authorisation.  This means that
#     the standard Auth/DBMAuth methods can be used for access control.  The
#     user name is the `one line' version of the client's X.509 certificate.
#     Note that no password is obtained from the user. Every entry in the user
#     file needs this password: `xxj31ZMTZzkVA'.
#   o ExportCertData:
#     This exports two additional environment variables: SSL_CLIENT_CERT and
#     SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
#     server (always existing) and the client (only existing when client
#     authentication is used). This can be used to import the certificates
#     into CGI scripts.
#   o StdEnvVars:
#     This exports the standard SSL/TLS related `SSL_*' environment variables.
#     Per default this exportation is switched off for performance reasons,
#     because the extraction step is an expensive operation and is usually
#     useless for serving static content. So one usually enables the
#     exportation for CGI and SSI requests only.
#   o StrictRequire:
#     This denies access when "SSLRequireSSL" or "SSLRequire" applied even
#     under a "Satisfy any" situation, i.e. when it applies access is denied
#     and no other module can change it.
#   o OptRenegotiate:
#     This enables optimized SSL connection renegotiation handling when SSL
#     directives are used in per-directory context. 
#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
<Files ~ "\.(cgi|shtml|phtml|php3?)$">
    SSLOptions +StdEnvVars
</Files>
<Directory "/var/www/cgi-bin">
    SSLOptions +StdEnvVars
</Directory>

#   SSL Protocol Adjustments:
#   The safe and default but still SSL/TLS standard compliant shutdown
#   approach is that mod_ssl sends the close notify alert but doesn't wait for
#   the close notify alert from client. When you need a different shutdown
#   approach you can use one of the following variables:
#   o ssl-unclean-shutdown:
#     This forces an unclean shutdown when the connection is closed, i.e. no
#     SSL close notify alert is send or allowed to received.  This violates
#     the SSL/TLS standard but is needed for some brain-dead browsers. Use
#     this when you receive I/O errors because of the standard approach where
#     mod_ssl sends the close notify alert.
#   o ssl-accurate-shutdown:
#     This forces an accurate shutdown when the connection is closed, i.e. a
#     SSL close notify alert is send and mod_ssl waits for the close notify
#     alert of the client. This is 100% SSL/TLS standard compliant, but in
#     practice often causes hanging connections with brain-dead browsers. Use
#     this only for browsers where you know that their SSL implementation
#     works correctly. 
#   Notice: Most problems of broken clients are also related to the HTTP
#   keep-alive facility, so you usually additionally want to disable
#   keep-alive for those clients, too. Use variable "nokeepalive" for this.
#   Similarly, one has to force some clients to use HTTP/1.0 to workaround
#   their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
#   "force-response-1.0" for this.
SetEnvIf User-Agent ".*MSIE.*" \
         nokeepalive ssl-unclean-shutdown \
         downgrade-1.0 force-response-1.0

#   Per-Server Logging:
#   The home of a custom SSL log file. Use this when you want a
#   compact non-error SSL logfile on a virtual host basis.
CustomLog logs/ssl_request_log \
          "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"

Alias /mail "/var/www/roundcubemail/"
Alias /webmail "/var/www/roundcubemail/"
Alias /roundcube "/var/www/roundcubemail/"
Alias /phpldapadmin "/var/www/phpldapadmin/"
Alias /ldap "/var/www/phpldapadmin/"
Alias /phpmyadmin "/var/www/phpmyadmin/"
Alias /mysql "/var/www/phpmyadmin/"
Alias /awstats/icon "/var/www/awstats/icon/"
ScriptAlias /awstats "/var/www/awstats/"
WSGIScriptAlias /iredadmin "/var/www/iredadmin/iredadmin.py/"
Alias /iredadmin/static "/var/www/iredadmin/static/"
</VirtualHost>                                  

20

Re: iRedAdmin won't display, can't access

Apache config looks OK. You should find out related apache log to help troubleshoot.

I will test it later with a fresh installation. Thanks for your feedback. smile

21

Re: iRedAdmin won't display, can't access

Thank you for helping me out. I'll wait for your findings with a new fresh installation.
I just started a new installation myself in an VMWare machine. If I find something new, I will post it here.

22

Re: iRedAdmin won't display, can't access

With my new install it all works fine.
A few things were different from the previous install:
- I installed a rather 'basic' CentOS 5.5 without the iRedMail tools Postfix, MySQL and Apache
- I did a full update of all installed software with yum update
- During install of iRedMail I accepted all default values except one: the firewall rules, I did not use the firewall rules of iRedMail.

After install it all worked fine, I could access iRedAdmin immediately

I am not sure what the problem was in the previous install: the firewall? yum update ? pre-installed MySQL, Apache etc ?

Hopefully this information is usefull for you

23

Re: iRedAdmin won't display, can't access

I installed iRedMail-0.6.1 (actually, it's trunk version) on CentOS 5.5 i386, works fine for me.

24

Re: iRedAdmin won't display, can't access

How did you install CentOS ? With apache, MySQL, Postfix ? Or without ?
Did you update CentOS with yum before installing iRedMail ?
Did you apply the firewall rules supplied by iRedMail ?

25

Re: iRedAdmin won't display, can't access

knockers wrote:

How did you install CentOS ? With apache, MySQL, Postfix ? Or without ?
Did you update CentOS with yum before installing iRedMail ?
Did you apply the firewall rules supplied by iRedMail ?

A fresh installation, minimal, without apache, mysql, postfix, etc.

It should be ok without update your system to latest packages.
Default iptables rules just blocks some network ports, but 80 is open by default.