Chnaged primary ipv6 on Hetzner and now failing status checks

Help with Setup/Upgrade
1

I have created a new mailinabox server and have migrated my old mailinabox data to the new server. I switched the ipv4 and ipv6 addresses between the old and new server and ipv4 works fine. However, I am getting issues in status check with ipv6. I have changed netplan yaml config to the new ipv6 address and run sudo mailinabox and rebooted. Not sure what else to do?

Public DNS (nsd4) is running and available over IPv4 but is not accessible over IPv6 at 2a01:4f9:c011:5a66::1 port 53.
:heavy_multiplication_x: Incoming Mail (SMTP/postfix) is running (and available over IPv4 and the local IPv6 address), but it is not publicly accessible at 2a01:4f9:c011:5a66::1:25.
:heavy_multiplication_x: Outgoing Mail (SMTP 465/postfix) is running (and available over IPv4 and the local IPv6 address), but it is not publicly accessible at 2a01:4f9:c011:5a66::1:465.
:heavy_multiplication_x: Outgoing Mail (SMTP 587/postfix) is running (and available over IPv4 and the local IPv6 address), but it is not publicly accessible at 2a01:4f9:c011:5a66::1:587.
:heavy_multiplication_x: IMAPS (dovecot) is running (and available over IPv4 and the local IPv6 address), but it is not publicly accessible at 2a01:4f9:c011:5a66::1:993.
:heavy_multiplication_x: Mail Filters (Sieve/dovecot) is running (and available over IPv4 and the local IPv6 address), but it is not publicly accessible at 2a01:4f9:c011:5a66::1:4190.
:heavy_multiplication_x: HTTP Web (nginx) is running (and available over IPv4 and the local IPv6 address), but it is not publicly accessible at 2a01:4f9:c011:5a66::1:80.

show more
:heavy_multiplication_x: HTTPS Web (nginx) is running (and available over IPv4 and the local IPv6 address), but it is not publicly accessible at 2a01:4f9:c011:5a66::1:443.

I am using the same Hetzner firewall rules for the new server and old server.

2

Should private_ipv6 be blank in mailinabox.conf?

PUBLIC_IP=95.217.237.156
PUBLIC_IPV6=2a01:4f9:c011:5a66::1
PRIVATE_IP=95.217.237.156
PRIVATE_IPV6=
3

It shouldn’t. If it is empty, your box won’t be configured correctly for ipv6.

If the setup stores the private ipv6 ad empty, check the following command:
ip -6 -o route get 2001:4860:4860::8888
This is what the setup uses to determine the private ip address.