What does "empty reply from server" mean?
The "empty reply from server" error indicates that a zero length response was received - no HTTP headers or content, simply a closed TCP connection with no HTTP payload transmitted.
One common cause of this problem is attempting to make a plain HTTP request against the HTTPS (TLS / SSL) web server port. The HTTPS client will not be able to establish an encrypted session with the plain HTTP port, hence fails with the "empty reply from server" error.
The HTTP standard requires that when a client makes an HTTP request, the server must respond with a valid HTTP response code. Failure to do so violates the standard, and will trigger an "empty reply from server" error from our HTTP client, as well as other compliant HTTP clients.
Troubleshooting steps
- Use the free HTTP test tool to verify if the problem persists. The test tool will provide diagnostic information showing the DNS resolution, TCP connection establishment, TLS / SSL encryption session creation and finally the HTTP request and response.
- Use the free remote PING tool to verify that the server or cloud instance hosting the web server is reachable.
Not what you were looking for? Try a search:
Also in this topic:
- Can I monitor the entire page, including images, CSS, Flash, etc?
- Can I perform an HTTP POST and monitor the results?
- Can I monitor a multiple page transaction (e.g. login)?
- Can I specify an username and password for a web page (HTTP Auth)?
- Can I verify that a specific phrase or text appears on my website?
- Unknown SSL protocol error in connection to [example.com]
- Can I monitor SSL certificate expiration?
- Can I monitor web servers behind a load balancer?
- What does "Operation timed out after x with y bytes received" mean?
- What does "couldn't connect to host" mean?
- What does "name lookup timed out" mean?
- Does Wormly support IPv6?
- How can I monitor a user log in / sign in on my website?