Cannot Access rs.local or Web Interface Despite Device Showing on Network

[pakkapong]

Hi Richard,

Thank you very much for your continued support — I really appreciate your help.

I would like to provide an update regarding my RS units.

For the unit that originally had the issue, I attempted the docker-rebuild method, but it reported a corrupted SD card (left screenshot). So I replaced it with a new micro-SD card and re-burned the image. After that, the unit is now working normally. Thank you again.

However, I still have a few other units experiencing the same problem:

• They appear online in Swarm
• SSH access works normally
• But the local web interface cannot be accessed

I tried running docker-rebuild and also rebooting the units, but the issue persists on those devices. (right screenshot)

Following your most recent update about the V21 updater, I rebooted the units as recommended, but unfortunately the problem is still not resolved.

I have attached logs.tar and upgrade.log from one of the units that continues to show this behavior.

Thank you again for your time and assistance — it is greatly appreciated.

Best regards
logs.tar.bz2 (219.8 KB)

upgrade.log (71.9 KB)

[ivor]

hello pakkapong,

thanks for the logs. for this particular unit, RB3F6, everything appears to be okay.

can you give me some additional details of what you are seeing, (or not, as it were)?

1. what is displayed in the browsers tab title?
2. what exactly is displayed in the browser’s tab?

maybe easiest to answer those questions with a pared down screenshot…

and:

1. do you see anything displayed in the browser’s dev tools window? F12 -> Console Tab

one additional piece of info:

1. log in to the shake
2. run the program /usr/local/bin/myShake on the command line
3. copy the file /opt/log/myshake.out and attach it here

thanks in advance,
richard

[pakkapong]

Hi Richard,
Thank you again for your help.

Here is the additional information for unit RB3F6:

1. Browser tab title

• When opening 192.168.10.34 → the tab shows “192.168.10.34”.
• When opening rs.local → the tab shows only “rs.local”.

2. What is displayed in the browser page

• 192.168.10.34 shows: “This site can’t be reached – ERR_CONNECTION_REFUSED”.
• rs.local shows a completely blank white page.

3. Browser Dev Tools (F12 → Console)

• rs.local displays:
  Failed to load resource: net::ERR_CONNECTION_RESET (bundle.js, main.css, Roboto-Regular.ttf)
• 192.168.10.34 shows nothing in the console because the request is refused immediately.

4. myshake.out
   I logged into the Shake, ran:
   sudo /usr/local/bin/myShake
   and attached the file /opt/log/myshake.out here as requested.

If you need more logs or want me to test anything else on this unit (or the others with the same issue), please let me know.
Thank you again for your time and support.

Best regards,

myshake.out (10.4 KB)

[ivor]

thanks for the additional info.

one more test to try:

1. on the command line, issue the commands:

    > ping auth.raspberryshake.org
    > sudo systemctl restart rsh-fe-config

we have very recently identified a race condition bug on FE startup we are working to fix: on FE startup, if the DNS server is not yet available, the FE ends up in a non-working state. a later restart of the app fixes the problem since the DNS service has come to be available in the meantime. this is a temporary fix until the patched version is rolled out, in the near future.

please let me know if the output of the ping command, and if the FE becomes active after the service restart command.

thanks in advance,
richard

[FlyingMoose]

@ivor

> ping auth.raspberryshake.org
> sudo systemctl restart rsh-fe-config

I am having the same problem. The above fixed it. I have frequent power failures so it may happen again.

[ivor]

hello FlyingMoose,

thanks for the report, this is appreciated.

the cause of this problem is understood and resolved. a patch release will be applied very soon that will fix this permanently.

apologies for the inconvenience.

cheers,
richard

[Ixioides]

I’m having the same problem, I got a notification this morning that my station was offline which (presumably) was the update, a reboot fixed it but the web interface isn’t functioning. Everything else is working OK, I can SSH in, reboot, restart services, etc as above, only the web interface isn’t working, or even running: ECONNREFUSED.

[Ixioides]

Just checked back today and it seems to have fixed itself in the meantime.

[Stormchaser]

Hello Ixioides, and welcome back to the community!

Thank you for your report and feedback. Our team has identified the issue causing this, and we will release a patch to the latest v21 version to fix it.

We’ll also announce it on the forum as usual.

Thank you again!