What's new

DDNS Status: Server Error/Inactive

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Don Draper

Occasional Visitor
For the past couple of months my router as shown a green bell indicating server error when I login.
When I look at my DDNS settings it says:
DDNS Status: Inactive

Log states:
Apr 5 11:10:00 Let's_Encrypt: Err, DDNS update failed.
Apr 5 11:15:00 rc_service: service 20380:notify_rc restart_letsencrypt
Apr 5 11:15:00 Let's_Encrypt: Err, DDNS update failed

RT-AX86U Pro
Current Version : 3004.388.6_2
Server: www.asus.com
Local Access Config set to both

Tried troubleshooting on my own for awhile now without any luck sadly.
 
For the past couple of months my router as shown a green bell indicating server error when I login.
When I look at my DDNS settings it says:
DDNS Status: Inactive

Log states:
Apr 5 11:10:00 Let's_Encrypt: Err, DDNS update failed.
Apr 5 11:15:00 rc_service: service 20380:notify_rc restart_letsencrypt
Apr 5 11:15:00 Let's_Encrypt: Err, DDNS update failed

RT-AX86U Pro
Current Version : 3004.388.6_2
Server: www.asus.com
Local Access Config set to both

Tried troubleshooting on my own for awhile now without any luck sadly.
What DDNS service are you using? Does it have an account that has to be renewed?
 
The error comes from Let's Encrypt trying to do DNS-based validation. If using the Asuscomm DDNS, make sure you DDNS is working properly.
 
How would one do that?
The DDNS status usually gets reported on the DDNS page, you can also check the system log for recent inadyn entries.
 
The DDNS status usually gets reported on the DDNS page, you can also check the system log for recent inadyn entries.
I did a factory reset and everything seems to be working well at this point no, except the following error:
Apr 8 11:10:03 rc_service: watchdog 2436:notify_rc stop_aae
Apr 8 11:10:03 rc_service: watchdog 2436:notify_rc start_mastiff
Apr 8 11:10:03 rc_service: waitting "stop_aae" via watchdog ...
Apr 8 11:10:04 Mastiff: init

I recall seeing this before and disabling the Asusnat tunnel.
Could that have caused my DNNS issue? I'm tempted to disable again and try but wanted your input first please.
 
I did a factory reset and everything seems to be working well at this point no, except the following error:
Apr 8 11:10:03 rc_service: watchdog 2436:notify_rc stop_aae
Apr 8 11:10:03 rc_service: watchdog 2436:notify_rc start_mastiff
Apr 8 11:10:03 rc_service: waitting "stop_aae" via watchdog ...
Apr 8 11:10:04 Mastiff: init

I recall seeing this before and disabling the Asusnat tunnel.
Could that have caused my DNNS issue? I'm tempted to disable again and try but wanted your input first please.
That's not an error, just a notification of a service restarting.
 
Since a factory reset the issue has returned - throwing a constant DDNS error. I also noticed when I go to the Amazon Alexa page (initially setup following the factory reset) it now says"Please click here to enable DDNS and Web Access from WAN for remote control." I click it and nothing changes other than a count to 100%.
Enable Web Access from WAN is enabled.

I'm unsure where to start troubleshooting ...please advise.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top