Mailcow Unable to Retrieve Server IPv6 Address #5859
Comments
7zx
changed the title
|
You need run |
|
Did you tried running |
Regarding the output from the commands: IPv6 NAT was recommended during after i first ran the The I have also executed the |
Em... you have working IPv6, at least from container... Did you tried send mail to gmail and check over which IP you would receive it? Also what you see in ACME? Do ACME container detect IPv6 properly? I see that you accepting connection over IPv6 without issues... |
|
|
I mean acme logs, and about postfix: you sure you not set stuff like prefer ipv4 etc? I don't see any reason why you have it not working as it already works even in inside container |
Because this is a bug and it should be reported? I've also included the ACME logs above... While the service is functional, the intention is for it to display my IPv4 and IPv6 on the Mailcow UI and operate with both IPv4 and IPv6 since both are enabled on my server and set on my DNS records and currently, this isn't fully reflected, which is why I'm trying to find out why this is happening. Here are my ACME logs again:
|
|
Did you tried to reproduce same cli commands I referred couple of comments ago? local IPV6=
local IPV6_SRCS=
local TRY=
IPV6_SRCS[0]="ip6.mailcow.email"
IPV6_SRCS[1]="ip6.nevondo.com"
until [[ ! -z ${IPV6} ]] || [[ ${TRY} -ge 10 ]]; do
IPV6=$(curl --connect-timeout 3 -m 10 -L6s ${IPV6_SRCS[$RANDOM % ${#IPV6_SRCS[@]} ]} | grep "^\([0-9a-fA-F]\{0,4\}:\)\{1,7\}[0-9a-fA-F]\{0,4\}$")
[[ ! -z ${TRY} ]] && sleep 1
TRY=$((TRY+1))
done
echo ${IPV6} |
|
What command? Isn't this from: |
|
Btw 2gb and 1 core? Sorry but you need expect ooms very strongly |
How is this related to my IPv6 issue 😂? Also regarding the server specs, I receive and send over 100 emails daily without encountering any issues. The server operates smoothly despite running on 2GB RAM and 1 core. |
It's not related. But any separate software from bunch mailcow contains by itself easily can consume all your ram, especially dovecot, rspamd, not speaking about clamav. About your issue with ipv6 you still not tried what I asked or not provided details? |
|
I didn’t understand what you want me to do, can you reformulate? |
|
Just run commands one by one from function that get ipv6 in acme.sh, aka debug. On host and in container |
|
|
What you have when doing just basic |
timeout outside and inside the acme container |
Then this totally explains why mailcow can't detect IP. Did you contacted your ISP about that you can't reach this resources? |
dragoangel
added
help-wanted
support
|
THIS IS A AUTOMATED MESSAGE! It seems your issue is not a bug. You can get support either by:
This issue will be closed. If you think your reported issue is not a support case feel free to comment above and if so the issue will reopened. |
|
ups :D anyway, it's really not a place to discuss network connectivity issues. You need get this ips working. @DerLinkman is there is a chance that somebody could be banned on firewall etc in front of this resources? I think - no |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
milkmaker
added
the
stale
Contribution guidelines
I've found a bug and checked that ...
Description
Logs:
Steps to reproduce:
Which branch are you using?
master
Which architecture are you using?
x86
Operating System:
Debian GNU/Linux 11 (bullseye)
Server/VM specifications:
2 GB RAM DDR4, 1 vCPU @3,60Ghz
Is Apparmor, SELinux or similar active?
AppArmor is active
Virtualization technology:
KVM
Docker version:
26.1.0
docker-compose version or docker compose version:
v2.26.1
mailcow version:
2024-04
Reverse proxy:
Nginx
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check:
Additional Information:
mailcow/acme container logs:
curl –connect-timeout 3 -m 10 -L6s ip6.mailcow.email command output on the server:
curl –connect-timeout 3 -m 10 -L6s ip6.mailcow.email command output inside the mailcow/acme container:
Native IPv6 NAT status:
Cloudflare DNS records:
Hosting Provider:
Innov4Web
Reverse DNS status:
Hostname and IPv4/IPv6 addresses associated with my Mailcow server:
Mailcow UI:
Notes:
All of this is being done on a fresh installation of Debian 11.
My hosting provider, Innov4Web, utilizes SolusVM for server control panel management and IPv6 is enabled on the server:
The text was updated successfully, but these errors were encountered: