upstream connect error

[walter.thoss]

since yesterday we can not update our IP address anymore. we receive this error message:

upstream connect error or disconnect / reset before headers

[rotblitz]

What update client do you use?   And what service?

[walter.thoss]

I have been using a shell script for two years now.

This host give the answer: https://updates.opendns.com

[rotblitz]

So you probably use wget or cURL in your shell script?

Is it possibly caused by this?  https://support.umbrella.com/hc/en-us/articles/360021913032

If not, what does a manual update via web browser result in?

https://updates.opendns.com/nic/update?hostname=YourNetworkLabel

See also https://support.opendns.com/hc/en-us/articles/227986527

If this succeeds, then your problem is with your shell script, not with OpenDNS.  Ensure that you have a valid user agent string configured.  The update server may check this.

[walter.thoss]

I use wget.

The link you have post, does not work, same error.

[rotblitz]

You're absolutely correct.  I get the same error.  :(

upstream connect error or disconnect/reset before headers

I'll shortly raise a support ticket about this.

What you can do to temporarily overcome the issue is one of these:

• Visit https://dashboard.opendns.com/settings/ to click the green arrows icon to perform a manual update.
  
  
• Send your updates through DNS-O-Matic.  This still seems to work, at least for me.

  https://updates.dnsomatic.com/nic/update

  You must configure OpenDNS as service at DNS-O-Matic before to make it work.

[rotblitz]

I have raised ticket #555086 now.

Edit:
Raised another ticket #555119 from the Umbrella forum.

[rotblitz]

Another symptom can be:

wget -O - -S --no-check-certificate https://updates.opendns.com/nic/update?hostname=example
--2019-02-09 23:39:42--  https://updates.opendns.com/nic/update?hostname=example
Auflösen des Hostnamen »updates.opendns.com«.... 146.112.255.50
Verbindungsaufbau zu updates.opendns.com|146.112.255.50|:443... verbunden.
WARNUNG: Kann das Zertifikat von »updates.opendns.com« nicht prüfen, ausgestellt von »/C=US/O=DigiCert Inc/CN=DigiCert SHA2 Secure Server CA«:.
  Ein selbst-signiertes Zertifikat gefunden.
WARNUNG: Der Common Name »api.opendns.com« des Zertifikates entspricht nicht dem angeforderten Hostname »updates.opendns.com«.
HTTP Anforderung gesendet, warte auf Antwort...
  HTTP/1.1 426 Upgrade Required
  date: Sat, 09 Feb 2019 22:39:42 GMT
  server: opendns
  content-length: 0
2019-02-09 23:39:42 FEHLER 426: Upgrade Required.

https://httpstatuses.com/426

[rotblitz]

See also https://support.opendns.com/hc/en-us/community/posts/360040994471

[w3d]

I'm seeing the same response with the "official" Windows OpenDNS Updater client. From the "log" I can see intermittent failures started 3 days ago. It improved for almost a day, but then more regular failures occurred and in the last day it's total failure.

2019-02-10 00:36 - connect error or disconnect/reset before headers
2019-02-10 00:24 - connect error or disconnect/reset before headers
2019-02-09 22:10 - connect error or disconnect/reset before headers
2019-02-09 19:10 - connect error or disconnect/reset before headers
2019-02-09 16:09 - connect error or disconnect/reset before headers
2019-02-09 16:07 - connect error or disconnect/reset before headers
2019-02-09 15:54 - connect error or disconnect/reset before headers
2019-02-09 12:54 - connect error or disconnect/reset before headers
2019-02-09 09:53 - connect error or disconnect/reset before headers
2019-02-09 06:53 - connect error or disconnect/reset before headers
2019-02-09 03:53 - connect error or disconnect/reset before headers
2019-02-09 00:53 - connect error or disconnect/reset before headers
2019-02-08 21:53 - 203.0.113.111
2019-02-08 18:53 - connect error or disconnect/reset before headers
2019-02-08 15:53 - 203.0.113.111
2019-02-08 12:53 - 203.0.113.111
2019-02-08 09:53 - connect error or disconnect/reset before headers
2019-02-08 06:53 - 203.0.113.111
2019-02-08 03:53 - connect error or disconnect/reset before headers
2019-02-08 00:53 - 203.0.113.111
2019-02-07 21:53 - 203.0.113.111
2019-02-07 18:53 - connect error or disconnect/reset before headers
2019-02-07 15:53 - connect error or disconnect/reset before headers
2019-02-07 12:53 - connect error or disconnect/reset before headers
2019-02-07 09:53 - 203.0.113.111
2019-02-07 06:53 - 203.0.113.111
2019-02-07 03:53 - 203.0.113.111
2019-02-07 00:53 - 203.0.113.111
2019-02-06 21:53 - 203.0.113.111
2019-02-06 18:52 - 203.0.113.111
2019-02-06 16:31 - 203.0.113.111
2019-02-06 13:31 - 203.0.113.111
2019-02-06 10:31 - 203.0.113.111
2019-02-06 07:31 - 203.0.113.111
2019-02-06 04:31 - 203.0.113.111
2019-02-06 03:36 - connect error or disconnect/reset before headers
2019-02-06 00:41 - 203.0.113.111
2019-02-05 21:40 - connect error or disconnect/reset before headers
2019-02-05 18:40 - 203.0.113.111 --- OK BEFORE THIS POINT

[chrstew2]

Hello walter.thoss, rotblitz, and w3d

There was recent changes made to updates.opendns.com. In the off chance that you have have firewall rules set up that are whitelisting traffic to the domain based on it's IP, we recommend that you update these rules to allow the traffic based on the domain name instead. This is because we've changed the IP of the domain.

For details, please refer to our article https://support.umbrella.com/hc/en-us/articles/360021913032

[rotblitz]

I got a reply to my ticket.  The developers are on the issue.

[walter.thoss]

The next problem!

Now the Update Answer is: nohost

We take a look, our host exist.

[walter.thoss]

Now it works perfect!

THX

[w3d]

Yes, this started working OK for me too yesterday (2019-02-11 09:56 UTC) and has been working OK since (1.5+ days) according to my logs. No change made at my end, using the Windows "OpenDNS Updater" v2.2.1.