HTTP 0 response code for a URL

[MridulS]

Describe the bug For the url https://vocabularies.cessda.eu the uptime action gives out a HTTP 0 response (from the curl function), but the URL is up and active.

To Reproduce

1. Add https://vocabularies.cessda.eu to sites: https://github.com/GESISWTS/uptime/commit/2985d9293cab75ed7efbf101e81a743f2a23ea5d
2. Error (HTTP 0) at https://github.com/GESISWTS/uptime/runs/1645754812?check_suite_focus=true#step:5:87

Expected behavior It should show the URL as up.

[AnandChowdhary]

Very interesting, I have no idea why this error is coming: Error: Timeout was reached. I was able to run the site normally so let me have a closer look at this!

[MridulS]

BTW this has happened again: https://github.com/gesisnotebooks/status/issues

A lot of end points are giving the HTTP 0 error response.

EDIT: I pushed a new line commit to rerun the CI, it fixed up everything AND deleted the issues (is the deleting part intentional?)

[AnandChowdhary]

The HTTP 0 happens when we didn't get a response. It's definitely specific to your site, since we haven't seen this anywhere else. Can you tell me more about where you host, etc.?

Yes, issues are deleted automatically when we think the site wasn't really down and it was a false negative.

[jefferycline1]

On Thu, Jan 7, 2021 at 6:24 AM Anand Chowdhary [email protected] wrote:

The HTTP 0 happens when we didn't get a response. It's definitely specific to your site, since we haven't seen this anywhere else. Can you tell me more about where you host, etc.?

Yes, issues are deleted automatically when we think the site wasn't really down and it was a false negative.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/upptime/upptime/issues/171#issuecomment-756057574, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQO7X2UZAH4GTSOVQIODYWLSYWKWPANCNFSM4VTOUIDA .

-- null

[niraj8]

This happens for some URLs here too -> https://github.com/niraj8/uidai-status/runs/1911663163?check_suite_focus=true#step:3:17

@AnandChowdhary How can I debug this?

[ghost]

Here's another example: https://github.com/xnaas/nitter-instances/runs/2016060659?check_suite_focus=true#step:3:10

There's definitely no issues accessing https://nitter.net at this time and it does have a valid certificate; however:

$ curl -I https://nitter.net
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

This may be a curl bug of some sort and not directly related to upptime?

---

and for @niraj8's linked site:

$ curl -I https://resident.uidai.gov.in
curl: (7) Failed to connect to resident.uidai.gov.in port 443: Connection refused

$ curl -I http://resident.uidai.gov.in
curl: (7) Failed to connect to resident.uidai.gov.in port 80: Connection refused

...but I also can't access it via a browser at all, so... ¯\_(ツ)_/¯

[Lvl4Sword]

@xnaas https://www.ssllabs.com/ssltest/analyze.html?d=nitter.net&s=167.233.9.51 shows certificate issues, for what that's worth.

[ghost]

So strange. Wonder what the hell Chain issues | Incomplete even means...If it was bad, you'd think most browsers would refuse to load it or give a warning...? I suppose that's outside of the scope of this issue, however.

[fabiofdsantos]

We noticed the same issue (temporary):

Checking https://www.dogchef.com/en/account
30
Current status undefined up 2021-05-08T09:22:31.000Z
31
Got an error (on error) [Error: Timeout was reached]
32
Result from test 0 0
33
Got an error (on error) [Error: Timeout was reached]
34
Result from test 0 0
35
Got an error (on error) [Error: Timeout was reached]
36
Result from test 0 0

[nullawu]

Same issue, and I got some details may be helpful.

For one of my sites:

1. At beginning. Http is good but https site is always down with status code 0;
2. Nginx conf changed, redirect http to https. Then both http and https sites are down with same status code;
3. __dangerous__disable_verify_peer: true added to http site. Http site is up, and https site keeps down.

The https site could be viewed in chrome and firefox without any alerts. So it should not be ssl certificate reasons?

[vicevolf]

😕 more and more，HTTP Code 0

HTTP code: 0
Response time: 0 ms

Nearly more than 20 pages have this problem https://github.com/volfclub/travellings-upptime/issues

[HugoGresse]

we are also experiencing this issue at Pl@ntNet, job log. Maybe double check with another uptime provider to see if this is a real issue or an upptime issue?

[meyersbs]

I also intermittently get the following for one of my sites (a GitLab pages site).

HTTP code: 0
Response time: 0 ms

The site is definitely up.

[mschirrmeister]

I get this HTTP code: 0 as well. At every second cycle. The sites are definitely up. But the status of all the sites go like, up, down, up, down,...

Got an error (on error) [Error: Failed sending data to the peer]
Result from test 0 0
Got an error (on error) [Error: Failed sending data to the peer]
Result from test 0 0
Got an error (on error) [Error: Failed sending data to the peer]
Result from test 0 0

I have a feeling this might be somehow a github issue. Like if these runners cannot connect.

[AnandChowdhary]

@mschirrmeister from https://github.com/curl/curl/issues/10591, it's recommended to update the version of libcurl (will do!) when you sett "Failed sending data to the peer", but I would have assumed that this would happen to all requests and not every alternate one. Totally strange.

[mschirrmeister]

@AnandChowdhary But if the monitor probe is just doing a GET, then there is nothing uploaded. Wondering what it is trying to send. And yes, I guess it should happen always and not only on every second run.