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
Describe the bug
NGINX cannot find server upstream because the container name is not named like that.
** Logs **
nginx: [emerg] host not found in upstream "server" in /etc/nginx/conf.d/default.conf:12
To Reproduce
Steps to reproduce the behavior:
Set the server container_name in the compose file to anything else other than server
Start the compose file
Proxy crashes
NOTES:
The NGINX config should not point to a hardcoded name of the server upstream, but instead depend on an env var or something like that.
I understand that everyone can set up their own proxy and overall most people will do it that way, but you can't just depend on people calling the ssm server plain server either. It's too much of a generic name.
The text was updated successfully, but these errors were encountered:
Hi @rojosinalma . Thanks for the feedback, giving user flexibility through ENV vars is well in my mind, and planned in the near future. Feel free If you can to open a PR to speedup the process :-)
Regards
Describe the bug
NGINX cannot find
server
upstream because the container name is not named like that.** Logs **
To Reproduce
Steps to reproduce the behavior:
container_name
in the compose file to anything else other thanserver
NOTES:
The NGINX config should not point to a hardcoded name of the server upstream, but instead depend on an env var or something like that.
I understand that everyone can set up their own proxy and overall most people will do it that way, but you can't just depend on people calling the ssm server plain
server
either. It's too much of a generic name.The text was updated successfully, but these errors were encountered: