Are you using rs.local to connect to your shake? If not, device IPs might have inadvertently changed and you are now trying to connect to a different device than your shake.
Besides that, I am not entirely sure what could cause the access denied error. Burning your SD card with a fresh image might be the easiest fool-proof solution here.
Seems like there is a static IP address configured and the trailing slash seems like a typo of sorts.
Could you disable the static IP in the rs.local config screen and also clear the DNS Server entry and then Save and reboot. This is the screen you need:
No sorry, that was a previous email where I had fixed a different error. I am still on the verge of giving up! I want so badly to have this work, but it sure has been a time suck.
For your suggestions below:
The static IP has always been set to âoff.â
The Shake is already plugged directly into the router.
Your dhcpcd.conf does indicate a static IP setting, as to how it got that way I donât know. But it is highly likely itâs the reason behind your connection issues.
Remove all the static lines from the dhcpcd.conf ( static ip_address=..., static routers=, ⌠) and put in this line: interface eth0
Restart your shake and let it retrieve its new network settings through DHCP. This should solve your connection issues.
once you have adjusted the files to use a DHCP address returned by the router, please resend the log files. without them, we are unable to see the effects the changes had (or not).
Iâve found that setting the static IP address doesnât work through the UI, especially if you make a mistake the first time. I had to delete the old entries in the files, and edit them directly. That solved my problem.
Thank you for the help! The unit is now plugged into the ethernet-over-powerline adapter, and still working.
My final remaining question â my station still shows as offline on the app on my iPhone. Are you able to confirm if you can see the station online on an iphone?
i can see your station fine in the android app. try to go to Settings screen and do a âclear cacheâ and see if that doesnât help. another option is to uninstall and reinstall the app. weâve gotten a couple of reports that new stations sometimes donât initially appear in the mobile app, we are looking into this and will apply a solution when we find where the code needs improving.