In this article

Use this article to troubleshoot Relay deployment for common errors. 

Listen tcp4 x.x.x.x:53 bind: address already in use

What we know. This error occurs when starting userland proxy. By default, most modern Linux distributions run a DNS daemon out of the box that may prevent the Relay from starting: it is unable to bind to port 53 due to the existing bound daemon.  

How to fix it. Disable the running DNS daemon on the host device or adjust the relay.conf file to direct the binary or container to listen on a different port. 

Post https://api.dnsfilter[...] lookup api.dnsfilter.com: Try Again

What we know. If the DNS daemon is disabled due to the issue above and now returns an error, there's a chance that the host device does not have an external DNS server set and cannot resolve the api.dnsfilter.com hostname.

How to fix it. Add an external DNS server such as 8.8.8.8 or 9.9.9.9 to the system per the distribution instructions to resolve the issue.

Not a valid TOML config file / open /go/bin/lan-proxy.conf: no such file or directory

What we know. This is a strong indication that the file expected to be found at ./relay.conf (where ./ is the same directory of the docker-compose.yml file) is either not there, named incorrectly, or unable to be accessed due to permission issues.

How to fix it. Ensure that relay.conf exists in the current working directory and is accessible by the Docker Daemon.