http not working

chanjay · 06-01-2011, 06:30 PM

Hi,

I just installed SSL certificate (Verisign) on my Apache webserver. Everything works perfectly under https but not regular http. Some pages that use http will not be displayed.

Any idea? Please help!

Thanks.

hc.

Noway2 · 06-01-2011, 06:37 PM

Check in your apache error log. In most installations is it is a location like /var/log/httpd or /var/log/apache and then the log file will be error.log. This should give you a clear indication of why it did not resolve the page.

Without knowing the error message, it is nearly impossible to guess as to what the problem could be.

frieza · 06-01-2011, 06:49 PM

did you create a separate virtual host for both http (port 80) and https (port 443) ? both should be pointing at the same document root but the one with 443 should be configured to use the certificates and serve on port 443, the other shouldn't be configured to use any certificates and serve on port 80.

chanjay · 06-01-2011, 07:12 PM

Hi thanks for the replies,

I checked the error log (/etc/httpd/logs) and looks like there are no errors there.

I have 2 name-based host (domain1 and domain2) sharing same IP address, but the secured one is domain2.

Here are what is in my httpd.conf

Code:

Listen 80
.
.
.
<VirtualHost *>
        ServerSignature email
        DirectoryIndex index.htm index.html index.shtml index.php index.php4 index.php3 index.cgi
        LogLevel  warn
        HostNameLookups off
</VirtualHost>

<VirtualHost 12.34.56.78:80>
     ServerAdmin webmaster@domain1.com
     DocumentRoot /var/www/domain1/
     ServerName www.domain1.com
     ErrorLog logs/domain1.com-error_log
     CustomLog logs/domain1.com-access_log common
</VirtualHost>

<VirtualHost 12.34.56.78:80>
     ServerAdmin webmaster@domain2.com
     DocumentRoot /var/www/domain2/
     ServerName www.domain2.com
     ErrorLog logs/domain2-error_log
     CustomLog logs/domain2-access_log common
Redirect permanent / https://www.domain2.com
</VirtualHost>

<VirtualHost 12.34.56.78:80>
     ServerAdmin webmaster@domain1.com
     DocumentRoot /var/www/domain1/
     ServerName domain1.com
     ErrorLog logs/domain1.com-error_log
     CustomLog logs/domain1.com-access_log common
Redirect permanent / http://www.domain1.com
</VirtualHost>

<VirtualHost 12.34.56.78:80>
     ServerAdmin webmaster@domain2.com
     DocumentRoot /var/www/domain2/
     ServerName domain2.com
     ErrorLog logs/domain2-error_log
     CustomLog logs/domain2-access_log common
Redirect permanent / https://www.domain2.com
</VirtualHost>

<VirtualHost _default_:*>
     ServerAdmin webmaster@domain1.com
     DocumentRoot /var/www/domain1/
     ServerName www.domain1.com
     ErrorLog logs/domain1.com-error_log
     CustomLog logs/domain1.com-access_log common
</VirtualHost>

Here are what is in my ssl.conf

Code:

Listen 443
.
.
.
<VirtualHost www.domain2.com:443>
DocumentRoot "/var/www/domain2/"
ServerName www.domain2.com
ErrorLog logs/ssl_error_log
TransferLog logs/ssl_access_log
LogLevel warn
SSLEngine on
SSLProtocol all -SSLv2
SSLCipherSuite ALL:!ADH:!EXPORT:!
SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOWULL
SSLCertificateFile /etc/httpd/conf/ssl.crt/server.crt
SSLCertificateKeyFile /etc/httpd/conf/ssl.key/server.key
SSLCertificateChainFile /etc/httpd/conf/ssl.crt/intermediate.crt
SSLCACertificateFile /etc/httpd/conf/ssl.crt/intermediate.crt
<Location/>
</Location>
SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
<Files ~ "\.(cgi|shtml|phtml|php3?)$">
    SSLOptions +StdEnvVars
</Files>
<Directory "/var/www/cgi-bin">
    SSLOptions +StdEnvVars
</Directory>
SetEnvIf User-Agent ".*MSIE.*" \
         nokeepalive ssl-unclean-shutdown \
         downgrade-1.0 force-response-1.0
CustomLog logs/ssl_request_log \
          "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"

</VirtualHost>

Noway2 · 06-02-2011, 04:18 AM

I realize that you tried to sanitize your post against putting your real domain or address in your response, but you need to double check your httpd.conf because you have four hosts listed as <VirtualHost 12.34.56.78:80> with different document roots and it looks like you have duplicates. My understanding of Apache is that you have the choice of using NameVirtualHost or IP identified virtual hosts. If you are identifying the hosts with the IP address and they all have the same IP address, it will pick the first one that matches. Instead you should try using *:80 in the virtual host declaration and declare NameVirualHost *:80, somewhere like the top of your httpd.conf. Traditionally, this won't work with secured sites, but if you only have one, it is a non issue.

chanjay · 06-02-2011, 11:44 AM

Hi Noway2,

Thanks for the response...my boss didn't want me to expose the real company info here. Anyways, the httpd.conf was actually setup by the previous people who worked here before, with couple name-based virtual hosts (not IP identified) sharing the same IP address. I guess from my understanding, the virtual host duplicate purposes are for redirecting, for example "www.domain1.com" & "domain1.com" to "https://www.domain1.com".

I had tried to replace all <VirtualHost 12.34.56.78:80> with <VirtualHost *:80> and also Name VirtualHost *.80, then restart the httpd. I got "Error establising a database connection" on domain1 but domain2 still working with https.

hc.

Noway2 · 06-02-2011, 12:54 PM

Quote:

I got "Error establising a database connection" on domain1 but domain2 still working with https.

Domain1 and Domain2 are using different document roots with different source paths right? The error message sounds like you have a SQL backend to your web server and something is configured wrong in the database connection. Normally, in the scripting language, you will have a connection string with the user name, database, and password. I would double check that all of this is the same for both as it sounds like Domain1 is not able to establish the connection for some reason. Searching through the code for that particular error message should show you right where the connection is being attempted and failing too.

Wim Sturkenboom · 06-02-2011, 12:57 PM

I think that the error message "Error establising a database connection" is not pointing to an apache problem. It might be indicating that the website no longer can connect the database; time to look in the PHP files to see how it exactly works.

PS Noway2 beat me to it

chanjay · 06-02-2011, 01:12 PM

Domain1 site is actually just plain simple html & css with no database involved. This is strange, it is working on NameVirtualHost 12.34.56.78:80 & <VirtualHost 12.34.56.78:80> but not NameVirtualHost *:80 & <VirtualHost *:80>.

hc.