Description |
This article describes an example where a real server health checks HTTPS not working, but HTTP or TCP is working. The solution may vary depending on the setup but the concept of configuration and troubleshooting should be the same. |
Scope | FortiGate v7.0 and v7.2 tested with 7.2.4. |
Solution |
It is necessary to troubleshoot the connectivity for the server first:
Case Example:
Case Example configuration fix: It is possible to use the GUI to help configure but for HTTPs, it is necessary to apply additional settings in CLI.
GUI is designed to be simple and may not have all options available there, check CLI-reference for all options: config firewall ldb-monitor.
Additional troubleshooting commands for real server health checks:
diagnose debug enable diagnose firewall vip realserver healthcheck stats show Related article: |