SFOS 18.0.0 EAP1-Refresh1 DDNS Fails on PPPoE Interface (DDNS update for host [DDNS Host] was Failed. Last Updated with IP 0.0.0.0. Failure Reason: noconnect)

Hi Leon,

        Thanks for the device access. 

As per our discussion in PM after entered the password again, your Namecheap DDNS successfully connected to the server.

Please get back to us if you face any issue again.

Hi Apurv, so yes at the core it was addressed by sorting out the authentication issues. However, it was complicated by some other factors.

As per our PM I believe most of this would be addressed in the documentation; however, the logs were not helpful at all.

Please improve the log entries and include information on what they possibly mean in the documentation along with guidance on possible solutions including how to clear the XG Cache.

Hi Apurv, so yes at the core it was addressed by sorting out the authentication issues. However, it was complicated by some other factors.

As per our PM I believe most of this would be addressed in the documentation; however, the logs were not helpful at all.

Please improve the log entries and include information on what they possibly mean in the documentation along with guidance on possible solutions including how to clear the XG Cache.

Leon Friend2 said:

As per our PM I believe most of this would be addressed in the documentation; however, the logs were not helpful at all.

Please improve the log entries and include information on what they possibly mean in the documentation along with guidance on possible solutions including how to clear the XG Cache.

I can imagine that troubleshooting the issue alone was almost impossible. Logging shall be improved into next major release (18.5). Please Sophos take it under consideration.

Hi Andrew, Apologies I can't find your request to do a direct reply but in short, the resolution on my end for Namecheap DDNS was to delete the entry and recreate it. the key is that the username needs to be your domain name.

Now the reason for deleting the profile and recreating it is that there is an odd backend timer that means if you just update the password it might not start working for 24 - 48 hours.