After some severe weather, we experienced a power outage that lasted several days. During this time, my Raspberry Shake was powered off. After the storm, we also had to change our internet service provider because the previous provider’s infrastructure was damaged.
Currently, the Raspberry Shake is connected to the router via Wi-Fi. Everything appears to be working correctly on the local network: I can access the device through rs.local, the SeedLink and Winston servers are running, and ZeroTier allows remote access without any issues.
However, the Raspberry Shake does not connect to the Raspberry Shake servers. Someone mentioned that they experienced a similar problem while using Wi-Fi and that it was resolved after switching to an Ethernet connection.
Before the outage and ISP change, I was using Ethernet, but the new router is located too far from the Raspberry Shake. I have already ordered a longer Ethernet cable and am waiting for it to arrive.
In the meantime, is there anything I can do to troubleshoot or resolve this issue while continuing to use Wi-Fi?
Additional information:
The Raspberry Shake is connected to a home network.
The hardware was supplied by Raspberry Shake and has not been modified.
Local services and remote access through ZeroTier are functioning normally.
The only issue is that the station is not connecting to the Raspberry Shake servers.
Hello Jonathan, and welcome back to the community!
Thank you for reaching out to us about this data transmission issue, and also for attaching the logs.
Nothing peculiar appears from the logs themselves (you had some time adjustment interruptions a few days ago, but they don’t appear to be happening anymore), so could you try the following procedure on your Shake?
turn off your Shake
disconnect its power cable
restart your router (if possible) and wait for it to regain internet connection
now reconnect the power cable to the Shake and turn it on again
Then wait for about 30-60 minutes, and when you can, download the new logs from the instrument and send them to me. I would like to see if there are any differences compared with the current log set, and also what the logs show after a full, fresh, restart.
Seems like the problem continues while using ethernet, could it be the change from ISP?, we had to change because the one from before had their infraestructure damaged after a storm. Right now the service is a rural fiber optic that gets its data from a starlink service, then they connect their infraestructure to that starlink and redistrubute it via fiber optic to houses with a modem (could that intefere?) RSH.RAAC8.2026-06-21T22_47_49.logs.tar (5.3 MB)
This are the logs after changing to ethernet
We had other users testing and successfully connecting their Raspberry Shakes via Starlink. If the default configuration of the router is not working, maybe this can help:
However, since the terminal is not yours, you would need to ask the service managers to check.
On your side, what you can do as a last test is to Factory Reset the Shake configuration using this button in Settings - Security:
This will reset all configurations, so by doing this (save all the data from the Shake, if you need it), you’ll make the Shake “see” the new configuration with Starlink as if it were the first time. If there is any conflict between the old and the new network setups, this will resolve it.
And another test you can try is to bring the Shake to a friend’s (or colleague’s) house and see if, from there (make sure they have a different internet connection), the instrument manages to connect.
Before relocating the station, I performed a factory reset. However, it appears that only the station password was reset. The station location, personal information, helicorder settings, and local seismic data are still present. Is this expected behavior? I assumed a factory reset would restore the station to its original factory state. Am I misunderstanding how the factory reset function works?
I will relocate the station tomorrow for testing and hope this resolves the connection issue.
I moved it to another place (and before connecting reinstalled shakeOS) and it works! i hope it was the OS or something, will try to move it back to the old place, if not im going to have to move it
To reply to your first (of the two) message: no, a reset should have brought you back to the Shake’s welcome screen, not just reset the password.
Could I ask you to send me the logs of this Shake whenever possible?
For the second message: great news! If you don’t change anything and, at your old location, the unit still refuses to connect to the server, then we can say with 99% certainty that the Starlink connection is stopping data transfer.
Just to confirm, i brought the shake to test it again in the old location with the new ISP, and the same thing happened, local services and zerotier works, but its not connecting to the datacenter, i will have to move it to the other location (its a bit noisier and has an unstable internet connection) however in the future i plan to move it back to the other town, its noisier than here, but the internet is more stable over there, i will review both options, just to confirm there are the logs from the new location RSH.RAAC8.2026-06-29T02_43_49.logs.tar (2.1 MB)
Then yes, as things stand, it appears that the new ISP at the old location is blocking data connection to our servers.
Thank you for the new logs. Everything appears clean except for the connection itself, as you have seen. You could try asking them to allow communication on ports 55555 and 55556 (also adding port 123), but since it’s a public-facing Starlink connection, I don’t know if the managers would green-light this.
For now, the best solution is the other location, even if it has the issues you listed.
