failing to access DynDNS
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- My Router
- :
- failing to access DynDNS
failing to access DynDNS
13-12-2022 4:49 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Hello
I have a Plusnet Hub One | Software version 4.7.5.1.83.8.263 .
I use noIP Dyndns service but somehow it's failing to update:
12:02:37, 11 Dec. | (833686.990000) Failed to update NoIP service. Server response: <myhost1.mydomain.net>:4 |
12:02:37, 11 Dec. | (833686.970000) Failed to update NoIP service. Server response: <myhost2.mydomain.net>:4 |
12:02:34, 11 Dec. | (833684.300000) Updating NoIP service with IP <myPublicIP> for host myhost1 |
12:02:34, 11 Dec. | (833684.290000) Updating NoIP service with IP 1<myPublicIP> for host myhost2 |
I can't any traction with noIP. does anyone use them successfully? I don't know what the error response 4 means
Re: failing to access DynDNS
13-12-2022 7:11 PM - edited 13-12-2022 7:13 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
What is the status of your hostnames if you log into the No-IP website?
You can query the No-IP API directly via a web browser by doing this:
http://<your_noip_username>:<your_no_ip_pasword>@dynupdate.no-ip.com/nic/update?hostname=<your_noip_hostname>&myip=<your_ip_address>
Replacing the obvious bits with the relevant information and removing the chevrons.
If the update is successful then you'll see something like:
good 1.2.3.4
Or maybe 'nochg', indicating that there's been no change to your IP.
If you see a failure when trying to access via web browser then the issue lies with No-IP, or you are using the wrong credentials.
Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵
Re: failing to access DynDNS
13-12-2022 9:15 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Yes that worked and so my host is now updated.
However, from the router itself http://192.168.1.254, it still fails.
Can I see more than just the Event logs to see more details?
Re: failing to access DynDNS
13-12-2022 9:49 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Are you able to private message me the hub serial number and the account you are using it from? The account I suspect is yours has a Hub One associated with it but it isn't running the firmware version mentioned in your original post
At the very least, we should be making sure the hub is running the latest firmware (although I have never known No-IP to be problematic on any of the Hub One firmwares).
Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page