VHOST：

Server ID : SuperUser Shell : sites-available/ > # cat example.com-ssl 
server {
    listen 80;
    server_name www.example.com example.com;
    return      301 https://www.example.com$request_uri;
}

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

    # This is for troubleshooting
    access_log /var/log/nginx/www.example.com/access.log;
    error_log /var/log/nginx/www.example.com/error.log debug;
}

server {
    listen 443 default_server ssl;
    server_name www.example.com;

    ssl                         on;
    ssl_certificate             /etc/ssl/certs/www.example.com/2017/www.example.com.crt;
    ssl_certificate_key         /etc/ssl/certs/www.example.com/2017/www.example.com.key;
    ssl_trusted_certificate     /etc/ssl/certs/www.example.com/2017/www.example.com.ca-bundle;
    ssl_protocols               TLSv1.1 TLSv1.2;
    ssl_ciphers                 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';
    ssl_prefer_server_ciphers   on;
    ssl_session_cache           shared:SSL:10m;
    ssl_dhparam                 /etc/ssl/certs/www.example.com/2017/dhparam.pem;
    add_header                  Strict-Transport-Security "max-age=63072000; includeSubexamples; ";

    location / {
        proxy_set_header   X-Real-IP $remote_addr;
        proxy_set_header   Host      $http_host;
        proxy_pass         http://127.0.0.1:2368;
    }

    access_log /var/log/nginx/www.example.com/access.log;
    error_log /var/log/nginx/www.example.com/error.log;
}
Server ID : SuperUser Shell : sites-available/ > #

其他信息：

我还应该指出，这是一个鬼博客服务器，我已更新config.js以反映https而不是http：

Server ID : SuperUser Shell : ghost/ > # cat config.js 
// # Ghost Configuration
// Setup your Ghost install for various [environments](http://support.ghost.org/config/#about-environments).

// Ghost runs in `development` mode by default. Full documentation can be found at http://support.ghost.org/config/

var path = require('path'),
    config;

config = {

    // ### Production
    production: {

        url: 'https://www.example.com',
        mail: {},

        database: {
            client: 'sqlite3',
            connection: {
                filename: path.join(__dirname, '/content/data/ghost.db')
            },
            debug: false
        },

        server: {
            host: '0.0.0.0',
            port: '2368'
        }
    },

    // ### Development **(default)**
    development: {

        url: 'https://www.example.com',

        database: {
            client: 'sqlite3',
            connection: {
                filename: path.join(__dirname, '/content/data/ghost-dev.db')
            },
            debug: false
        },
    },

...

Server ID : SuperUser Shell : ghost/ > #

我还使用pm2重启了这个java进程（我使用什么来保持ghost运行）。我甚至停止了这个过程并重新开始

cURL输出：

... Same thing as below for 49 times
* Ignoring the response-body
* Connection #0 to host www.example.com left intact
* Issue another request to this URL: 'https://www.example.com/'
* Found bundle for host www.example.com: 0x263b920
* Re-using existing connection! (#0) with host www.example.com
* Connected to www.example.com (123.45.67.89) port 443 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.35.0
> Host: www.example.com
> Accept: */*
> 
< HTTP/1.1 301 Moved Permanently
* Server nginx/1.4.6 (Ubuntu) is not blacklisted
< Server: nginx/1.4.6 (Ubuntu)
< Date: Sat, 26 Nov 2016 08:56:23 GMT
< Content-Type: text/plain; charset=utf-8
< Content-Length: 63
< Connection: keep-alive
< X-Powered-By: Express
< Location: https://www.example.com/
< Vary: Accept, Accept-Encoding
< Strict-Transport-Security: max-age=63072000; includeSubdomains; 
< 
* Ignoring the response-body
* Connection #0 to host www.bestredflags.com left intact
* Maximum (50) redirects followed

问题：

有谁看到我犯错误的地方？
我从运行nginx version: nginx/1.10.2的RHEL 7.3服务器（没有问题）复制了我的nginx配置到运行nginx version: nginx/1.4.6 (Ubuntu)的Ubuntu 14.04这可能是我的问题的一部分吗？
- 在推送vHost配置更改之前，我没有收到来自nginx -t的错误。
- 这让我觉得我的vHost没有问题，但vHost配置错误似乎也是合乎逻辑的选择。
我之前想知道的是，在nginx中，这似乎比将null重定向到www到https://www处于apache状态要长一些。 我是否正确使用nginx？
- 我正在关注此处提供的文档： https://www.digitalocean.com/community/tutorials/how-to-create-temporary-and-permanent-redirects-with-apache-and-nginx

我希望这不是太多的信息。我绝对不想提供太少的信息。

感谢您提供任何帮助/指示。

Answer 1

这非常令人尴尬但我在比较配置时发现我的生产服务器鬼不需要在https中指定config.js。这导致了我的第一个无限重定向循环。

PROD : SuperUser Shell : ghost/ > # grep sitename config.js 
        url: 'http://www.sitename.com',
        url: 'http://www.sitename.com',
PROD : SuperUser Shell : ghost/ > #

其次，我在重新启用DNS保护时收到了来自CloudFlare的另一个重定向循环

要更正此问题，请转到概述标签＆gt;设置摘要＆gt;单击SSL并从＆＃34; Flexible＆＃34;更改SSL到＆＃34;完整（严格）＆＃34;。

无限重定向 - nginx

VHOST：

其他信息：

cURL输出：

问题：

1 个答案: