QNAP NAS Community Forum

I have 14 QNAP servers that are setup with myQNAPcloud . 90% of them are reporting warnings every 10 minutes
Severity: Warning
Date/Time: 2020/05/22 22:42:36

App Name: Network & Virtual Switch
Category: Infrastructure
Message: [Network & Virtual Switch] Failed to update DDNS "myQNAPcloud".

When i log into myQNAPcloud portal none of my QNAPS appear, it just spins at loading. Tried this on multiple sites and also on my mobile phone and all produce that same "loading" spin forever.

my situation is, i enabled myqnapcloud. tested it works.

then later i decide to disable myqnapcloud. unregister device in myqnapcloud website, remove lets encrypot cert, remove cloudlink, remove port forward.

then later i noticed i too was getting this failed to update ddns myqnapcloud.

i get brought to myqnapcloud ddns settings. i click disable, but it won't let me.

next thing i tried is in myqnapcloud to signout, won't let me either.

also went to virtual network and see if i can remove the myqnapcloud dyndns entry there, also can't.


All i could find in reference to this situation was this

schumaku wrote: ↑Wed Feb 01, 2017 6:17 pm The trick is easy: Go to https://www.myqnapcloud.com/ - select the device, go to [Device details], and use [Unregister].

After an email chat with QNAP I learnt that there will be some connectivity updates regardless for the "convenience" reasons. Still unclear to me why the disabled DDNS does still trigger the DDNS updates. Will challenge QNAP again after the Chinese New Year.

Regards,
-Kurt.

viewtopic.php?t=129255#p595354


I'm using the latest 4.4.2 build

Just adding a me as well post on this. Started 11:30pm same warning every 10 mins. Current firmware; no network changes.

i already created a ticket here
https://service.qnap.com/en


but based on that post i linked earlier, somethings tells me this is not necessarily a problem that begin with the latest qts build, but something that existed since a while back ???

yeap same here, no change no firmare update since yesterday i woke up with 40 emails alerts
i click on test and the connectivity says ok it is all green.

what is its problem ???

Have the same problem, a bucket load of emails from 2:43UTC to 6:13UTC (every 10mins), QNAP cloud DDNS ones, Sydney Australia if location dependent.
Although the last hour it has been OK, so I guess the outage is over? QNAP service status page shows all green at the moment, would be interesting to see if it was a planned outage?

I haven't updated firmware in a couple of months so it isn't related to that for those here suggesting this.

Not sure if this will help, but it is at least a hint for a solution.

in my logs i noticed that myqnapcloud is signed out. and since then i no longer get the dyndns failed spam.

so you need to somehow go to qts, myqnapcloud and sign out from myqnapcloud.


only reason why i say hint, is because earlier i tried to sign out but it wouldn't let me. i only checked log later and it says i'm now signed out. not quite sure how that happened.


In summary, they need to relook at the process for removing myqnapcloud. because it seemingly has some faultiness that cause this ddns spamming when you try to disable/undo myqnapcloud from your configuration the issue might be not following the undo steps in order, and this could result in this situation.

i believe the correct step might be to first go myqnapcloud and select the disable ddns FIRST thing. only after that then you should sign out myqnapcloud from within qts. then you can remove your lets encrypt cert (this should go back to qnap default). disable cloudlink, then go appcenter and remove it. only after that, then you go to myqnapcloud website to unregister your device. then lastly you can go router and disable portforwarding.

i suspect the problem occured because i didnt disable ddns and unsign from myqnapcloud early on in the steps when trying to remove myqnapcloud :/

Moogle Stiltzkin wrote: ↑Sat May 23, 2020 6:53 pm
i suspect the problem occured because i didnt disable ddns and unsign from myqnapcloud early on in the steps when trying to remove myqnapcloud :/

this was no ones fault.
this was due to qnap servers.
it got fixed on its own

great_vc wrote: ↑Sun May 24, 2020 5:39 pm this was no ones fault.
this was due to qnap servers.
it got fixed on its own

good to hear.

but i don't think that quite explains why

1. myqnapcloud ddns could not be disable in qts
2. why cannot sign out from myqnapcloud in qts

maybe they should take alook at that how can myqnapcloud ddns server issues be having a qts issue, that will not allow you to disable ddns service to stop the ddns fail spam

yes i understand why ddns server itself having issues, may result in the alerts. but why on earth would they lock/prevent disabling ddns within qts? that doesn't make sense.