Lost remote access after update

Configuration
,
1

I just updated to core-2021.7.3 and lost remote access. Error log from NGINX below, any ideas?

 [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
 [s6-init] ensuring user provided files have correct perms...exited 0.
 [fix-attrs.d] applying ownership & permissions fixes...
 [fix-attrs.d] done.
 [cont-init.d] executing container initialization scripts...
 [cont-init.d] done.
 [services.d] starting services
 [services.d] done.
 [06:52:22] INFO: Running nginx...
 2021/07/19 06:58:32 [error] 221#221: *1 connect() failed (111: Connection refused) while connecting to upstream, client: xxx.xxx.xxx.xxx, server: xxxxx.duckdns.org, request: "POST /api/webhook/cfbff84be3f62d7890db3b44a3590e07070cfda2cc8cd8787b88aa22 HTTP/2.0", upstream: "http://172.30.32.1:8123/api/webhook/cfbff84be3f62d7890db3b44a3590e07070cfda2cc8cd8787b88aa22", host: "xxxxx.duckdns.org"
 2021/07/19 06:58:32 [error] 221#221: *2 connect() failed (111: Connection refused) while connecting to upstream, client: xxx.xxx.xxx.xxx, server: xxxxx.duckdns.org, request: "POST /api/webhook/cfbff84be3f62d7890db3b44a3590e07070cfda2cc8cd8787b88aa22 HTTP/2.0", upstream: "http://172.30.32.1:8123/api/webhook/cfbff84be3f62d7890db3b44a3590e07070cfda2cc8cd8787b88aa22", host: "xxxxx.duckdns.org"
 2021/07/19 06:58:38 [error] 221#221: *5 connect() failed (111: Connection refused) while connecting to upstream, client: xxx.xxx.xxx.xxx, server: xxxxx.duckdns.org, request: "POST /api/webhook/cfbff84be3f62d7890db3b44a3590e07070cfda2cc8cd8787b88aa22 HTTP/2.0", upstream: "http://172.30.32.1:8123/api/webhook/cfbff84be3f62d7890db3b44a3590e07070cfda2cc8cd8787b88aa22", host: "xxxxx.duckdns.org"
2

Have you read about breaking changes regarding reverse proxy in 2021.7?

You need to add this line to your configuration.yaml-

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.30.33.0/24  # Add the IP address of the proxy server

For the trusted_proxies IP, you should see an error in the log. Then, you input those value to configuration.yaml.

3

Thanks for the quick reply, worked great! To be honest, I didn’t read the breaking changes on this one, but I will remember to do this from now on! Remote access is back! So… dumb question here… in the future, how do I know the address of the proxy server? This IP is not on my network anywhere.

4

Glad it worked out :slight_smile: To answer your question, you may want to read this- (first post made by the author).

5

Thanks again, added to my notes!