Make sure it hasn't crashed and it's running. SSH to your server and view your application logs.If all above points are correct, this is how to troubleshoot: You tried to deploy your own application and it deployed successfully, but when you try to access it via you get a 502 error.You have been able to deploy one of the samples apps (see here) successfully and it worked.You have been able to setup your server and access it via.Successful Deploy but 502 bad gateway error!

If successful, it's probably your firewall that's blocking the connection. If both 'First' and 'Second' debugging steps explained above worked fine and there is no error seen in the logs, run this command on your server: curl localhost:3000 -v Search CapRover Github issues for your problem and if you can't find a solution, create a new issue on Github. You might see that CapRover is getting restarted constantly due to an error. If you don't see any errors when your ran docker service ps captain-captain -no-trunc, then try docker service logs captain-captain -since 60m Linode, for example, has many problems, such as subnet sandbox join failed and vxlan interface.

For example, see error creating vxlan interface, or error while creating mount source path. You might see Captain is getting restarted constantly due to an error.

To check this, ssh to your server and run docker service ps captain-captain -no-trunc You need to make sure that CapRover is running on your server. There is a whole set of reasons for this. This section covers most frequent issues that users may encounter.

Docker adguard