我们的应用程序在Laravel Forge上的一台服务器上运行，但我们最近不得不添加另一台服务器，所以我们这样做并将它们放在一个新的AWS ELB上，出于可扩展性的目的，我们更喜欢Forge的ELB解决方案。一切正常，但是ELB的健康检查失败，将两个目标标记为不健康。尽管这不会导致任何问题，但我想解决这个问题，这样我就可以使用像Cloudwatch这样的监视器。我登录到一个服务器查看日志，这是我发现的：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文件的开头添加这个，但没有运气：

location /health-check {
    access_log off;
    return 200;
}

型
还尝试在ELB健康检查中添加444作为可接受的响应代码，但它不喜欢，我也不喜欢。