example.com 之类的基本 URL 在 NGinx 中不起作用

Question

我有 12 个站点，我计划运行在一台装有 NGinx 和 php5-fpm 的服务器上。我为每个 conf 文件使用一个服务器块来设置它们，所有这些都包含在主 nginx.conf 文件中。它是 Wordpress、PhpMyAdmin 和 PHP 站点的混合体。 wordpress 和 PhpMyAdmin 站点工作正常，但 PHP 站点不是。意思是，当我拉起 example.com 时，Chrome 说连接被拒绝，并且在 NGinx 日志上没有传入连接的痕迹。 test.example.com 同时拉起默认站点（因为当时我没有配置test.example.com）。

我从工作站点复制了 nginx 配置来设置不工作的站点，但没有成功。工作站点和非工作站点之间 nginx 配置的唯一区别是 server_name 指令。

检查和检查了 2 个多小时后，我发现带有 server_name 作为 pqr.example.com 的站点有效，但带有 example.com 的站点无效.所有工作站点都配置为使用子域 URL，这可能就是它们工作的原因。

我的问题是-
1. 我在配置中缺少什么才能使 abc.com 正常工作？
2. 我有两个网站，example.com 和 example.net，我想在同一台服务器上运行。这会成为 NGinx 的问题吗？
3. Nginx 区分example.com、test.example.com 和example.net 有问题吗？
4. 我还注意到，如果 www.example.net 有效，www.example.com 则无效，反之亦然，这意味着我必须为每个名称为 abc 的站点分配不同的子域，例如 www. example.net 和测试。example.com。这是 Nginx 的 standard/expected 行为，还是我遗漏了什么？
5. 我所有的基本 URL 都从 http://example.com to http://www.example.com 自动重定向；我如何找出发生重定向的位置？

以下是我遇到问题的 Nginx 配置文件，运行包含重要部分；如果需要更多信息，请告诉我。

主 nginx.conf 文件 -

user www-data www-data;
pid /var/run/nginx.pid;
worker_processes 4;
worker_rlimit_nofile 100000;

events {
    worker_connections  4096;
    include /etc/nginx.custom.events.d/*.conf;
}

http {
    default_type application/octet-stream;

    access_log off;
    error_log  /var/log/nginx/error.log crit;
    .......
    server_tokens off;

    include proxy.conf;
    include fcgi.conf;

    include conf.d/*.conf;
    include /etc/nginx.custom.d/*.conf;
}

include /etc/nginx.custom.global.d/*.conf;

这是一个有效博客的完整工作 .conf 文件。所有其他站点都具有此完整配置，因为它们只是基本 PHP 站点。

server {
    listen *:80;    

    server_name blog.example.com;

    access_log /var/log/nginx/blog-example.access.log;
    error_log /var/log/nginx/blog-example.error.log;

    root /var/www/example/blog;
    index index.html index.htm index.php;

    # This order might seem weird - this is attempted to match last if rules below fail.
    location / {
        try_files $uri $uri/ /index.php?$args;
    }

    # Add trailing slash to */wp-admin requests.
    rewrite /wp-admin$ $scheme://$host$uri/ permanent;

    # Directives to send expires headers and turn off 404 error logging.
    location ~* ^.+\.(ogg|ogv|svg|svgz|eot|otf|woff|mp4|ttf|rss|atom|jpg|jpeg|gif|png|ico|zip|tgz|gz|rar|bz2|doc|xls|exe|ppt|tar|mid|midi|wav|bmp|rtf)$ {
           access_log off; log_not_found off; expires max;
    }

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

    location = /robots.txt {
        allow all;
        log_not_found off;
        access_log off;
    }

    # Deny all attempts to access hidden files such as .htaccess, .htpasswd, .DS_Store (Mac).
    # Keep logging the requests to parse later (or to pass to firewall utilities such as fail2ban)
    location ~ /\. {
        deny all;
    }

    # Deny access to any files with a .php extension in the uploads directory
    # Works in sub-directory installs and also in multisite network
    # Keep logging the requests to parse later (or to pass to firewall utilities such as fail2ban)
    location ~* /(?:uploads|files)/.*\.php$ {
        deny all;
    }

    location ~ [^/]\.php(/|$) {

        # Zero-day exploit defense.
        # http://forum.nginx.org/read.php?2,88845,page=3
        # Won't work properly (404 error) if the file is not stored on this server, which is entirely possible with php-fpm/php-fcgi.
        # Comment the 'try_files' line out if you set up php-fpm/php-fcgi on another machine.  And then cross your fingers that you won't get hacked.
        try_files $uri =404;
        fastcgi_split_path_info ^(.+\.php)(/.+)$;

        fastcgi_index index.php;
        include fcgi.conf;
        fastcgi_pass unix:/var/run/php-fcgi-blog-example-php-fcgi-0.sock;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

    }

}

这是 example.com

的 t运行cated .conf 文件

server {
    listen *:80;    

    server_name example.com www.example.com test.example.com;

    access_log /var/log/nginx/examplecom.access.log;
    error_log /var/log/nginx/examplecom.error.log;

    root /var/www/example/com;
    index index.html index.htm index.php;

    # This order might seem weird - this is attempted to match last if rules below fail.
    location / {
        try_files $uri $uri/ /index.php?$args;
    }
    ........

    location ~ [^/]\.php(/|$) {
        ......
        fastcgi_index index.php;
        include fcgi.conf;
        fastcgi_pass unix:/var/run/php-fcgi-examplecom-php-fcgi-0.sock;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
    }

}

这是 example.net

的 t运行分类文件

server {
    listen *:80;

    server_name example.net www.example.net test.example.net;

    access_log /var/log/nginx/examplenet.access.log;
    error_log /var/log/nginx/examplenet.error.log;

    root /var/www/example/net;
    index index.html index.htm index.php;

    # This order might seem weird - this is attempted to match last if rules below fail.
    location / {
        try_files $uri $uri/ /index.php?$args;
    }
    ........

    location ~ [^/]\.php(/|$) {
        ......
        fastcgi_index index.php;
        include fcgi.conf;
        fastcgi_pass unix:/var/run/php-fcgi-examplenet-php-fcgi-0.sock;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
    }
}

Answer 1

Meaning, when I pull up example.com, Chrome says connection refused, and there's no trace of an incoming connection on NGinx logs. test.example.com pulls up the default site(because I didn't configure test.example.com then) at the same time.

好的，您的服务器正在侦听。可能是您没有正确配置 DNS 记录，或者存在 DNS 缓存。设置你的主机文件来测试这个理论。

example.com 之类的基本 URL 在 NGinx 中不起作用

Base URLs like example.com not working in NGinx

php

nginx