Failed Request Trace 502 Bad Gateway

Partial screenshot of a Failed Request Trace showing two warnings related to a 502 Bad Gateway error - refer to description
Two warnings indicating a URL was unresolved leading to a 502 error

After more than two seconds the ApplicationRequestRouting module raised EXECUTE_REQUEST_HANDLER, HttpStatus 502, HttpReason Bad Gateway, HttpSubStatus 3, ErrorCode 2147954407 … ErrorDescription “The server name or address could not be resolved”. Possibly linked to an earlier rewrite which seemed to substitute the internal https://blog.xarta.co.uk/ with just forward slash.

Print Friendly