【问题标题】:Endless redirect loop with SSL nginx configuration带有 SSL nginx 配置的无休止的重定向循环
【发布时间】:2019-09-20 07:29:08
【问题描述】:

我配置了一些基本代理,然后运行了 certbot。不幸的是,它无休止地重定向了我。

我尝试了许多解决方案都无济于事。这些服务器块所在的其他是否有问题?任何帮助将不胜感激。

server {
    server_name www.example.com;
    return 301 https://example.com$request_uri;

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}

server {
    server_name example.com; # managed by Certbot

    listen [::]:443 ssl ipv6only=on; # managed by Certbot
    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

    location / {
      proxy_pass http://localhost:3000/;
      proxy_set_header X-Real-IP $remote_addr;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header X-NginX-Proxy true;
      proxy_set_header X-Forwarded-Proto $scheme;
      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection upgrade;
      proxy_set_header Host $host;
    }

    location /api/ {
      proxy_pass http://localhost:8000/;
      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection 'upgrade';
      proxy_set_header Host $host;
      proxy_cache_bypass $http_upgrade;
    }

}
server {
    listen 80;
    listen [::]:80 default_server;
    return 302 https://$host$request_uri;
}

server {
    if ($host = www.example.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

    server_name www.example.com;
    listen 80;
    return 404; # managed by Certbot
}

【问题讨论】:

  • 所有这些东西都由 Certbot 管理。它没有自己的配置吗?你不应该把那个提供给我们检查吗?
  • 事实证明,这是与 Cloudflare 相关的问题。配置没问题。

标签: ssl nginx certbot


【解决方案1】:

试试:

server {
    listen 80;
    listen [::]:80 default_server;
    server_name www.example.com example.com;
    return 302 https://$host$request_uri;
}

server {
    server_name www.example.com example.com; # managed by Certbot

    listen [::]:443 ssl ipv6only=on; # managed by Certbot
    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot

    location / {
      proxy_pass http://localhost:3000;
      proxy_set_header X-Real-IP $remote_addr;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header X-NginX-Proxy true;
      proxy_set_header X-Forwarded-Proto $scheme;
      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection upgrade;
      proxy_set_header Host $host;
    }

    location /api/ {
      proxy_pass http://localhost:8000;
      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection 'upgrade';
      proxy_set_header Host $host;
      proxy_cache_bypass $http_upgrade;
    }
}

【讨论】:

  • 原来这与 Cloudflare 有关。不过,感谢您的意见!
猜你喜欢
  • 2014-06-01
  • 1970-01-01
  • 2015-02-26
  • 2011-06-04
  • 1970-01-01
  • 2015-02-15
  • 1970-01-01
  • 2015-04-19
  • 1970-01-01
相关资源
最近更新 更多