You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
2024/02/28 09:58:47 [error] 382#382: *1621121 srv-captain--xexlabs-siwe-test could not be resolved (3: Host not found), client: 1.146.66.68, server: xexlabs-siwe-test.hosting.ataye.au, request: "GET / HTTP/2.0", host: "xexlabs-siwe-test.hosting.ataye.au"
1.146.66.68 - - [28/Feb/2024:09:58:47 +0000] "xexlabs-siwe-test.hosting.ataye.au" "GET / HTTP/2.0" 502 2577 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36" "-"
Then after the restart i see these:
2024/02/28 09:58:56 [warn] 1#1: protocol options redefined for 0.0.0.0:443 in /etc/nginx/conf.d/captain.conf:127
2024/02/28 09:58:56 [warn] 1#1: protocol options redefined for 0.0.0.0:443 in /etc/nginx/conf.d/captain.conf:127
...
2024/02/28 09:59:03 [warn] 384#384: *1621147 an upstream response is buffered to a temporary file /var/cache/nginx/proxy_temp/3/83/0000000833 while reading upstream, client: 1.146.66.68, server: xexlabs-siwe-test.hosting.ataye.au, request: "GET /main.js HTTP/2.0", upstream: "http://10.0.1.197:80/main.js", host: "xexlabs-siwe-test.hosting.ataye.au", referrer: "https://xexlabs-siwe-test.hosting.ataye.au/"
2024/02/28 09:59:04 1.146.66.68 - - [28/Feb/2024:09:59:04 +0000] "xexlabs-siwe-test.hosting.ataye.au" "GET /main.js HTTP/2.0" 200 1512469 "https://xexlabs-siwe-test.hosting.ataye.au/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36" "-"
If applicable, content of captain-definition file:
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 package.json and captain-definition then deploy with /t and i get the 502 unless i go and hit Save & Restart.
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: