Hi! We have been experiencing some weird behaviour on our site that is hosted on our droplet (currently only one).

Currently we have a check on pingdom that checks the uptime of some of our services, this check has begun to regularly fail. The only error we see from pingdom is: “No data received from server”. This now happens almost every day. It’s not the services themselves that go down since we check the logs, but rather the API call that is suppose to tell us if they’re down is not responding.

Is there any built in protection on digital ocean that could block this traffic? The calls from pingdom is from a bot after all and is done regularly. We have tried to debug on our end on the server but can’t find anything that could block the calls.

Pingdom does it’s calls from random locations and which ones that fail seems random. One day a call from Atlanta fails and a call from San Francisco succeeds, and the next day vice-versa.

We’re hosting the same site in Sweden on another hosting provider with the same site (but different domain) with the same check but that does not fail.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
3 answers

This issue has been resolved. It was a compability issue between the mpm and http2 module in apache. This resulted in random segfault errors.

Hello, @viktorwml

Could you please let me know if the call is simply a ping/curl request to your droplet and if you were able to replicate the issue at the same time when Pingdom reported outage/unavailability?

I’ve seen a lot of users complaining that Pingdom reports outages, but eventually they’re not able to replicate the issue on their end, so I believe this might be the same case here.

Looking forward to hearing from you.

Regards,
Alex

@alexdo I am noticing what appears to be a similar issue. We have services on Digital Ocean which appear to be behaving normally, however, an uptime check from Google Cloud Monitoring started failing spontaneously about 5 hours ago. The service process, droplet, and cluster all are to be behaving fine but the healthcheck is failing. Is there some sort of firewall that might be blocking traffic? The healthcheck is just a simple HTTPS check expecting status code 200. These healthchecks have been running fine for several weeks and this just started spontaneously today. Can you check to see if there might be something blocking traffic from certain IPs?

Submit an Answer