Hi,
I would like to ask for your help to determine the reason why my shakes can’t connect to the server. Last week it successfully connected but after few days it didn’t. My shakes are newly formatted and I’m doing the test in our office. plugged in an automatic network switch (TPLINK TL-SF1016DS) so I don’t think there is a firewall that is blocking the connection. Power source and internet connection are stable. I really don’t know what to do next.
attached are the logs for your reference
RSH.RE7F4.2024-08-06T02_05_29.logs.tar (839 KB)
RSH.R050E.2024-08-06T02_05_35.logs.tar (553.5 KB)
1 Like
Hello waw0102,
Thank you for posting both Shakes’ logs, they were very helpful.
It seems that the issue it to be found in the fact that the ports required to communicate with our servers are not responding properly:
=== Shake Data Server ===
Name: raspberryshakedata.com
/usr/local/bin/myShake: line 396: NO: command not found
Port 55555 :
/usr/local/bin/myShake: line 396: NO: command not found
Port 55556 :
From your office location, could you SSH (if needed, instructions on how to do so can be found here: Please read before posting!) into the Shake and execute these commands for me?
ping -c 5 8.8.8.8
ping -c 5 144.91.66.87
nc -zvw5 144.91.66.87 55555
nc -zvw5 144.91.66.87 55556
And also:
traceroute 8.8.8.8
traceroute 144.91.66.87
And post their output here? Thank you!
Hi,
Thank you for your swift response. ill attach the output here. Hopefully we can find a solution from this.
RE7F4.txt (3.8 KB)
R050E.txt (3.7 KB)
2 Likes
Hello again waw0102, and thank you so much for both text files.
We can clearly see that, while the Shake is fully able to dialog with the Google IP (8.8.8.8
), it cannot communicate with our server (144.91.66.87
).
Both ports 55555
and 55556
time out, so they need to be opened in your office firewall (by your IT manager, maybe) so that the Shake can “see” and transmit data to us.
If your IT manager requires it, this is the complete list of ports that need to be open: Firewall issues?
Also, on some occasions (as office/school networks have stricter firewall rules in place), it has been necessary to add the Shake IP and MAC address to the firewall exceptions, too.