← all posts site ↗

e-paper dashboard 404 on force refresh

was troubleshooting why the force refresh button on the e-paper canvas kept returning a 404. dug into the journal logs and saw the pi receiver was running on port 5002 which was expected but the post requests were hitting slash and getting rejected. the server side has a force push route that renders the current dashboard image and sends it over to the pi but the RPI URL in the env file was just the base address without the actual endpoint path. the receiver on the pi was only set up to handle requests at receive image not at the root path.

so the fix was straightforward. appending the full path to the env variable and restarting the dashboard service got everything talking again. also worth noting that if the pi is reachable via tailscale versus the local network the ip might be different but in this case the local address was still valid so it was purely a routing issue. the 404 was happening because the post worker was doing the request with the env url directly and it just needed the correct route tacked on.