Sorry, wrong traceback copypaste. Right one:
8844ce6e22f6:/# traceroute google.com
traceroute to google.com (142.251.1.102), 30 hops max, 46 byte packets
1 172.22.1.1 (172.22.1.1) 0.006 ms 0.013 ms 0.006 ms
2 * * *Ddaenbol
- Jul 22, 2024
- Joined Jun 27, 2024
- 1 discussion
- 3 posts
- 0 best answers
- Post posted... wait what?
- Edited
Here is my healthcheck.log
8844ce6e22f6:/# cat /var/log/healthcheck.log 2024-06-28 11:22:37: Please check your internet connection or firewall rules to fix this error, because a simple ping test should always go through from the unbound container! 8844ce6e22f6:/# ping 1.1.1.1I know that this problem is setup specific but I’m installing mailcow on a fresh new Alpine without firewall. I’m ready to cooperate and trace packages. Please help.
Here is my traceroute from unbound container:
8844ce6e22f6:/# cat /var/log/healthcheck.log 2024-06-28 11:22:37: Please check your internet connection or firewall rules to fix this error, because a simple ping test should always go through from the unbound container! 8844ce6e22f6:/# ping 1.1.1.1I’m trying to get mailcow work with default settings on a fresh alpine (aarch64) with no firewall (iptables and nftables only), but there is some network issue.
My issue is similar to the following
problem: mailcow community
curl: (7) Failed to connect to “www.internic.net” port 443 after 3216 ms: Couldn’t connect to server.I was not able to bypass this by disabling ipv6.curl -vo /tmp/root.hints https://www.internic.net/domain/named.cache
works from host but not from unbound containerPorts seem to be closed for an outer computer in LAN:
View paste YVYA bpa.st
My ip a from unbound container:
View paste AYAQ bpa.stHere is ps aux | grep docker-proxy:
View paste D55A bpa.stSeems like the problem is related to docker-proxy setup