HTTPS Monitor on non-standard port fails

When I upgraded from 9.x to 10.x we ran into an unexpected issue with our custom monitors. We had to explicitly add a linefeed (\r\n) to the Request commands. You might not have the same issue because you would also see it on custom HTTP checks, but reviewing the Release Notes might help explain behavior.

 

 

In terms of troubleshooting the monitor, you could always add the original monitor in addition to the existing tcp monitor. Just make sure you change the pool settings to only require 1 monitor. At this point, you can make adjustments and capture traffic without affecting the availability of the pool members. This is what I normally do when I want to gracefully phase in a new monitor for a pool. This way, I avoid taking down a pool if the new monitor has issues.