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

So I have a website (I'm using nginx). I can connect to just fine. But if I connect to then it says something about the connection is encrypted but there is resources on the page that are not. There are no resources on the page (and the pages are exactly the same whether they have 'www' or not).

The only thing I can figure is that maybe somehow cookies aren't encrypted?

How can I figure out the problem and how can I solve it (I need to figure out the problem first of course).

share|improve this question
up vote 0 down vote accepted

The error you describe shouldn't have anything to do with the hostname that is used to access the site (you would receive a different error stating that the certificate is issued to a different name). To fix the problem, try the solutions listed here:

share|improve this answer

If your SSL certificate is for then it will not work on or vice versa. An SSL certificate will only work for a specific domain (and in this case is considered a specific subdomain).

The only way around this is to get a wildcard SSL certificate which would work on both and

share|improve this answer

If you do not have a Wildcard SSL Certificate, you could use mod_rewrite to rewrite any request to to

RewriteEngine On
RewriteCond %{HTTPS} =on
RewriteCond %{HTTP_HOST} !^www\ [NC]
RewriteRule ^(.*)$1 [L,R=301]
share|improve this answer
Guy is using Nginx, Apache rules would not do him much good. – Martin Fjordvald Oct 1 '10 at 20:13

Your Answer


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

Not the answer you're looking for? Browse other questions tagged or ask your own question.