Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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'm running a web app that is using websockets and have nginx as a reverse proxy for that and that works fine. I've also been able to get SSL to work without the socket. Now we're nearing the official launch and would be required to have SSL too.

Any ideas on how to make that happen? Here's my nginx config file:

server {
    listen               443 ssl;
    ssl                  on;
    ssl_certificate      /etc/nginx/server.crt;
    ssl_certificate_key  /etc/nginx/server.key;
    ssl_session_timeout  5m;
    ssl_protocols  SSLv2 SSLv3 TLSv1;
    ssl_ciphers  ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP;
    ssl_prefer_server_ciphers   on;

    listen 80;

    location / {
      proxy_pass http://localhost:8866;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection "upgrade";
      proxy_read_timeout 43200000;

    location /static/ {
        autoindex on;
        alias /home/xyz/.jenkins/jobs/app/workspace/main/static/;

share|improve this question
What's not working? What are you expecting and what is actually happening? Are you getting any errors? If so, what are they? – chrskly Jun 12 '13 at 21:41
Actually the config seemed to work as it is. The problem was with one of the URLs to my internal API being still hardcoded to use :http// – jesseniem Jun 13 '13 at 17:56

Your Answer


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

Browse other questions tagged or ask your own question.