Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    HE.NET dyndns client stopped working

    Scheduled Pinned Locked Moved DHCP and DNS
    5 Posts 1 Posters 75 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N8LBVN Offline
      N8LBV
      last edited by

      I had set this up to update he.net DNS when WAN address changes.
      This worked flawlessly for several months and all my tests when I set it up.
      Recently it is no longer working and will not handshake successfully with he.net

      I do not get any errors in the GUI other than "a big red X" under status and the IP address is in red text and is the old IP address from when it last worked a week ago.
      And shows red IP address on the dashboard widget.

      Re-saving and forcing update does not fix it.

      I have not made any changes to passwords/keys.

      I'd like to troubleshoot this but the GUI does not give any contextual information to where relevant logs may be located.

      Looking for help on where I should be looking in terms of logs to try and fix this.

      I feel more like I do now.

      N8LBVN 1 Reply Last reply Reply Quote 0
      • N8LBVN Offline
        N8LBV @N8LBV
        last edited by

        It's in the main system.log

        Figured this much out:
        There was an error trying to determine the public IP for interface - wan (igb0

        Without verbose logging turned on.

        I'll search around to try and see if this is common or whatnot.

        I feel more like I do now.

        N8LBVN 1 Reply Last reply Reply Quote 0
        • N8LBVN Offline
          N8LBV @N8LBV
          last edited by

          I turned on verbose logging for this and still do not see any further information in the log than " There was an error trying to determine the public IP for interface - wan (igb0)"

          I feel more like I do now.

          N8LBVN 1 Reply Last reply Reply Quote 0
          • N8LBVN Offline
            N8LBV @N8LBV
            last edited by

            Disabling gateway monitor immediately fixed this.
            But it was working fine for 2+ months.
            And I moved it between different Internet connections and was fine for those 2-months.
            It just failed a few days ago after the WAN IP changed.

            Is this a bug or anything that needs further looking into on my part?

            I feel more like I do now.

            N8LBVN 1 Reply Last reply Reply Quote 0
            • N8LBVN Offline
              N8LBV @N8LBV
              last edited by

              Any thoughts on this?

              I feel more like I do now.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.