Forum Discussion
Mark_Stradling_
Nov 11, 2015Cirrus
I ran into this error. This may not apply to everyone's scenario, but thought I would post our solution. It turned out to be something really simple. We were trying to do an SSL::disable serverside, which was working just fine. Problem is, "port translation" was not enabled on the VIP, so it was disabling SSL, but it was not sending the traffic to port 80 on the server side (even though the pool was defined as such). Enabling port translation on the VIP allowed it to correctly send the traffic to 80 after the SSL::disable serverside command and eliminate the error.