Nginx：导致301重定向的原因是什么？

Question

我仍然不知道为什么我的网页正在显示

myapp.com redirected you too many times.

Nginx仅用作我的django渠道应用程序的代理，该应用程序与daphne一起运行。

Nginx运行没有错误。

myapp systemd[1]: Starting A high performance web server and a reverse proxy server...

达芙妮的运行时间为127.0.0.1:8001

curl -I http://myapp.com/
curl -I https://myapp.com/

回报

HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Tue, 05 Mar 2019 11:53:39 GMT
Content-Type: text/html
Content-Length: 178
Connection: keep-alive
Location: https://myapp.com/

HTTP/1.1 301 Moved Permanently
Server: nginx/1.10.3 (Ubuntu)
Date: Tue, 05 Mar 2019 11:54:43 GMT
Content-Type: text/html
Content-Length: 194
Location: https://myapp.com/
Connection: keep-alive

有谁知道导致这301错误的原因是什么？

Nginx配置文件

server {
listen 80;
servername myapp.com www.myapp.com;
servertokens off;
return 301 https://$servername$requesturi;
}

server {
listen 443 ssl; # managed by Certbot
server_name myapp.com www.myapp.com;

ssl_certificate /etc/letsencrypt/live/myapp.com/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/myapp.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  

root /home/me/myapp/src/myapp;

location = /favicon.ico { access_log off; log_not_found off; }

location /static/ {
    root /home/me/myapp/src/myapp;
}

location /media/  {
    root /home/me/myapp/src/myapp;
}

location / {
    try_files $uri/ @python_django;
}

location @python_django {
    proxy_pass http://127.0.0.1:8001;
    proxy_pass_request_headers on;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Host $http_host;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_redirect off;
}
}

Answer 1

我仍然不确定如何完全解决这个问题，但是当我拿出来的时候

return 301 https://$server_name$request_uri;

并运行curl -I -L http://www.myapp.com/我得到

HTTP/1.1 200 OK
Server: nginx
Date: Tue, 05 Mar 2019 13:33:42 GMT
Content-Type: text/html
Content-Length: 612
Last-Modified: Tue, 31 Jan 2017 15:01:11 GMT
Connection: keep-alive
ETag: "5890a6b7-264"
Accept-Ranges: bytes

但我无法访问该页面，因为很明显LetsEncrypt正在将所有http重定向到https，所以我被引回到301错误页面！