In this article
Use this article to troubleshoot Relay deployment for common errors and steps to view Relay logs.
Deployment error message troubleshooting
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, contains a formatting error, or unable to be accessed due to permission issues.
How to fix it. Ensure that relay.conf exists in the current working directory, matches the correct format, and is accessible by the Docker Daemon.
Invalid organization or network secret key
What we know. The Site Secret Key (SSK) entered into the relay.conf file is invalid.
How to fix it. Replace the value with the accurate SSK.
View Relay Logs
Relay logs are useful for our Support team when assisting with troubleshooting. DNS Relays installed using binary and the in-app generated config file run a command window that continually print logs.
If you've deployed the Relay with Docker or a VM, use these commands to run diagnostics:
-
sudo docker logs relay1
andsudo docker logs relay2
to view the logs -
sudo docker ps
to see if the relay is running -
sudo docker start relay1 relay2
to start the relay -
sudo docker restart relay1 relay2
to restart the relay
Comments
0 comments
Please sign in to leave a comment.