netavark aardvark-dns port 53 on a VPS

[Weylon69]

I've read through the discussions here and elsewhere about failing to bind to port 53, but nothing I've found has led me to a resolution for my case. I've got a VPS on HostGator and they provision everything with cPanel, which obfuscates so much it drives me crazy. I have a WordPress site with SSL, and I can see that it's using nginx and Apache. I had Freescout working via my own podman install, then saw that HG offered it through Softaculous in cPanel, and I figured I may as well scrap my installation and see if I get anything more using their canned package. Now Freescout works fine, but I can't get Vaultwarden back.

I don't think is should try to use the cPanel controlled nginx to proxy the ports for Vaultwarden, or anything cPanel for that matter. I'd prefer to have my container as independent from the HG / cPanel stuff. SO.. this is my compose.yml and the error:

vaultwarden:
image: vaultwarden/server:latest
container_name: vaultwarden
restart: unless-stopped
environment:
DOMAIN: "https://mysitethatwork.xyz"
volumes:
- ./vw-data/:/data/
ports:
- 3575:80

podman-compose up -d
podman-compose version: 1.0.6
['podman', '--version', '']
using podman version: 5.2.2
** excluding: set()
['podman', 'ps', '--filter', 'label=io.podman.compose.project=vaultwarden', '-a', '--format', '{{ index .Labels "io.podman.compose.config-hash"}}']
['podman', 'network', 'exists', 'vaultwarden_default']
podman run --name=vaultwarden -d --label io.podman.compose.config-hash=ac92e595cbdca76dbddf62b1e373c1745b09124abaf25c1f34c4e1cb74110875 --label io.podman.compose.project=vaultwarden --label io.podman.compose.version=1.0.6 --label PODMAN_SYSTEMD_UNIT=podman-compose@vaultwarden.service --label com.docker.compose.project=vaultwarden --label com.docker.compose.project.working_dir=/root/docker/vaultwarden --label com.docker.compose.project.config_files=compose.yml --label com.docker.compose.container-number=1 --label com.docker.compose.service=vaultwarden -e DOMAIN=https://mysitethatwork.xyz -v /root/docker/vaultwarden/vw-data:/data/ --net vaultwarden_default --network-alias vaultwarden -p 3575:80 --restart unless-stopped vaultwarden/server:latest

Error: netavark: IO error: Error while applying dns entries: IO error: aardvark-dns failed to start: Error from child process
Error starting server failed to bind udp listener on 10.89.4.1:53: IO error: Address already in use (os error 98)
exit code: 126

podman start vaultwarden
**[WARN netavark::dns::aardvark] Failed to delete aardvark-dns entries after failed start: IO error: aardvark-dns failed to start: Error from child process

Error: unable to start container "c48d7fd64280747b9433ac2660555c0984110c909722f743ccf814faba869405": netavark: IO error: Error while applying dns entries: IO error: aardvark-dns failed to start: Error from child process

Error starting server failed to bind udp listener on 10.89.4.1:53: IO error: Address already in use (os error 98)
exit code: 125**

So how ignorant am I? Is there a simple entry I need in my compose file? Do I need to set up a separate network container and reference that for Vaultwarden?

...and this is what's serving up dns:

lsof -i :53 -n -P

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
pdns_serv 3055834 named 5u IPv4 16179595 0t0 UDP *:53
pdns_serv 3055834 named 6u IPv6 16179596 0t0 UDP *:53
pdns_serv 3055834 named 7u IPv4 16179597 0t0 TCP *:53 (LISTEN)
pdns_serv 3055834 named 8u IPv6 16179598 0t0 TCP *:53 (LISTEN)
]#
]#

psg pdns_serv

named 3055834 1 0 Jan01 ? 00:00:11 /usr/sbin/pdns_server --guardian=no --daemon=no --disable-syslog --log-timestamp=no --write-pid=no

Any help greatly appreciated, and any abuse will be taken in stride ;-)

[stefan0xC]

Can you maybe enclose your config files, commands and outputs with ``` so the formatting is preserved and your question becomes more legible?

If I look up the error message it seems more like a podman issue. Cf. containers/aardvark-dns#535 - Sorry, I am not sure if we can help you troubleshoot the issue if that's the case.

[Weylon69]

I saw that thread too, but I'm not trying to create a network. Vaultman was working before someone at HG dicked with nameservers and hostname when we transferred a domain to the server.