Forum Discussion
HTTPS monitor suddenly stopped working. http works fine on same nodes. what could cause this, newbie here
I have a customer environment where the HTTP monitors are just fine, but the HTTPs monitors have suddenly stopped. it is using the default https monitor and the monitor is operating correctly on other https nodes. that seems to me that that would be on the customer side since the only thing specific about it is the individual node itself on port 443. if it was a monitor issue, especially a default one, it would seem the issue would be spread further. Does anyone have any insight to simple issues this could be or is everyone of the same mind that this looks like a customer side issue?
- Vijay_ECirrus
HTTPS monitor failed working on some nodes but it is working well on other nodes ? If so, is it possible to see what was changed at the server level ?
- The_YCirrus
You can also enable Monitor Logging on that pool member and check the logs (/var/log/monitors/). The log will give you a better idea of what is going on with that server failling the https monitor.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com