When I made a GTM liveness test I received the response with liveness test failed: No valid reply code in server header response
Is there any way to test o validate what happen when I'm requesting the static object?
Alex Henry Hayes
Invalid reply code would imply that the HTTP response code the liveness test returned was not one that your GTM Liveness test considers good - i.e. HTTP 200.
Check your liveness test isn't sending a redirect and if you're using SiteShield that you've white listed the GTM test agents. There is a firewall notification list you can subscribe to to get these.
Thank you Neil. I fixed the Timed Out connection, but I have the following error:
12/16/2017 18:5665 seconds No valid reply code in server header response; or server closed the connection 126.96.36.199
12/16/2017 19:1665 seconds No valid reply code in server header response; or server closed the connection 188.8.131.52
12/16/2017 19:1865 seconds No valid reply code in server header response; or server closed the connection 184.108.40.206
12/16/2017 19:4165 seconds No valid reply code in server header response; or server closed the connection 220.127.116.11
Do you have any suggestion about how to fix it?
Is this new problem (either new GTM, new liveness test or new origin)?
Do you use SiteShield at your origin? If so, as Neil Jedrzejewski suggested, this sounds like a problem where the IP address of the GTM 'servermonitors' (the machines that actually make the liveness requests) have not been added to your firewall ACL, so they are getting kicked back by your firewall. If that is indeed the case, in Luna, if you click the CONFIGURE mega-menu option and select the Firewall Rules Notification option and then click the Manage Subscriptions tab, you can add a notification email to get a list of the current CIDR blocks used by GTM servermonitors, and add them to your firewall ACL.
Hi Rory, I updated the White List and we don't any timed out connection. The problem is with answer. I assumed that the code is coming empty, but I received StatusCode 200. That's why I'm asking if there is another way to test. in the Internal Network I'm running a couple of test. But I would like to understand the how could I reproduce the error.
Hmmm. At this point, I think it makes most sense to open a ticket with AkaTec - you will be able to send them all the details of the liveness test and the GTM properties which use it (which you probably shouldn't post here) and they can do some further checking.
Retrieving data ...