Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a virtual (CentOS) webserver running Apache. I have multiple websites running. Two websites share the same set of core files and have a common database. The files are "shared" via symlinks. Site1's files are the real files and site2's "files" are the symlinks of site1.

When browsing site2 in a non-SSL encrypted browser, the site works as intended. But as I try to view the site using the https protocol, the site appears to be empty. The SSL certificate was installed by the hosting company.

Any idea why this is happening?

share|improve this question

You may not have FollowSymLinks in the Options of the SSL vhost. The ssl vhost is distinct from the non-SSL vhost and has separate configuration. Both will inherit config from the default vhost config.

share|improve this answer

It is likely because the SSL certificate was certified for site1, but not for site2. This would explain why it would work for http but not for https. What are the two domain names?

share|improve this answer
No, it was created for site2, and has been installed in site2. – Rob Decker Jun 26 '10 at 3:19

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.