Why are target group detection machines unhealthy?

Question

Health status：Unhealthy	
Health status details：Health checks failed
The associated load balancer can access the site using the DNS name. Why are target group detection machines unhealthy?

The access.log log shows that the health request is successful, but why does Target Groups show as unhealthy?

172.3.52.49 - - [09/Nov/2023:07:57:27 +0000] "GET / HTTP/1.1" 200 38278 "-" "ELB-HealthChecker/2.0"
172.3.2.25 - - [09/Nov/2023:07:57:27 +0000] "GET / HTTP/1.1" 200 38274 "-" "ELB-HealthChecker/2.0"
172.3.43.26 - - [09/Nov/2023:07:57:27 +0000] "GET / HTTP/1.1" 200 38277 "-" "ELB-HealthChecker/2.0"
172.3.65.157 - - [09/Nov/2023:07:57:27 +0000] "GET / HTTP/1.1" 200 38275 "-" "ELB-HealthChecker/2.0"
172.3.23.186 - - [09/Nov/2023:07:57:27 +0000] "GET / HTTP/1.1" 200 38271 "-" "ELB-HealthChecker/2.0"
172.3.95.67 - - [09/Nov/2023:07:57:27 +0000] "GET / HTTP/1.1" 200 38277 "-" "ELB-HealthChecker/2.0"
::1 - - [09/Nov/2023:07:58:28 +0000] "OPTIONS * HTTP/1.0" 200 126 "-" "Apache/2.4.52 (Ubuntu) OpenSSL/3.0.8 (internal dummy connection)"

Accepted Answer

The problem is found. The site is not connected to the database and cannot access the website. Although I can access the login page, I cannot log in to the web page.

Answer

What do you have defined as your success codes on your target groups? Is 200 listed?

Something that’s not related but unless you own 172.3 network address space, I’d recommend readdressing. That’s not a private RFC1918. You could have issues later.

Why are target group detection machines unhealthy?

相关内容