Your DDNS is not effective yet

Routers VPN, DNS, Leaks
1

This is frustrating. Whole reason to get GL.inet is because it just works for VPN. But not anymore.

The new router just constantly gives me “Your DDNS is not effective yet. Please try later.”

So it’s basically become an expensive paper weight lol. All other DNS options, as far as I can tell, have been removed.

2

Please give use more details about what your setup looks like, what you are trying to do.
Please refer to How to get support quickly

3

I think i figured out the problem.

I’m using a GL-B1300-ba6

And really just care about 1 thing, wireguard server to run w/ dynamic DNS so i can connect to it.

Wireguard turns out just fine, however to get Dynamic Dns working you have to go to:

“Applications” → “Remote Access”

Then enable dynamic dns, check the “I agree to all terms I didn’t read” box, AND ALSO enable “Enable HTTPS Remote Access”

It didn’t resolve till I did that last step. Which I do not want enabled, but i guess there’s a bug in the UI?

4

No, this shouldn’t be required for enabling DDNS.
What happens if you disable it and just enable DDNS?

5

DDNS stopped working 2 days ago for me now even the goodcloud service is not working…

6

DDNS does not need GoodCloud nor the other way around.
Could you please restart your router, wait 5 minutes and upload the logs?

7

Tried multiple restarts and enabling etc here are my logs
[logs removed]

8

Not sure about your time zone but the logs show me that your date isn’t the right one?
Could you please check date & time settings?

10

I second to this. Your timezone is not set correctly, that’s why goodcloud is failing!

11

[logs removed]
So just performed a factory reset and now im getting these logs but receiving connection timed out when accessing the router from my DDNS address

12 
Tue Apr 30 18:45:29 2024 authpriv.notice sudo:     root : PWD=/ ; USER=root ; GROUP=nonevpn ; COMMAND=/usr/lib/ddns/dynamic_dns_updater.sh -- stop
Tue Apr 30 18:45:30 2024 user.notice ddns-scripts[5969]: glddns: PID '5969' terminated by 'SIGTERM' at 2024-04-30 18:45
Tue Apr 30 18:45:31 2024 authpriv.notice sudo:     root : PWD=/ ; USER=root ; GROUP=nonevpn ; COMMAND=/usr/lib/ddns/dynamic_dns_updater.sh -- start
Tue Apr 30 18:45:34 2024 user.notice ddns-scripts[9304]: glddns: PID '9304' started at 2024-04-30 18:45
Tue Apr 30 18:45:39 2024 user.notice mwan3[9461]: Execute ifup event on interface modem_1_1_2 (wwan0)
Tue Apr 30 18:45:41 2024 user.notice mwan3[9461]: Starting tracker on interface modem_1_1_2 (wwan0)
Tue Apr 30 18:45:47 2024 user.info mwan3rtmon[8858]: Detect rtchange event.
Tue Apr 30 18:45:49 2024 daemon.info dnsmasq[1]: read /etc/hosts - 4 addresses
Tue Apr 30 18:45:49 2024 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Tue Apr 30 18:45:49 2024 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Tue Apr 30 18:45:50 2024 user.notice firewall: Reloading firewall due to ifup of modem_1_1_2 (wwan0)
Tue Apr 30 18:45:54 2024 authpriv.notice sudo:     root : PWD=/ ; USER=root ; GROUP=nonevpn ; COMMAND=/usr/lib/ddns/dynamic_dns_updater.sh -- stop
Tue Apr 30 18:45:56 2024 user.notice ddns-scripts[9304]: glddns: PID '9304' terminated by 'SIGTERM' at 2024-04-30 18:45
Tue Apr 30 18:45:57 2024 authpriv.notice sudo:     root : PWD=/ ; USER=root ; GROUP=nonevpn ; COMMAND=/usr/lib/ddns/dynamic_dns_updater.sh -- start
Tue Apr 30 18:45:59 2024 user.notice ddns-scripts[10855]: glddns: PID '10855' started at 2024-04-30 18:45
Tue Apr 30 18:46:10 2024 daemon.info dnsmasq[1]: read /etc/hosts - 4 addresses
Tue Apr 30 18:46:10 2024 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Tue Apr 30 18:46:10 2024 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Tue Apr 30 18:46:14 2024 daemon.err eco: (gl-cloud:535) disconnected	false	19	unexpected disconnect
Tue Apr 30 18:46:19 2024 daemon.debug eco: (gl-cloud:232) fetch server from:	https://gslb-eu.goodcloud.xyz/gslb/getbucket?deviceType=1&mac=9483c41fbe3c&sn=33333333333333&ddns=4444&timestamp=1714499179&sign=4444444444444444444444
Tue Apr 30 18:46:20 2024 daemon.debug eco: (gl-cloud:518) connected:	true	0	connection accepted
Tue Apr 30 18:46:20 2024 daemon.debug eco: (gl-cloud:525) connected:	0	connection accepted
Tue Apr 30 18:54:52 2024 daemon.info dnsmasq[1]: read /etc/hosts - 4 addresses
Tue Apr 30 18:54:52 2024 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Tue Apr 30 18:54:52 2024 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
13

Do you try from another device? You can’t try from your own network.
Enabling DDNS will not enable access as well, you need to enable this.

14

DDNS should be merely ddns without firewall settings.

Maybe older firmware?

image
image883×505 22.4 KB

15

Sorry I have to remove your file because it contains unique device info.

What is your firmware version?