Fatal Unable to initialize iptables on host lookup coredns o

Question

Fatal Unable to initialize iptables on host lookup coredns on 161 97 189 51 port 53 no such host

creamy-judge-86664 · Answer

Hi I redeployed netmaker on my server and now I get the following error As a note that is not my public IP

jolly-london-20127 · Answer

how did you deploy with docker compose

creamy-judge-86664 · Answer

Yes the traefik based config

creamy-judge-86664 · Answer

and modified to use host network on the netmaker container

jolly-london-20127 · Answer

ok that s likely the issue then It attempts to look up the coredns container to forward traffic You need to turn that bit off Make sure PORT FORWARD SERVICES=

creamy-judge-86664 · Answer

great

jolly-london-20127 · Answer

you may also want to turn MANAGE IPTABLE=off

creamy-judge-86664 · Answer

it is working

creamy-judge-86664 · Answer

but now I get this in traefik ``` time= 2022 06 16T15 25 43Z level=info msg= Configuration loaded from flags time= 2022 06 16T15 25 44Z level=error msg= entryPoint websecure doesn t exist routerName=netmaker ui docker entryPointName=websecure time= 2022 06 16T15 25 44Z level=error msg= no valid entryPoint for this router routerName=netmaker ui docker time= 2022 06 16T15 25 44Z level=error msg= entryPoint websecure doesn t exist entryPointName=websecure routerName=netmaker api docker time= 2022 06 16T15 25 44Z level=error msg= no valid entryPoint for this router routerName=netmaker api docker time= 2022 06 16T15 25 44Z level=error msg= entryPoint websecure doesn t exist routerName=mqtts docker entryPointName=websecure time= 2022 06 16T15 25 44Z level=error msg= no valid entryPoint for this router routerName=mqtts docker ```

creamy-judge-86664 · Answer

With the following traefik config and netmaker they are in different files due to issues with other services