nginx 添加新站点导致 ERR_TOO_MANY_REDIRECTS

nginx adding new site causes ERR_TOO_MANY_REDIRECTS

我正在尝试向我的服务器添加另一个 Django 应用程序。我已经有了 xmlanalyzer.maciejg.pl up&运行ning,现在我正在尝试向现有的 nginx 和 gunicorn 设置添加另一个应用程序,以便在 fencing.maciejg.pl.

上可用

我使用了现有的 XMLAnalyzer gunicorn 设置(工作正常):

#!/bin/bash

NAME="xmlanalyzer"                                   # Name of the application
DJANGODIR=/home/django/xmlanalyzer                   # Django project directory
SOCKFILE=/home/django/xmlanalyzer/run/gunicorn.sock  # we will communicte using this unix socket
USER=my-user-name                                             # the user to run as
GROUP=my-user-name                                            # the group to run as
NUM_WORKERS=3                                        # how many worker processes should Gunicorn spawn
DJANGO_SETTINGS_MODULE=xmlanalyzer.settings          # which settings file should Django use
DJANGO_WSGI_MODULE=xmlanalyzer.wsgi                  # WSGI module name

echo "Starting $NAME as `whoami`"

# Activate the virtual environment
cd $DJANGODIR
source ../venv/bin/activate
export DJANGO_SETTINGS_MODULE=$DJANGO_SETTINGS_MODULE
export PYTHONPATH=$DJANGODIR:$PYTHONPATH

# Create the run directory if it doesn't exist
RUNDIR=$(dirname $SOCKFILE)
test -d $RUNDIR || mkdir -p $RUNDIR

# Start your Django Unicorn
# Programs meant to be run under supervisor should not daemonize themselves (do not use --daemon)
#exec gunicorn -b 127.0.0.1:8001 xmlanalyzer.wsgi:application --pid /tmp/gunicorn.pid ;
exec gunicorn -b 127.0.0.1:8001 ${DJANGO_WSGI_MODULE}:application \
  --name $NAME \
  --workers $NUM_WORKERS \
  --user=$USER --group=$GROUP \
##   --bind=unix:$SOCKFILE \
  --bind=127.0.0.1:8001 \
  --log-level=debug \
  --log-file=-

这是 Fencing 应用程序的 gunicorn 设置(不工作):

#!/bin/bash

NAME="fencing"                                  # Name of the application
DJANGODIR=/home/django/fencing                  # Django project directory
SOCKFILE=/home/django/fencing/run/gunicorn.sock # we will communicte using this unix socket
USER=my-user-name                                        # the user to run as
GROUP=my-user-name                                       # the group to run as
NUM_WORKERS=3                                   # how many worker processes should Gunicorn spawn
DJANGO_SETTINGS_MODULE=mysite.settings          # which settings file should Django use
DJANGO_WSGI_MODULE=mysite.wsgi                  # WSGI module name

echo "Starting $NAME as `whoami`"

# Activate the virtual environment
cd $DJANGODIR
source ../venv/bin/activate
export DJANGO_SETTINGS_MODULE=$DJANGO_SETTINGS_MODULE
export PYTHONPATH=$DJANGODIR:$PYTHONPATH

# Create the run directory if it doesn't exist
RUNDIR=$(dirname $SOCKFILE)
test -d $RUNDIR || mkdir -p $RUNDIR

# Start your Django Unicorn
# Programs meant to be run under supervisor should not daemonize themselves (do not use --daemon)

exec gunicorn -b 127.0.0.1:8002 ${DJANGO_WSGI_MODULE}:application \
  --name $NAME \
  --workers $NUM_WORKERS \
  --user=$USER --group=$GROUP \
##   --bind=unix:$SOCKFILE \
  --bind=127.0.0.1:8002 \
  --log-level=debug \
  --log-file=-

两者似乎都已启动:

ps -ef | grep gunicorn
my-user-name        780 20697  0 10:20 ?        00:00:01 /home/django/venv/bin/python3 /home/django/venv/bin/gunicorn -b 127.0.0.1:8002 mysite.wsgi:application --name fencing --workers 3 --user=my-user-name --group=my-user-name
my-user-name        787   780  0 10:20 ?        00:00:00 /home/django/venv/bin/python3 /home/django/venv/bin/gunicorn -b 127.0.0.1:8002 mysite.wsgi:application --name fencing --workers 3 --user=my-user-name --group=my-user-name
my-user-name        788   780  0 10:20 ?        00:00:00 /home/django/venv/bin/python3 /home/django/venv/bin/gunicorn -b 127.0.0.1:8002 mysite.wsgi:application --name fencing --workers 3 --user=my-user-name --group=my-user-name
my-user-name        789   780  0 10:20 ?        00:00:00 /home/django/venv/bin/python3 /home/django/venv/bin/gunicorn -b 127.0.0.1:8002 mysite.wsgi:application --name fencing --workers 3 --user=my-user-name --group=my-user-name
my-user-name       1712  1656  0 12:40 pts/1    00:00:00 grep --color=auto gunicorn
root      1730     1  0  2018 ?        01:04:09 /home/django/venv/bin/python3 /home/django/venv/bin/gunicorn -b 127.0.0.1:8001 xmlanalyzer.wsgi:application --name xmlanalyzer --workers 3 --user=my-user-name --group=my-user-name
my-user-name      17483  1730  0 Mar25 ?        00:01:12 /home/django/venv/bin/python3 /home/django/venv/bin/gunicorn -b 127.0.0.1:8001 xmlanalyzer.wsgi:application --name xmlanalyzer --workers 3 --user=my-user-name --group=my-user-name
my-user-name      17554  1730  0 Mar25 ?        00:01:05 /home/django/venv/bin/python3 /home/django/venv/bin/gunicorn -b 127.0.0.1:8001 xmlanalyzer.wsgi:application --name xmlanalyzer --workers 3 --user=my-user-name --group=my-user-name
my-user-name      17953  1730  0 Mar25 ?        00:00:41 /home/django/venv/bin/python3 /home/django/venv/bin/gunicorn -b 127.0.0.1:8001 xmlanalyzer.wsgi:application --name xmlanalyzer --workers 3 --user=my-user-name --group=my-user-name

我使用以下方法创建了 nginx 设置:

/etc/nginx/sites-available# more xmlanalyzer
server {
    server_name xmlanalyzer.maciejg.pl;

    access_log off;

    location /static/ {
        alias /home/django/xmlanalyzer/XMLAnalyzer/static/;
    }

    location / {
        proxy_set_header Host $host;
        proxy_pass http://127.0.0.1:8001;
        proxy_set_header X-Forwarded-Host $server_name;
        proxy_set_header X-Real-IP $remote_addr;
        add_header P3P 'CP="ALL DSP COR PSAa PSDa OUR NOR ONL UNI COM NAV"';
    }
 # managed by Certbot

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/xmlanalyzer.maciejg.pl/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/xmlanalyzer.maciejg.pl/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 {
    if ($host = xmlanalyzer.maciejg.pl) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


    server_name xmlanalyzer.maciejg.pl;
    listen 80;
    return 404; # managed by Certbot
    client_max_body_size 64M;
}

我已将文件夹和端口从 8001 更改为 8002。结果我得到:

/etc/nginx/sites-available# more fencing
server {
    server_name fencing.maciejg.pl;

    access_log off;

    location = /favicon.ico { access_log off; log_not_found off; }
    location /static/ {
        alias /home/django/fencing/fencingtournament/static/;
    }

    access_log /home/django/fencing/logs/nginx-access.log;
    error_log /home/django/fencing/logs/nginx-error.log;

    location / {
        proxy_set_header Host $host;
        proxy_pass http://127.0.0.1:8002;
        proxy_set_header X-Forwarded-Host $server_name;
        proxy_set_header X-Real-IP $remote_addr;
        add_header P3P 'CP="ALL DSP COR PSAa PSDa OUR NOR ONL UNI COM NAV"';
    }
 # managed by Certbot

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/fencing.maciejg.pl/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/fencing.maciejg.pl/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 {
    if ($host = fencing.maciejg.pl) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


    server_name fencing.maciejg.pl;
    listen [::]:80;
    return 404; # managed by Certbot
}

现在,https://xmlanalyzer.maciejg.pl works great, I get ERR_TOO_MANY_REDIRECTS while trying to access https://fencing.maciejg.pl/

curl证明域设置正确,nginx可用。由于某种原因,它没有重定向到我的应用程序:

curl fencing.maciejg.pl
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
    body {
        width: 35em;
        margin: 0 auto;
        font-family: Tahoma, Verdana, Arial, sans-serif;
    }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>

<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>

<p><em>Thank you for using nginx.</em></p>
</body>
</html>

两个站点都可用。

ll ../sites-enabled/
total 12
drwxr-xr-x 2 root root 4096 Mar 25 20:39 ./
drwxr-xr-x 6 root root 4096 Mar 25 22:59 ../
lrwxrwxrwx 1 root root   26 Mar 25 20:39 fencing -> ../sites-available/fencing
lrwxrwxrwx 1 root root   30 Feb 23  2018 xmlanalyzer -> ../sites-available/xmlanalyzer

我觉得 gunicorn 日志不错:

tail gunicorn-error.log
Starting fencing as my-user-name
[2019-03-26 10:20:01 +0000] [780] [INFO] Starting gunicorn 19.7.1
[2019-03-26 10:20:01 +0000] [780] [INFO] Listening at: http://127.0.0.1:8002 (780)
[2019-03-26 10:20:01 +0000] [780] [INFO] Using worker: sync
[2019-03-26 10:20:01 +0000] [787] [INFO] Booting worker with pid: 787
[2019-03-26 10:20:01 +0000] [788] [INFO] Booting worker with pid: 788
[2019-03-26 10:20:02 +0000] [789] [INFO] Booting worker with pid: 789

nginx-access.log 和 nginx-error.log 在我的 /home/django/fencing/logs foler 中是空的。

我错过了什么?我将不胜感激。

编辑 只是补充 - 如果手动启动应用程序可以访问:

Starting development server at http://159.65.24.62:8002/
[26/Mar/2019 14:24:37] You're accessing the development server over HTTPS, but it only supports HTTP.

这里的错误是预期的 - 这只是为了表明对 https://fencing.maciejg.pl:8002/ 的 Web 请求确实命中了正确的位置,因此域设置正常。

编辑 2 将 Fencing 应用程序的 nginx 设置更改为 access_log on;,结果如下:

more nginx-access.log

37.30.26.37 - - [26/Mar/2019:14:14:04 +0000] "GET / HTTP/1.1" 301 5 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko
) Chrome/73.0.3683.86 Safari/537.36"
37.30.26.37 - - [26/Mar/2019:14:14:04 +0000] "GET / HTTP/1.1" 301 5 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko
) Chrome/73.0.3683.86 Safari/537.36"

所以我可以看到请求到达了nginx并且被拒绝了。

编辑 3 使用 certbot 禁用重定向后,我现在在访问 http://fencing.maciejg.pl/ 时获得 nginx 登录页面 - 所以,它再次通过,只是没有重定向到我的应用程序运行 通过 gunicorn。所以我仍然相信这是我的 nginx 设置中的一个错误 - 但是,我仍然没有看到它...

好的,我终于解决了这个问题!存在多个问题。

首先,我在 nginx 设置中发生了冲突。 虽然部分是,即使我解决了这个问题,我仍然遇到 HTTP 错误。这是因为 gunicorn 设置无效。 虽然部分是,即使我解决了这个问题,我仍然遇到 HTTP 错误。这是因为 Django 设置无效。

所以我一遍又一遍地把每一块都搞砸了,我的建议和解决方法是:一步一步地分析。

首先:我 运行 通过在 Debug = True 和禁用 SSL 的情况下启动 python manage.py runserver 127.0.0.1:8000 我的 Django 应用程序处于开发模式。通过这种方式 curl 我能够让它响应并确认它有效。

接下来,我通过 gunicorn 脚本终止了该应用程序并 运行 它。我发现它抛出错误是因为保存 SECRET_KEY 的环境变量不可用。老实说 - 我没有解决这个问题,我已经转而将密钥保存在一个单独的文件中。所以,一个问题解决了,我的 gunicorn 运行 没问题。

嵌套步骤:终止 gunicorn 进程并使用 supervisiord 调用它。原来有一个特权问题,因为 supervisiord 运行s 在不同的帐户上。

一旦我解决了这个问题,我就从头开始重新创建我的 nginx 设置,直到它开始转发请求。无 SSL。

接下来,我重新运行 certbot 以恢复 SSL。在这里我还发现您需要清除浏览器缓存,因为它没有显示页面,即使下面的设置很好。这也花了一段时间 - 我在尝试使用不同的笔记本电脑访问我的网站时无意中发现了这个,发现它工作正常。

最后,我把我的其他nginx服务器配置放在sites-enabled后面,一个接一个。

我希望我永远不需要这个解决方案,并且它只会对其他人有用:)