Replies: 1 comment
-
|
Unfortunately have never used this provider before so do not know how helpful I can be. Upstream errors however are usually a networking issue, it appears the UI container cannot connect to the API container using the container alias, you may have to associate it by IP instead |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to deploy, but I'm getting an error when deploying the UI container. How can I fix it?
Caprover Container Environment.
Log do errors:
2024-11-01T00:59:59.672599066Z 2024/11/01 00:59:59 [emerg] 1#1: host not found in upstream "api" in /etc/nginx/conf.d/default.conf:11
2024-11-01T00:59:59.672668698Z nginx: [emerg] host not found in upstream "api" in /etc/nginx/conf.d/default.conf:11
2024-11-01T01:00:06.125944529Z 2024/11/01 01:00:06 [emerg] 1#1: host not found in upstream "api" in /etc/nginx/conf.d/default.conf:11
2024-11-01T01:00:06.126011396Z nginx: [emerg] host not found in upstream "api" in /etc/nginx/conf.d/default.conf:11
2024-11-01T01:00:12.369070330Z 2024/11/01 01:00:12 [emerg] 1#1: host not found in upstream "api" in /etc/nginx/conf.d/default.conf:11
2024-11-01T01:00:12.369383296Z nginx: [emerg] host not found in upstream "api" in /etc/nginx/conf.d/default.conf:11
2024-11-01T01:00:18.604779317Z 2024/11/01 01:00:18 [emerg] 1#1: host not found in upstream "api" in /etc/nginx/conf.d/default.conf:11
2024-11-01T01:00:18.604813993Z nginx: [emerg] host not found in upstream "api" in /etc/nginx/conf.d/default.conf:11
Beta Was this translation helpful? Give feedback.
All reactions