I am having the same issue as this one that unfortunately got closed without been evident a determinist solution based the fact that a VM is not a dedicated server and that apparetly to many the “build” goes well the tutor local status show everything is running but in the end the frontend website apparently is not serve or reachable.
Actually from this one seems as I also have that the verhangio/openedx-permissions:17.0.6 container is the one that could got some issue.
–> overhangio/openedx-permissions:17.0.6 “sh /usr/local/bin/s…” 6 hours ago Exited (0) 8 minutes ago
The thing is that this build do success on a WSL with tutor dev, do success on a WSL with tutor local but fail, exact same code and procedure on a VM.
Tutor on development or testing if developed feature or custom them do work also on local as in dev smooth before the full release in production.
That issue is very similar; it’s usually caused by local DNS/hosts resolution or Tutor’s web proxy not exposing local.edly.io correctly.
Can you share what exactly you’ve tried so far and a bit more about your setup (OS, Tutor version, how you edited your hosts file, and what docker compose ps shows)? That’ll make it easier to pinpoint what’s going wrong.
