Good day,
I have a raspberryshake that cannot connect to the server using a wifi network from the modem. Previously, shake had successfully connected and streamed for several months to the raspberryshake website, but after I stopped raspberryshake for a few weeks and reconnected to wifi, my shake could not connect to the server. But now I try to ping from SSH to the shake server address:
myshake@raspberryshake:/opt $ ping -c 4 raspberryshakedata.com
4 packets transmitted, 4 received, 0% packet loss, time 6ms
The result is 0% Packet loss.
As additional information, I also have another raspberry connected to the same modem, and this other device can connect to the raspberryshake server and can stream data.
So is the problem with my modem or the raspberryshake device?
Here I attach the log file as a reference.
Best regards,
RSH.RCFEC.2024-10-17T01_30_55.logs.tar (3.3 MB)
1 Like
Hello amsal, and welcome back to the community!
Thank you for the logs, the description of the problem you’re having, and the initial troubleshooting you’ve done.
It appears that, however, the logs are incomplete, so could I please ask you to:
- Shut down the Shake
- Disconnect all cables, wait for 5 minutes
- Reconnect the power cable (as you are connected via WiFi) and turn on the Shake again
- Wait for ~30 minutes, download the logs from the Shake (if needed, instructions here: Please read before posting! ) and attach them to your next answer?
Let’s see if this new set will provide more answers.
Thank you!
Thank you for your kind response.
Here I attach the log file after I run raspberryshake according to your instructions. Thankyou
RSH.RCFEC.2024-10-21T06_17_57.logs.tar (3.4 MB)
1 Like
Here I also attach the results of the ping test to raspberryshake, to ensure whether raspberryshake is connected to the server. Until now the status of my device in rs.local is still not connected to the server
1 Like
Hello amsal,
Thank you for the new logs and the screenshot from the server ping test you have done.
The Shake manages to find a DNS and connect to the network, so the problem may be located with ports that need to be opened on your router.
Can you SSH again into the Shake and execute these commands for me?
nc -zvw5 144.91.66.87 55555nc -zvw5 144.91.66.87 55556traceroute 8.8.8.8traceroute 144.91.66.87
And post their output here? Thank you!
Thank you for your advice, I have attached the test results that I obtained.
Thankyou
1 Like
Here is a display of the port settings that I made on my modem.
1 Like
Thank you again amsal, for all checks.
It seems that, even with the rules in place, the Shake doesn’t manage to connect via the port 55556, as the command output shows.
Let’s try this:
- Turn off the Shake and disconnect it from the router
- Delete the current port rule from the router (only the one for this Shake) and then reboot it
- Once the router has completed the reboot, turn on the Shake again and reconnect it
- Add the rule again (the way you’ve done it now seems correct)
- If required, reboot again the router and then the Shake
Hopefully, the Shake will connect after this operation. If not, can you download the logs and execute these commands again and send them here? Thanks!
nc -zvw5 144.91.66.87 55555nc -zvw5 144.91.66.87 55556
I have turned off my shake and router, but it seems the problem is not solved. I also checked the connection to 5555 and 5556, the results are as shown in the following image:
RSH.RCFEC.2024-10-23T02_14_29.logs.tar (3.5 MB)
I also attach the log file as a reference for root cause search.
Thank you
1 Like
Hello amsal,
Thanks for the new checks and logs that you have done.
It seems that there are still issues with port 55556. Could I please ask you to download the logs from the Shake that is actually working and sending data, so that we can compare the two and see if there is something there?
Hello Storm Chaser,
I checked again today that my raspberryshake has been successfully connected to the server, I only let it walk for a few hours and when I returned I checked again through RS.Local, my shakes have been connected to the internet, even though the custom firewall settings have been deleted beforehand so I Don’t know what happened to my router or on the RaspberryShake server. This is really a strange problem. Here I attach the log file from my device after successfully connected to the RaspberryShake server.
RSH.RCFEC.2024-10-24T01_41_21.logs.tar (3.5 MB)
I have also tried NC on port 55555 and 55556, the results are as follows:
Hello amsal,
I am seeing your Shake transmitting too, so good news!
And yes, it is unusual that you are online now, but the port still seems closed. Could you try executing these two commands?
nc -zvw5 raspberryshakedata.com 55555
nc -zvw5 raspberryshakedata.com 55556
and see what the response is?
This is just for a crosscheck, as I think that the matter has been solved.
I have checked, until now my device can still connect to the raspberry shake server. Here are the results of checking ports 55555 and 55556, I don’t know what happened so that port 55556 can be opened, while the custom firewall settings on my router I have previously deleted.
1 Like
Hello amsal,
Yes, as said, a truly unusual situation. In any case, the Shake is still transmitting data, and I see that the crosscheck has yielded a positive response from our servers.
I am not sure why the router has behaved as we have seen, but everything seems right now.
For anything else, you know where to find us.
Ok, thanks for your help. I will monitor my shake device and router to make sure the data streaming is smooth.
Best regards
2 Likes
