Hello, could you please tell me why this shake doesnt connect to server ?
Thanks in advance.
RSH.RDE7C.2025-01-08T10_00_32.logs.tar (3.2 MB)
1 Like
Hello Olivier, and welcome to our community!
Thank you for sending the logs of your Shake. From them, it appears that some steps in the unit configuration are missing. In particular:
Station Info
------------
Data-Sharing Mode : OFF
Data Server Conn : OFF
Could you please reboot your Shake and try the following procedure to see if it solves the connectivity issue?
Please access your
rs.local/page, go toSettings(the gear icon high on the left), and then theDatatab. Make sure that theForward Databox is checked, and then clickSave and Restart.The station should now be able to connect again.
From the logs, it seems that the Forward Data box is not checked, so this should solve the problem you are experiencing and make the Shake appear on our network. If not, please wait for around 10-15 minutes, download and re-send the new logs to see if there have been any changes that could point us towards a solution.
Thank you.
Hello Stormchaser,
Thank you for your quick answer.
But it appears that the box is already checked, if it’s the right one here (in french) :
2 Likes
Hello Olivier, no trouble at all.
Mmm, thank you for the screenshot. Can you try the following:
- Uncheck that box
- Click on the
Enregistrerbutton at the bottom of the page - Reboot the Shake
Then, when the Shake is up again:
- Check the box again
- Click another time on the button at the bottom
- And reboot the Shake again
If this doesn’t work, it may be due to the fact that your Shake is still using an older OS version, Software Version : v0.19, where there was a bug causing what you see, then corrected in v0.20.
To update you have two options:
- Wait until your Shake checks for an OS update (usually happening at reboot) and wait until the OS updates. Or
- Update manually following the instructions here: microSD card topics.
And, if you need any assistance, feel free to ask.
Wonderful, that did the trick… Thank you !
By the way, I was wondering why this shake didnt upgrade to 0.20 automaticly since it is online for some weeks ?
2 Likes
Great to read that. You’re more than welcome!
I was asking myself the same question, out of curiosity. Is your Shake behind some firewall/proxy server/internal network (like a school)?
Because there are some update errors in the logs (below)
fatal: unable to access ‘https://gitlab.com’: server certificate verification failed.
tha indicate that certificates validation fails, stopping your update progress. We have checked from our side, and the certificates are in place and valid, so there must be something else which is blocking the procedure.
Yes, it’s behind a firewall and filter content as we maintain scolar network.
Is there some IP adresses/ports to whitelist for software upgrade ?
1 Like
Ah, perfect. Thank you for confirming the network situation.
Our first recommendation is, if possible, to modify your Firewall rules by whitelisting registry.gitlab.com for SSL bypass. This should allow the Shake to communicate with GitLab and the procedure should advance now.
Otherwise, it is also possible to make modifications directly on the shake to fix this, but at this point, I would recommend manually installing the new OS version. It would be a faster and easier procedure.
Thank you ! We dont have a direct access to the shakes…
2 Likes
No problem at all.
If you need anything else, you know where to find us.
Well, it seems that no upgrade had been tried this night.
Extract from the upgrade.log, last iteration :
2025 008 13:29:28: Checking for software updates…
2025 008 13:29:28: Updating repo rsh-SW-updater
fatal: unable to access ‘raspberryshake-SW-public / rsh-SW-updater · GitLab’: server certificate verification failed. CAfile: none CRLfile: none
2025 008 13:29:29: Upgrading UPG to latest version
2025 008 13:29:29: Updating Docker image registry.gitlab.com/rshake-public/rsh-fe-config:v19
Error response from daemon: Get https://registry.gitlab.com/v1/_ping: x509: certificate signed by unknown authority
2025 008 13:29:30: Updating Docker image registry.gitlab.com/rshake-public/rsh-data-producer
2025 008 13:32:13: Checking for software updates…
2025 008 13:32:13: Updating repo rsh-SW-updater
fatal: unable to access ‘raspberryshake-SW-public / rsh-SW-updater · GitLab’: server certificate verification failed. CAfile: none CRLfile: none
2025 008 13:32:14: Upgrading UPG to latest version
2025 008 13:32:15: Updating Docker image registry.gitlab.com/rshake-public/rsh-fe-config:v19
Error response from daemon: Get https://registry.gitlab.com/v1/_ping: x509: certificate signed by unknown authority
2025 008 13:32:45: Updating Docker image registry.gitlab.com/rshake-public/rsh-data-producer
Error response from daemon: Get https://registry.gitlab.com/v1/_ping: x509: certificate signed by unknown authority
2025 008 13:33:15: Updating Docker image registry.gitlab.com/rshake-public/rsh-data-consumer
Error response from daemon: Get https://registry.gitlab.com/v1/_ping: x509: certificate signed by unknown authority
2025 008 13:33:17: Software updates complete.
Is there a command line to launch manually and remotely the upgrade ?
Is it the last line of the crontab ? I will double check if SSL inspection is desactivated for registry.gitlab.com…
@daily /usr/local/bin/myShake
@hourly /usr/local/bin/clean-logs
57 4 * * 5 /usr/local/bin/rsh-sw-fetcher C >/dev/null 2>&1
Thanks.
1 Like
So, We had to disable also SSL inspection for gitlab.com not only registry.gitlab.com
Everything is OK.
2025 009 08:02:54: Checking for software updates…
2025 009 08:02:54: Updating repo rsh-SW-updater
From raspberryshake-SW-public / rsh-SW-updater · GitLab
80d3fde…54f79c3 master → origin/master
2025 009 08:02:56: Upgrading UPG to latest version
2025 009 08:02:57: Installing ver 0.20 of the R-Shake system…
2025 009 08:03:03: Rebooting…
2025 009 08:03:48: Checking for software updates…
2025 009 08:03:48: Updating rsh-SW-updater
2025 009 08:03:50: Shake-OS is up to date (ver 0.20)
2025 009 08:03:50: Updating Docker image registry.gitlab.com/rshake-public/rsh-fe-config:v19
2025 009 08:03:53: Updating Docker image registry.gitlab.com/rshake-public/rsh-data-producer
2025 009 08:04:00: Updating Docker image registry.gitlab.com/rshake-public/rsh-data-consumer
2025 009 08:04:03: Software updates complete.
Thanks again.
2 Likes
Perfect, thank you for letting us know!
I’ll update our documentation so this information will be easily retrievable in the future.