After a long lasting power failure at the power company, when the router came back up it will not update its ddns via IP>Cloud.

It is stuck on 'updating...' for well over two hours and does not actually ever update its ddns. The router is an hAP ac^2 running v6.43.4

The router can resolve both cloud.mikrotik.com (81.198.87.240) and cloud2.mikrotik.com (159.148.147.201) and both IPs are reachable.

I can see packets going back and forth to IP 159.148.147.201 but nothing happens. I've also explicitly allowed both IPs in input/output chains just in case.

Trying with a different routerboard (mipsbe based) with v6.40.x from the same location, has the same behavior.

Anyone else experiencing the same issue?

Yes, I'm experiencing the same exact issue, it's been two hours now since I noticed it won't update. Several devices, internet connections, locations.

Yes, I just checked from other locations/ISPs too and it won't update.

Same here (Brazil), IP Cloud is not updating on 3 different locations/ISPs (made a mess out of my VPNs).

Response -
"Error: request timed out"

The new cloud (in 6.43 and above) works fine, but be warned: this is the worst moment to update as you cannot disable the ddns cloud service properly before upgrade.

https://mikrotik.com/download/changelog ... lease-tree

What's new in 6.43 (2018-Sep-06 12:44):

MAJOR CHANGES IN v6.43:
----------------------
!) cloud - reworked "/ip cloud ddns-enabled" implementation (suggested to disable service and re-enable after installation process);
----------------------

What this means: if you do not disable the ddns service before upgrading, your IP address will be kept in old cloud servers memory, which leads to unexpected situations (old ip re-appearing after disabling new cloud).

As the new IP Cloud implementation enters the bugfix-only stage, the old IP cloud will be disabled. Also, Old IP address will resurface only if you disable DDNS service. Also, before update, you can try to disable DDNS option in the old IP Cloud.

The problem occurred on both updated devices with the new cloud service and old devices with the old cloud service.

It just started to work the next day. But only after it caused havoc on vpns and other stuff that were based on ddns.

As the new IP Cloud implementation enters the bugfix-only stage, the old IP cloud will be disabled.

Are you disabling the old cloud services as soon as the new IP cloud service hits the long-term branch?

What about users who will wait for the next long-term version? Or have to wait for a maintenance window?

people on long-term version will have to upgrade to the new long-term version.

Response -
"Error: request timed out"

I am facing the same problem. Ddns is not updating ip adress. On force update my public ip shows there but i can't access through ddns.
I have also checked it with online dns to ip converter and there it is showing an old ip address.
This happened after i upgrade to 6.43.4 and then again downgraded to 6.40.8
I can access winbox with my public ip address.
Any solution? I'll b thankful

In change logs it is mentioned that when doing upgrades/downgrades accross version 6.42 (or is it 6.43?) boundary, one has to manually disable cloud services in the previous version, then do the upgrade/downgrade and at the end enable cloud again.

Hence the solution for @fiazahmmad: upgrade to 6.43.x again, disable cloud services, downgrade to 6.40.8 and enable cloud services again.

Hello,

yesterday I upgraded two RouterBoards 2011UiAS-2HnD from RouterOS 6.42.12 to 6.43.13 (different locations and ISPs).
Since the upgrade, the Cloud DDNS does not work anymore. The status always stays with "updating ...".
Rebooting the two routers and disabling and enabling the service did not help.

I always made a Downgrade back to 6.42.12, disabled Cloud Service and upgraded again to 6.43.13 - same problem.

Do you have an idea?

Thank you in advance.

Best Regards,
Manuel

No Idea?

Thank you.

Today I tried Version 6.43.14 and 6.44.2 - still same problem.
I don't understand why.

So I went back to 6.42.12...

Best Regards,
Manuel

check if you are not blocking the responses sent to IP Cloud servers. (you can resolve cloud.mikrotik.com IP to get the IP address) Also, writing to support is an option.

Also, disabling/enable "dance" is not required anymore when upgrading or downgrading from old IP Cloud to current.

Some routers on some locations get the cloud address some don't, similar config, version 6.44.3 - can not see the pattern yet.
Can ping/resolve both addresses cloud.mikrotik.com and cloud2.mikrotik.com on all.
Anything else to try besides the things mentioned in this post?

Thanks,
Borut

Hello,

now it's working with 6.43.16
There was really a problem with the DNS lookup of cloud2.mikrotik.com.
I can not explain it either... with a ping from the Routerboard hostnames has been resolved without setting a DNS Server under "IP" -> "DNS".
Now I have added a DNS Server under "IP" -> "DNS" - so the DDNS Cloud it's working!

It was my mistake!

Anyway thanks to the MikroTik Support for the help!

Best Regards,
Manuel

You chose IP --> DNS ---> use DNS Google: 8.8.8.8 / 8.8.4.4 and Update Cloud.