A server that belongs to a server pool became unavailable (down) according to the configured server health check, if any.

• Verify that you have selected a server health check in the server pool definition.

• Verify that the server health check is using a method to contact the server that the server can respond to. If you are using Ping, for example, the server must be responsive to ICMP ECHO_REQUEST signals.

• Confirm that the physical cables connecting FortiWeb and all the back-end servers are securely connected, including any intermediary devices such as switches or routers. You can also use commands like execute ping and execute traceroute to check connectivity.

• Verify that the server health check is selected in the server pool settings.

• Ensure the server health check method is one that the server can respond to. If using Ping, for example, the server must respond to ICMP ECHO_REQUEST signals.

• For methods like TCP, TCP Half Open, TCP SSL, or HTTP, ensure the IP and port of the servers are correct.

• If the server health check refers to a custom health check policy using multiple methods, ensure the "Relationship And/Or" setting is correct.

• For the HTTP method, ensure the configured HTTP URL Path, Method, Match Type, and Matched Content are correct.

Physical Server <pserver_index> [<pserver_name>:<pserver-port_int>] in server pool <server_pool_name> status change from up to down.

date=2024-07-26 time=15:03:21 log_id=19999495 msg_id=000000001228 device_id=FVVM040000010871 vd="root" timezone="(GMT-5:00)Eastern Time(US & Canada)" type=event subtype="system" pri=alert trigger_policy="N/A" user=daemon ui=daemon action=check-resource status=failure msg="Physical Server 1 [apache1:80] in server pool My-Server-Pool-1 status change from up to down"