Laravel Forge服务器不接受AWS ELB健康检查请求问题排查

我们的应用原本部署在Laravel Forge的单台服务器上，近期为了扩展新增一台服务器，并将两台服务器接入新的AWS ELB（未使用Forge自带的ELB方案）。应用运行正常，但ELB健康检查始终失败，两台目标服务器均被标记为不健康。查看Nginx访问日志，发现健康检查请求被返回HTTP 444状态码：

/var/log/nginx# tail -f access.log
[20/Jun/2023:23:24:23 +0000] "GET /health-check HTTP/1.1" 444 0 "-" "ELB-HealthChecker/2.0"

当前Nginx配置文件如下：

# FORGE CONFIG (DO NOT REMOVE!)
include forge-conf/mywebsite.com/before/*;

server {
    listen 80;
    listen [::]:80;
    server_name mywebsite.com;
    server_tokens off;
    root /home/forge/mywebsite.com/current/public;

    # FORGE SSL (DO NOT REMOVE!)
    # ssl_certificate;
    # ssl_certificate_key;

    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
    ssl_prefer_server_ciphers off;
    ssl_dhparam /etc/nginx/dhparams.pem;

    add_header X-Frame-Options "SAMEORIGIN";
    add_header X-XSS-Protection "1; mode=block";
    add_header X-Content-Type-Options "nosniff";

    index index.html index.htm index.php;

    charset utf-8;

    # FORGE CONFIG (DO NOT REMOVE!)
    include forge-conf/mywebsite.com/server/*;

    location / {
        try_files $uri $uri/ /index.php?$query_string;
    }

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

    access_log off;
    error_log  /var/log/nginx/mywebsite.com-error.log error;

    error_page 404 /index.php;

    location ~ \.php$ {
        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        fastcgi_pass unix:/var/run/php/php8.1-fpm.sock;
        fastcgi_index index.php;
        include fastcgi_params;
    }

    location ~ /\.(?!well-known).* {
        deny all;
    }
}

# FORGE CONFIG (DO NOT REMOVE!)
include forge-conf/mywebsite.com/after/*;

已尝试以下操作但均无效：

• 在Nginx配置文件开头添加健康检查路由配置
• 将444设置为ELB健康检查可接受的响应码

解决方案 #

1. 调整server_name匹配所有请求 #

ELB健康检查的请求Host头通常是服务器私有IP或主机名，而非配置的mywebsite.com。Nginx会拒绝不匹配server_name的请求，导致返回444。修改server_name，添加通配符_匹配所有主机：

server_name mywebsite.com _;

或者直接指定服务器的私有IP：

server_name mywebsite.com 10.0.0.10; # 替换为你的服务器实际私有IP

2. 正确放置健康检查的location规则 #

Nginx按配置顺序匹配location规则，需将/health-check的匹配规则放在location /之前，确保优先被命中：

# 放在location / 之前
location = /health-check {
    access_log off;
    return 200 'OK';
    add_header Content-Type text/plain;
}

location / {
    try_files $uri $uri/ /index.php?$query_string;
}

3. 验证配置并重启Nginx #

修改完成后，先校验Nginx配置是否合法：

sudo nginx -t

校验通过后，重启Nginx生效：

sudo systemctl restart nginx

4. 确认ELB健康检查参数 #

确保ELB健康检查的路径为/health-check，端口为80（或你配置的HTTP端口），且接受200状态码作为健康响应。

内容的提问来源于stack exchange，提问作者Brayan