Welcome! Log In Create A New Profile

Advanced

resolver does not work

Anonymous User
April 18, 2023 09:00AM
Hello,
I have a nginx proxy in front of systemd-nspawn containers.
The IP's of the containers are dynamic.

When I start nginx *after* the  containers it works.
When the IP of the container is changed while nginx is running i get a
"Bad Gateway" error.

The config looks like:

server {
    server_name foobar.example.com
...
   location / {
      resolver 127.0.0.53 valid=10s;
      ...
      proxy_pass http://container;
   }
}

nginx is 1.1.18 so it should work as documented in
http://nginx.org/en/docs/http/ngx_http_core_module.html#resolver
The workaround there
https://stackoverflow.com/questions/42720618/docker-nginx-stopped-emerg-11-host-not-found-in-upstream/52319161#52319161
doesn't work.

I have also try to config a upstream backend and the resolver in the
server part or in the http part.
The errors are: "upstream timed out" or "container could not be resolved
(3: Host not found)"

Whats wrong there?
Best Regards
_______________________________________________
nginx mailing list
nginx@nginx.org
https://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

resolver does not work

Anonymous User April 18, 2023 09:00AM

Re: resolver does not work

A. Schulze via nginx April 18, 2023 01:24PM

Re: resolver does not work

basti April 18, 2023 03:06PM

Re: resolver does not work

Maxim Dounin April 18, 2023 03:30PM

Re: resolver does not work

basti April 18, 2023 04:26PM

Re: resolver does not work

Maxim Dounin April 18, 2023 08:52PM

Re: resolver does not work

basti April 19, 2023 06:30AM

Re: resolver does not work

J Carter April 18, 2023 03:32PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 71
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready