Failed to establish a new connection: [Errno -3] Temporary failure in name resolution

Help
7

@rg305
You are great, thank you very much. It works if I set the nameserver to my router or directly to a public DNS server.
On startup the getaddrinfo error is now gone and certificates can be created.

[1/27/2022] [10:02:55 AM] [Global   ] › ℹ  info      No valid environment variables for database provided, using default SQLite file '/data/database.sqlite'
[1/27/2022] [10:02:57 AM] [Migrate  ] › ℹ  info      Current database version: none
[1/27/2022] [10:02:57 AM] [Setup    ] › ℹ  info      Logrotate Timer initialized
[1/27/2022] [10:02:57 AM] [Setup    ] › ℹ  info      Logrotate completed.
[1/27/2022] [10:02:57 AM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
[1/27/2022] [10:02:57 AM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[1/27/2022] [10:02:59 AM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
[1/27/2022] [10:02:59 AM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
[1/27/2022] [10:02:59 AM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
[1/27/2022] [10:02:59 AM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
[1/27/2022] [10:02:59 AM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
[1/27/2022] [10:02:59 AM] [Global   ] › ℹ  info      Backend PID 246 listening on port 3000 ...
QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0
QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. eager` method will be removed in 3.0
QueryBuilder#omit is deprecated. This method will be removed in version 3.0
Model#$omit is deprected and will be removed in 3.0.
[1/27/2022] [10:03:03 AM] [Nginx    ] › ℹ  info      Reloading Nginx
[1/27/2022] [10:03:03 AM] [SSL      ] › ℹ  info      Renew Complete

This is really great now that I can move the proxy server from the NAS to the Raspberry.

But I still don't understand the issue.
Why does it work on the NAS server which also has "only" 192.168.1.2 (Pi-hole/Unbound) as DNS server but not directly on the Pi (192.168.1.2)? This is not clear to me yet. Does this make sense?

1 Like