Hi @Shengjie_Yang! Sometimes 502 Bad Gateway can appear when portal service or other services are not ready yet. Sheepdog and Peregrine services download the dictionary schema at startup, and the portal service runs a series of pre-launch compilations that depend on Sheepdog and Peregrine, so it may take several minutes for the portal to finally come up at https://localhost. You can monitor startup process by following portal logs:
docker logs -f portal-service
If all services started and you still get 502 Bad Gateway error after several minutes, maybe there is additional information in other logs? You can check it with docker logs -f <service-name> for a live log output when you attempt to reach localhost.