Disabled ipv6, now can't connect to LXCs

[daviid]

I had proxmox up and running but I had problems with a minecraft server.

no matter what I did the debug logs showed

-Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Stack=true

I had already done

net.ipv6.conf.all.disable_ipv6=1
net.ipv6.conf.default.disable_ipv6=1
net.ipv6.conf.lo.disable_ipv6=0
net.ipv6.conf.eth0.disable_ipv6=1

On the LXC but whenever I rebooted ip ashowed a v6 IP.

So I though of disabling it on proxmox too by adding ipv6.disable=1 to the grub.

After rebooting the server I can't access any LXC

david@test:~$ sudo pct list
VMID       Status     Lock         Name
100        running                 alpine
101        running                 jellyfin
102        running                 jellyseerr
103        running                 portainer
104        running                 myspeed
105        running                 radarr-anime
106        running                 sabnzbd
107        running                 minecraft
109        running                 qbittorrent
110        running                 nginxproxymanager
111        running                 homepage
112        running                 wireguard
113        running                 technitiumdns
114        running                 bazarr
115        running                 sonarr-anime
118        running                 grafana
119        running                 prowlarr
121        running                 alpine-docker
122        running                 vaultwarden
123        running                 radarr-normal
125        running                 flaresolverr
126        running                 notifiarr
127        running                 sonarr-normal
128        running                 prometheus
130        running                 bazarr-anime
131        running                 immich
132        running                 navidrome
133        running                 readarr
134        running                 calibre-web

all the LXC are running, I can enter them and check that the services are also running, for example technitiumdns and nginxproxymanager with ips 192.168.2.113 and 192.168.2.110 give me ERR_CONNECTION_REFUSED

root@nginxproxymanager:/# systemctl status npm
● npm.service - Nginx Proxy Manager
     Loaded: loaded (/lib/systemd/system/npm.service; enabled; preset: enabled)
     Active: active (running) since Mon 2024-12-09 15:11:28 CET; 13min ago
    Process: 779 ExecStartPre=mkdir -p /tmp/nginx/body /data/letsencrypt-acme-challenge (code=exited, status=0/SUCCESS)
   Main PID: 780 (node)
      Tasks: 11 (limit: 18844)
     Memory: 63.3M
        CPU: 1.864s
     CGroup: /system.slice/npm.service
             └─780 /usr/bin/node index.js --abort_on_uncaught_exception --max_old_space_size=250

Dec 09 15:11:30 nginxproxymanager node[780]: [12/9/2024] [3:11:30 PM] [Setup    ] › ℹ  info      Logrotate completed.
Dec 09 15:11:30 nginxproxymanager node[780]: [12/9/2024] [3:11:30 PM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
Dec 09 15:11:30 nginxproxymanager node[780]: [12/9/2024] [3:11:30 PM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
Dec 09 15:11:31 nginxproxymanager node[780]: [12/9/2024] [3:11:31 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
Dec 09 15:11:31 nginxproxymanager node[780]: [12/9/2024] [3:11:31 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
Dec 09 15:11:31 nginxproxymanager node[780]: [12/9/2024] [3:11:31 PM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
Dec 09 15:11:31 nginxproxymanager node[780]: [12/9/2024] [3:11:31 PM] [SSL      ] › ℹ  info      Renewing SSL certs expiring within 30 days ...
Dec 09 15:11:31 nginxproxymanager node[780]: [12/9/2024] [3:11:31 PM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
Dec 09 15:11:31 nginxproxymanager node[780]: [12/9/2024] [3:11:31 PM] [Global   ] › ℹ  info      Backend PID 780 listening on port 3000 ...
Dec 09 15:11:31 nginxproxymanager node[780]: [12/9/2024] [3:11:31 PM] [SSL      ] › ℹ  info      Completed SSL cert renew process

root@technitiumdns:/# systemctl status dns
● dns.service - Technitium DNS Server
     Loaded: loaded (/etc/systemd/system/dns.service; enabled; preset: enabled)
     Active: active (running) since Mon 2024-12-09 15:04:16 CET; 21min ago
   Main PID: 99 (dotnet)
      Tasks: 20 (limit: 18844)
     Memory: 153.9M
        CPU: 7.276s
     CGroup: /system.slice/dns.service
             └─99 /usr/bin/dotnet /opt/technitium/dns/DnsServerApp.dll /etc/dns

Dec 09 15:04:16 technitiumdns systemd[1]: Started dns.service - Technitium DNS Server.
Dec 09 15:04:17 technitiumdns dns-server[99]: Technitium DNS Server was started successfully.
Dec 09 15:04:17 technitiumdns dns-server[99]: Using config folder: /etc/dns
Dec 09 15:04:17 technitiumdns dns-server[99]: Note: Open http://technitiumdns:5380/ in web browser to access web console.
Dec 09 15:04:17 technitiumdns dns-server[99]: Press [CTRL + C] to stop...

Edit: Rmoving ipv6.disable=1 makes everything work again

Edit2: found the reason https://forum.proxmox.com/threads/status-update-error-iptables_restore_cmdlist.118247/ I had the same status update error: iptables_restore_cmdlist errors