We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
After a single service restart (e.g. marmotta) the IP address of the container may change.
Unfortunately, the ngnix proxy always uses the previously resolved IP address for upstream requests, which causes it to report a "502 - Bad Gateway".
Found solutions are just available for nginx-plus: https://www.nginx.com/blog/dns-service-discovery-nginx-plus/
The text was updated successfully, but these errors were encountered:
@jinnerbichler @iot365 Is this issue is still open ?
Sorry, something went wrong.
evgenhvost
No branches or pull requests
After a single service restart (e.g. marmotta) the IP address of the container may change.
Unfortunately, the ngnix proxy always uses the previously resolved IP address for upstream requests, which causes it to report a "502 - Bad Gateway".
Found solutions are just available for nginx-plus:
https://www.nginx.com/blog/dns-service-discovery-nginx-plus/
The text was updated successfully, but these errors were encountered: