【宋词】《渡江云》 张炎：山空天入海，倚楼望极，风急暮潮初。一帘鸠外雨，几处闲田，隔水动春锄。新烟禁柳，想如今、绿到西湖。犹记得、当年深隐，

永夜

没有不值得去解决的问题，也没有不值得去学习的技术！

Analyze and Resolve 404 Not Found Responses in a Docker Nginx PHP Environment

In a Docker container, the Nginx PHP environment responds with a 404 Not Found when opening a route mapped to a PHP file

作者：

永夜

在

, , , , , ,
Views: 34

1. In a Docker container, the Nginx PHP environment responds with a 404 Not Found when opening a route mapped to a PHP file, as shown in Figure 1.

In a Docker container, the Nginx PHP environment responds with a 404 Not Found when opening a route mapped to a PHP file
Figure 1
HTML
<html>
 
<head>
    <title>404 Not Found</title>
</head>
 
<body>
    <center>
        <h1>404 Not Found</h1>
    </center>
    <hr>
    <center>nginx</center>
</body>
 
</html>

2. Opening a route mapped to an HTML file returns a 200 response, as shown in Figure 2.

Opening a route mapped to an HTML file returns a 200 response
Figure 2

3. The Nginx configuration file contains the following:

Nginx
server {
    listen 80; ## listen for ipv4
    server_name api.pcs.wjdev.chinamcloud.cn;
    charset utf-8;

    root /mcloud/www/pcs-api/api/web;
    index index.php;
    location / {
        # 如果找不到真实存在的文件，把请求分发至 index.php
        try_files $uri $uri/ /index.php$is_args$args;
    }

    location / {
        rewrite /interace /abc;
    }

    location /abc {
        return 200 '{"msg":"success"}';
    }


    # uncomment to avoid processing of calls to non-existing static files by Yii
    #location ~ \.(js|css|png|jpg|gif|swf|ico|pdf|mov|fla|zip|rar)$ {
    #    try_files $uri =404;
    #}
    #error_page 404 /404.html;

    # deny accessing php files for the /assets directory
    location ~ ^/assets/.*\.php$ {
        deny all;
    }

    # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
    #
    location ~ \.php$ {
        fastcgi_pass 127.0.0.1:9000;
        fastcgi_index index.php;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include fastcgi_params;
    }

    # deny access to .htaccess files, if Apache's document root
    # concurs with nginx's one
    #
    location ~* /\. {
        deny all;
    }

    location /nginx_status {
        stub_status on;
        access_log off;
        allow 127.0.0.1;
        deny all;
    }

    location ~ ^/(status|ping)$ {
        include fastcgi_params;
        fastcgi_pass 127.0.0.1:9000;
        fastcgi_param SCRIPT_FILENAME $fastcgi_script_name;
        access_log off;
        allow 127.0.0.1;
        allow 10.42.0.0/16;
        allow 10.244.0.0/8;
        allow 192.168.0.0/8;
        allow 172.17.0.0/8;
        deny all;
    }
}

4. I found duplicate entries (location / { }) in the configuration file, which caused the first configuration block to be overwritten. I decided to delete the second configuration block.

Nginx

    location / {
        rewrite /interace /abc;
    }

    location /abc {
        return 200 '{"msg":"success"}';
    }
Nginx
server {
    listen 80; ## listen for ipv4
    server_name api.pcs.wjdev.chinamcloud.cn;
    charset utf-8;

    root /mcloud/www/pcs-api/api/web;
    index index.php;
    location / {
        # 如果找不到真实存在的文件，把请求分发至 index.php
        try_files $uri $uri/ /index.php$is_args$args;
    }

    # uncomment to avoid processing of calls to non-existing static files by Yii
    #location ~ \.(js|css|png|jpg|gif|swf|ico|pdf|mov|fla|zip|rar)$ {
    #    try_files $uri =404;
    #}
    #error_page 404 /404.html;

    # deny accessing php files for the /assets directory
    location ~ ^/assets/.*\.php$ {
        deny all;
    }

    # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
    #
    location ~ \.php$ {
        fastcgi_pass 127.0.0.1:9000;
        fastcgi_index index.php;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include fastcgi_params;
    }

    # deny access to .htaccess files, if Apache's document root
    # concurs with nginx's one
    #
    location ~* /\. {
        deny all;
    }

    location /nginx_status {
        stub_status on;
        access_log off;
        allow 127.0.0.1;
        deny all;
    }

    location ~ ^/(status|ping)$ {
        include fastcgi_params;
        fastcgi_pass 127.0.0.1:9000;
        fastcgi_param SCRIPT_FILENAME $fastcgi_script_name;
        access_log off;
        allow 127.0.0.1;
        allow 10.42.0.0/16;
        allow 10.244.0.0/8;
        allow 192.168.0.0/8;
        allow 172.17.0.0/8;
        deny all;
    }

5. Opening a route mapped to a PHP file now returns a 200 response, as expected, as shown in Figure 3.

Opening a route mapped to a PHP file returns a 200 response, as expected
Figure 3

关于作者 · 持续学习与技术实践

我是一名拥有 15 年以上开发经验的技术从业者，自 2013 年起持续运营个人技术博客，记录工作与个人项目中遇到的真实问题，以及解决问题过程中的探索、实践和思考。

除了技术写作，我也在持续开发和维护自己的独立项目，探索新技术和新工具在实际场景中的应用。我始终相信，没有不值得去解决的问题，也没有不值得去学习的技术。

如果这篇文章对你有所帮助，欢迎浏览博客中的其他文章，也欢迎交流技术经验与想法。

关于我  ·  GitHub  ·  邮件联系

更多文章