New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NGINX 502 every time i deploy a web app using deploy.tar #2021
Comments
Can you please provide an example repository or a tar file that exhibits this behavior? |
It happens with any pretty much any code repo i push. I'll put together a public project and share here. Currently i'm building a react app with a node backend, build the react locally and copy dist into the node server, then archive the node server along with |
All Save & Update does is to restart your app. When you deploy, the same thing happens as well (restart). It's weird that it only happens for you. Can you reproduce the issue with the examples here? Simply just download one of these tar files and deploy. |
What is the problem?
Every time i deploy, i get an nginx 502 error page. I just deployed 2 react apps with a nodejs server that serves the react app. Both build locally and deploy using the deploy.tar method:
caprover deploy -t ./deploy.tar --default
. Both are vite react apps, but it also happens with 1 click apps that have a web interface except i get the blue 502 error page on the first deployment.These particular react apps have a nodejs server back end which also serves the react app. I just tried with a simple static react app to run through the
Steps to reproduce
and had the same issue doing the deployment.I have Dozzle running and monitor the nginx logs, and after the deploy i see these errors:
Then after the restart i see these:
If applicable, content of
captain-definition
file:This is basically what i use for both react apps:
And the static react app:
Steps to reproduce the problem:
caprover deploy -t ./deploy.tar
,NGINX 502 502 :/
,Output of the following command on your server:
The text was updated successfully, but these errors were encountered: