Common problems
Work through Portal access, World connection, Docker and lab startup problems.
Portal does not open
- Confirm Docker is running and inspect the Portal containers with docker ps -a.
- Check the URL and the published host port. localhost refers to the machine running your browser.
- For a remote host, use its configured address and confirm the route and firewall allow access.
- If startup reports a port conflict, identify the existing listener before changing your configuration.
World connection or content is missing
- Open Settings and check the connected account in Connection Info.
- Check Access Info for the intended plan and subscription status.
- Use Refresh Info, or Refresh License on older versions.
- Record any connection error. A lab can also be unavailable because of plan access or learning progress.
A lab or service will not start
- Confirm that the intended environment is loaded in Control.
- Read the operation output: downloading an image is different from starting its application.
- Check free disk space, available memory and the affected container’s logs.
- For image download failures, check the host’s internet connection and access to the registry.
- For a service URL that will not open, check the published port and application readiness.
Collect the logs before trying a reset. Repeatedly recreating containers can hide the first useful error.
