Replies: 3 comments 5 replies
|
Hello @Dev-sh21 |
0 replies
|
Have you followed the developer guide or the user guide? |
3 replies
|
hi @jmplaza @javizqh
I will submit the pr shortly for your review |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi @jmplaza @javizqh ,
I'm setting up Robotics Academy locally on my Mac (M1/M2) using Docker, and I've been running into an issue where the application verifies application_running but the frontend stays stuck on the "Connecting..." dialog indefinitely.
Symptoms:
The container starts and is healthy (docker ps shows it up).
The web interface loads (localhost:7164).
WebSockets connect initially but then seem to drop or fail to establish the VNC stream.
Findings: After digging into the logs and the container, I suspect this might be a timeout issue specific to emulated environments (Rosetta/QEMU on ARM64).
The vnc_server.py script has a hardcoded timeout of 20 seconds for the VNC port to become available: def wait_for_port(self, host, port, timeout=20):
On my machine, due to emulation overhead, the Xorg/TurboVNC server takes about 30-40 seconds to initialize. This causes the Manager to raise a TimeoutError and exit silently before the frontend can fully connect.
Has anyone else on Apple Silicon experienced this? Should we consider increasing this default timeout to accommodate non-native Docker setups? I'd be happy to open a PR if this is a valid improvement.
Thanks!

All reactions