upstream connect error

Comments

24 comments

  • Official comment
    Avatar
    Christopher Stewart

    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

  • Avatar
    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.

  • Avatar
    rotblitz (Edited )

    What update client do you use?   And what service?

  • Avatar
    walter.thoss

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

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

  • Avatar
    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.

  • Avatar
    walter.thoss

    I use wget.

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

  • Avatar
    rotblitz (Edited )

    I have raised ticket #555086 now.

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

  • Avatar
    rotblitz (Edited )

    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

  • Avatar
    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

  • Avatar
    rotblitz

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

  • Avatar
    walter.thoss

    The next problem!

    Now the Update Answer is: nohost

    We take a look, our host exist.

  • Avatar
    walter.thoss (Edited )

    Now it works perfect!

    THX

  • Avatar
    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.

  • Avatar
    rotblitz (Edited )

    Correct, according to the response to my ticket this should be solved.  No further details were provided.

  • Avatar
    micalkin

    as of today I'm still getting this error while using ddclient

    RECEIVE: HTTP/1.1 426 Upgrade Required
    RECEIVE: date: Sat, 16 Feb 2019 19:37:41 GMT
    RECEIVE: server: opendns
    RECEIVE: content-length: 0

  • Avatar
    walter.thoss

    Today opendns also not work:

    Unknown response

    What ist the problem?

  • Avatar
    walter.thoss

    Now I have this returncode: Unknown Response 8

  • Avatar
    rotblitz (Edited )

    I'm confident that you rose a support ticket, because it is clear to you that we other users cannot really help here.  Else you would be able to help yourself.

  • Avatar
    w3d

    @walter.thoss FWIW it appears to be working OK from my end. Since the service came back for me on 2019-02-11 09:56 UTC, it appears to have been working OK uninterrupted ever since (6+ days).

  • Avatar
    walter.thoss

    I just want to show here that I did not change my script with wget. This script runs daily for 2 years. So opendns has made changes, so the service did not work at first. Now it does not work with wget anymore. I have now rewritten my script to curl, but wanted to know the opendns of it,

    So I write in here.

  • Avatar
    rotblitz

    Not sure what you mean by "wanted to know the opendns of it".  Especially, what is "it"?

    Whatever, to communicate with staff, your best bet is to raise a support ticket.  Here are almost other users.

  • Avatar
    edo.g

    I'm facing the same error "upstream connect error or disconnect/reset before headers". What should I do? I tried surfing around the forum with people saying that now everything is ok without giving a solution

  • Avatar
    rotblitz

    As has been said multiple times above, you raise a support ticket.

Please sign in to leave a comment.