Email is not configured properly
-
@dynimighti who is your vps provider ?
Because there is a known issue in cloudron for VPS providers that are using DHCPv6, the lease will not be renewed because the traffic is not allowed on UDP port 546 (client) from port 547 (server) in Cloudron's default ip6tables ruleset. Based on RFC 8415 , this port needs to be explicitly opened for DHCPv6 to work correctly.
This issue will lead to PTR6 value = null ... simply because your ipv6 lease is not renewed and so you loose your ipv6...
You can find more information about the issue I'm talking about and a temporary fix here :
https://forum.cloudron.io/topic/13566/infomaniak-ipv6-issues/61?_=1745357068478But if you are using Hetzner it shouldn't be the case because I did some tests and they are setting a fixed ipv6 address. It means you cannot loose your ipv6, so you shouldn't have the issue I'm talking about.
-
@dynimighti who is your vps provider ?
Because there is a known issue in cloudron for VPS providers that are using DHCPv6, the lease will not be renewed because the traffic is not allowed on UDP port 546 (client) from port 547 (server) in Cloudron's default ip6tables ruleset. Based on RFC 8415 , this port needs to be explicitly opened for DHCPv6 to work correctly.
This issue will lead to PTR6 value = null ... simply because your ipv6 lease is not renewed and so you loose your ipv6...
You can find more information about the issue I'm talking about and a temporary fix here :
https://forum.cloudron.io/topic/13566/infomaniak-ipv6-issues/61?_=1745357068478But if you are using Hetzner it shouldn't be the case because I did some tests and they are setting a fixed ipv6 address. It means you cannot loose your ipv6, so you shouldn't have the issue I'm talking about.
-
@dynimighti who is your vps provider ?
Because there is a known issue in cloudron for VPS providers that are using DHCPv6, the lease will not be renewed because the traffic is not allowed on UDP port 546 (client) from port 547 (server) in Cloudron's default ip6tables ruleset. Based on RFC 8415 , this port needs to be explicitly opened for DHCPv6 to work correctly.
This issue will lead to PTR6 value = null ... simply because your ipv6 lease is not renewed and so you loose your ipv6...
You can find more information about the issue I'm talking about and a temporary fix here :
https://forum.cloudron.io/topic/13566/infomaniak-ipv6-issues/61?_=1745357068478But if you are using Hetzner it shouldn't be the case because I did some tests and they are setting a fixed ipv6 address. It means you cannot loose your ipv6, so you shouldn't have the issue I'm talking about.
-
@Gengar linode
@dynimighti okay so if you read the content of your netplan yaml config file you will be able to see if dhcpv6 is enabled . If yes , then you need to use the fix in the link I’ve sent before.
-
@Gengar Hetzner dedicated and virtual
@andreasdueren I only tried with a virtual one at hetzner so idk for the dedicated . But for virtual it’s a fixed IPv6 and I also had my ptr to null one or two times on this one but it’s temporary and very quick. I think it should be a brief interruption with their dns or something network related .
-
@andreasdueren I only tried with a virtual one at hetzner so idk for the dedicated . But for virtual it’s a fixed IPv6 and I also had my ptr to null one or two times on this one but it’s temporary and very quick. I think it should be a brief interruption with their dns or something network related .
@Gengar said in Email is not configured properly:
I think it should be a brief interruption with their dns or something network related .
That's my current guess.
-
This post is deleted!
-
@Gengar think that worked, thanks.
@dynimighti the only issue with the workaround is that you have to reapply it at each reboot of your server …
@nebulon would it be possible to add the firewall rule specified in this post (link below) in cloudron to solve this issue with vps providers using dhcpv6 ?
-
J joseph marked this topic as a question
-
J joseph has marked this topic as solved
-
I had this issue for a long time with Cloudron, with both Hostinger and Hetzner as DNS/NS managers. I just check everytime those issues occur of course but I tend to just not trust anymore any Cloudron notifications for Emails config
