My router only connects very briefly to GoodCloud on booting

As mentioned in the topic, my router only connects very briefly to the Goodcloud when it is started, and then it is offline. I have read some topics here that seem to point towards timezone issues?

I am located in Iceland and I am using the Atlantic/Reykjavik timezone. My device is a GL-X300B.

While I am here, I have setup the Astrorelay service, but when I reboot my router it get’s a new IP address and that is not updated in Astrorelay, so I have to change it manually. Any idea what this problem is?

Please follow this guide to gather additional information. Especially the log files:

To answer this automated reply. I was looking for logs, but I don´t see to find them in my interface on my router. Perhaps it doesn´t have this feature?

Nah, nothing automated. All handcrafted.

Which firmware version are you running? All routers should have logs.

I am running 3.217. I saw in another post here on this forum a screenshot that does not look like my interface.

The post I am referring to: Goodcloud keeps showing router offline - GoodCloud and Astrorelay - GL.iNet (gl-inet.com)

Here is mine:

Ok, I found the logs:

Logs

Cloud Operation Logs

init set log level = 6

mqtt start!

mqtt init success!

Subscribe succeeded

Subscribe succeeded

[ 99.295985] do_page_fault(): sending SIGSEGV to gl_mqtt_service for invalid read access from 00000000

[ 99.296023] ra = 0040623d in gl_mqtt_service[400000+d000]

init set log level = 6

mqtt start!

mqtt init success!

Subscribe succeeded

Subscribe succeeded

[ 150.057881] do_page_fault(): sending SIGSEGV to gl_mqtt_service for invalid read access from 00000000

[ 150.057918] ra = 0040623d in gl_mqtt_service[400000+d000]

init set log level = 6

mqtt start!

mqtt init success!

Subscribe succeeded

Subscribe succeeded

[ 213.228651] do_page_fault(): sending SIGSEGV to gl_mqtt_service for invalid read access from 00000000

[ 213.228686] ra = 0040623d in gl_mqtt_service[400000+d000]

init set log level = 6

mqtt start!

mqtt init success!

Subscribe succeeded

Subscribe succeeded

[ 275.793106] do_page_fault(): sending SIGSEGV to gl_mqtt_service for invalid read access from 00000000

[ 275.793143] ra = 0040623d in gl_mqtt_service[400000+d000]

init set log level = 6

mqtt start!

mqtt init success!

Subscribe succeeded

Subscribe succeeded

[ 338.839130] do_page_fault(): sending SIGSEGV to gl_mqtt_service for invalid read access from 00000000

[ 338.839167] ra = 0040623d in gl_mqtt_service[400000+d000]

init set log level = 6

mqtt start!

mqtt init success!

Subscribe succeeded

Subscribe succeeded

[ 401.539104] do_page_fault(): sending SIGSEGV to gl_mqtt_service for invalid read access from 00000000

[ 401.539140] ra = 0040623d in gl_mqtt_service[400000+d000]

init set log level = 6

mqtt start!

mqtt init success!

Subscribe succeeded

Subscribe succeeded

[ 465.330774] do_page_fault(): sending SIGSEGV to gl_mqtt_service for invalid read access from 00000000

[ 465.330811] ra = 0040623d in gl_mqtt_service[400000+d000]

init set log level = 6

mqtt start!

mqtt init success!

Subscribe succeeded

Subscribe succeeded

[ 527.818833] do_page_fault(): sending SIGSEGV to gl_mqtt_service for invalid read access from 00000000

[ 527.818870] ra = 0040623d in gl_mqtt_service[400000+d000]

init set log level = 6

mqtt start!

mqtt init success!

Subscribe succeeded

Subscribe succeeded

[ 591.102344] do_page_fault(): sending SIGSEGV to gl_mqtt_service for invalid read access from 00000000

[ 591.102391] ra = 0040623d in gl_mqtt_service[400000+d000]

init set log level = 6

mqtt start!

mqtt init success!

Subscribe succeeded

Subscribe succeeded

[ 656.136177] do_page_fault(): sending SIGSEGV to gl_mqtt_service for invalid read access from 00000000

[ 656.136214] ra = 0040623d in gl_mqtt_service[400000+d000]

init set log level = 6

mqtt start!

mqtt init success!

Subscribe succeeded

Subscribe succeeded

[ 721.490426] do_page_fault(): sending SIGSEGV to gl_mqtt_service for invalid read access from 00000000

[ 721.490466] ra = 0040623d in gl_mqtt_service[400000+d000]

init set log level = 6

mqtt start!

mqtt init success!

Subscribe succeeded

Subscribe succeeded

[ 784.026070] do_page_fault(): sending SIGSEGV to gl_mqtt_service for invalid read access from 00000000

[ 784.026107] ra = 0040623d in gl_mqtt_service[400000+d000]

init set log level = 6

mqtt start!

mqtt init success!

Subscribe succeeded

Subscribe succeeded

[ 849.429448] do_page_fault(): sending SIGSEGV to gl_mqtt_service for invalid read access from 00000000

[ 849.429487] ra = 0040623d in gl_mqtt_service[400000+d000]

Like mentioned, it will show as available after a restart (can be repeated), but after a short while it will no longer be available. Not sure what the logs can tell us.

Here is a screenshot of the device when it was visible and the time:

It looks like an issue with the service itself, it seems to crash.
@hansome any idea?

I just connected the device in the location it should reside in the future. When I started it, it logged on to Goodcloud, but again, after a short time, it showed as offline. I then shut it down and then I got an email that it was offline.

This is a screenshot of the mails:

I tested 3.217 with goodcloud and astrorelay enabled but didn’t reproduce the issue.
Could you please elaborate what setting did you make to x300b?

I can do that, but really there is not much too the changes/settings I made. Can I somehow export them or can you tell which screenshots to share?

I can also see that it is online at this moment and it has been several hours since I restarted last time, so perhaps it is working now? I still see the error that @admon posted though.

Please try firmware 4.5, the goodcloud program for 4.5 is reconstructed.
https://dl.gl-inet.com/?model=x300b&type=rc

Thanks. I will try that, but right now the device is located remotely and it is working with VPN via AstroRelay on the 4G IP address. If I reboot the device the address will change and I won´t be able to reach it. I am waiting for my carrier to apply a static IP address on 4G.

Having said this, it would be great if AstroCloud could pick up on changed addresses, of perhaps if the GoodCloud would show last known address for 4G, as it has been shown that my FW logs on at the start and will post information.

I don´t know yet when I will be able to apply the FW. I might be brave enough to try it after the IP address has been fixed :slight_smile:

Hello again. I haven´t been around the device to update it, but it has actually shown itself on Goodcloud in the meantime.

The problem is, I know it was rebooted this morning due to a network outage and I am unable to connect to it now via mobile as I don´t know the 4G IP address. I know this is normally shown in the Goodcloud interface, but obviously I don’t see it.

I do see that Goodcloud claims the device was online, but then offline at the same minute.

How can I get the IP address of the 4G connection? It cannot be seen in the offline information of the device. Is the information available somewhere on the backend?

I have it also connected via the WAN port to LAN, but I cannot connect via that port as I hadn´t configured it. It does seem to answer on Port 53 though.

Edit:

Does this not indicate that the device is indeed connecting?

image

Connecting very briefly to GoodCloud on booting is possible.
For example, goodcloud gets online after the 4G network is ready.
After a while, the VPN network is established, but it doesn’t let the goodcloud traffic pass.
Then it will go offline.

I suggest you upgrade to firmware 4.5, export and send the system log to debug.

Thanks. I would indeed like to do the Firmware upgrade, but I would need to connect to it first remotely and connect Port 80 on the WAN port (which is connected to LAN).

For that, I need the current IP address of the device on the 4G network. Is it possible to get this from “behind the scenes” in the Goodcloud?

EDIT: As I finished writing, I checked GoodCloud and the device was showing, so I now have the IP address of 4G and am able to connect. Will try to update a.s.a.p.

I have managed to connect and make the admin interface available on my network so I can manage the device now.

I am trying to update the FW but when I try I cannot seem to complete it. I get a timed out error. I have reached as far as “verifying”.

You are uploading firmware by goodcloud right? This could happen when network is slow. Is it possible to upgrade by admin panel locally?

I am using the admin panel locally on the device, but trying to upload over the network from my home to the holiday home where the device is located. Unfortunately I don´t have the possibility right now to upload to a computer on the local network.

I was thinking if it could be better to upgrade the firmware from the Luci interface? Or perhaps I can upload it via SSH to the device and start the update from there?

Let me update this. I managed to reach my local LAN computer and tried to upload the FW. I had the same thing happen. I then rebooted the device and was then able to upload.

The new “problem” is that I get the following message about the FW. Obviously I want to keep my settings. Should I move forward with the update?

3.x → 4.x?
You can’t keep the settings, sorry.