Skip to main content

AlmaLinux 8 (CloudLinux 8), cPanel and IPv6

Radeonpower
Hi everyone, I'm having difficulty getting IPv6 to work on my new AlmaLinux 8 (CloudLinux 8) with cPanel to work. Before I installed cPanel on the server everything worked just fine but after installation of cPanel it does not work anymore. I suspect it's due to the fact that cPanel now disables NetworkManager. Here is my network config (this is a server from Hetzner if it matters): IPV6INIT=yes IPV6ADDR=2a01:xxx:xxx:xxxx::x/64 IPV6_DEFAULTGW=fe80::1 IPV6_DEFROUTE=yes IPV6_AUTOCONF=no IPV6_FAILURE_FATAL=no IPV6_DEFAULTDEV=enp41s0 enp41s0: flags=4163 mtu 1500 inet xx.xx.x.xxx netmask 255.255.255.192 broadcast xx.xx.x.xxx inet6 fe80::aaa1:59ff:fea2:939b prefixlen 64 scopeid 0x20 ether a8:a1:59:a2:xx:xx txqueuelen 1000 (Ethernet) RX packets 1450 bytes 351253 (343.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1145 bytes 305677 (298.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device memory 0xfc200000-fc27ffff lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 2420 bytes 958431 (935.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2420 bytes 958431 (935.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Anyone have an idea for me? :) Thanks!

Comments

14 comments

Date Votes
  • cPRex Jurassic Moderator
    Hey there! I don't have much to add on my end since cPanel doesn't control the network interface, but I'll leave this marked as new for a bit for others to add their experience.
    0
  • AzeDK
    Hey there! I don't have much to add on my end since cPanel doesn't control the network interface, but I'll leave this marked as new for a bit for others to add their experience.

    I got this warning today, how will this affect us, if CPANEL doesn't work with NetworkManager? AlmaLinux 8.6 (Sky Tiger) Jun 24 13:06:11 network[2918]: WARN : [network] You are using 'network' service provided by 'network-scripts', which are now deprecated. Jun 24 13:06:11 network[2918]: WARN : [network] 'network-scripts' will be removed in one of the next major releases of RHEL. Jun 24 13:06:11 network[2918]: WARN : [network] It is advised to switch to 'NetworkManager' instead for network management.
    0
  • AzeDK
    Hi everyone, I'm having difficulty getting IPv6 to work on my new AlmaLinux 8 (CloudLinux 8) with cPanel to work. Before I installed cPanel on the server everything worked just fine but after installation of cPanel it does not work anymore. I suspect it's due to the fact that cPanel now disables NetworkManager. Here is my network config (this is a server from Hetzner if it matters): IPV6INIT=yes IPV6ADDR=2a01:xxx:xxx:xxxx::x/64 IPV6_DEFAULTGW=fe80::1 IPV6_DEFROUTE=yes IPV6_AUTOCONF=no IPV6_FAILURE_FATAL=no IPV6_DEFAULTDEV=enp41s0 enp41s0: flags=4163 mtu 1500 inet xx.xx.x.xxx netmask 255.255.255.192 broadcast xx.xx.x.xxx inet6 fe80::aaa1:59ff:fea2:939b prefixlen 64 scopeid 0x20 ether a8:a1:59:a2:xx:xx txqueuelen 1000 (Ethernet) RX packets 1450 bytes 351253 (343.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1145 bytes 305677 (298.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device memory 0xfc200000-fc27ffff lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 2420 bytes 958431 (935.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2420 bytes 958431 (935.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Anyone have an idea for me? :) Thanks!

    Here is what we use with AlmaLinux 8.6 (Also hetzner) TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=dhcp DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=no IPV6_FAILURE_FATAL=no NAME=enp1s0 UUID=XXXXXXXXXXXX DEVICE=enp1s0 ONBOOT=yes
    0
  • cPRex Jurassic Moderator
    @AzeDK - let me look into that and I'll see what I can find out!
    0
  • cPRex Jurassic Moderator
    Our long-term plan is to eventually support NetworkManager, so this won't be an issue. It's not ready yet, but it'll be ready before anything is officially deprecated by the operating systems themselves.
    0
  • gvard
    Hello, On each Hetzner server we setup with AlmaLinux, after cPanel installation we lose network too. In order to fix connectivity, we do this: IPv4: pico /etc/sysconfig/network-scripts/ifcfg-e* (the network card name) Add: NETMASK=255.255.255.192 service network restart IPv6: pico /etc/sysconfig/network-scripts/ifcfg-e* (the network card name) Add: IPV6_DEFAULTDEV= (followed by the network card name) service network restart
    0
  • AzeDK
    Hello, On each Hetzner server we setup with AlmaLinux, after cPanel installation we lose network too. In order to fix connectivity, we do this: IPv4: pico /etc/sysconfig/network-scripts/ifcfg-e* (the network card name) Add: NETMASK=255.255.255.192 service network restart IPv6: pico /etc/sysconfig/network-scripts/ifcfg-e* (the network card name) Add: IPV6_DEFAULTDEV= (followed by the network card name) service network restart

    Is it a dedicated root server or their cloud server?
    0
  • gvard
    I'm talking about dedicated servers. We've already contacted them regarding this, I hope if more people let them know they might be able to fix it on their image.
    0
  • AzeDK
    Hetzner cloud servers are forced to only work with DHCP, which causes issues for CPANEL that doesn't support NetworkManager.
    0
  • Radeonpower
    I already have IPV6_DEFAULTDEV=enp5s0 in my config and still does not work. This is very annoying, before installing cPanel and rebooting everything is just fine. Never had this problem before. Edit: Ok, I started to look at logs now and I noticed an error regarding " that was missing from the end of the SCOPE line. Now everything works and it looks like this. Btw, this is a dedicated server from Hetzner. DEVICE=enp5s0 ONBOOT=yes BOOTPROTO=none IPADDR=157.90.xx.xx #PREFIX=32 NETMASK=255.255.255.192 GATEWAY=157.90.xx.xx DEFROUTE=yes SCOPE="peer [157.90.xx.xx]" NM_CONTROLLED=NO DNS1=49.12.xx.xx DNS2=5.255.xx.xx IPV6INIT=yes IPV6ADDR=2a01:4f8:xxx:xxxx::2/64 IPV6_DEFAULTGW=fe80::1 IPV6_DEFROUTE=no IPV6_AUTOCONF=yes IPV6_FAILURE_FATAL=no IPV6_DEFAULTDEV=enp5s0 Thanks. :cool:
    0
  • Andreix
    Hallo, I have the same issue on a cloud server. Now the system is stuck in the middle of an almalinux upgrade and cannot connect to any repository. I tried all of the above ideas and none work. I tried disabling ipv6 completely and no change. Any other ideas? curl -v www.google.com * Rebuilt URL to: www.google.com/ * Could not resolve host: www.google.com * Closing connection 0 curl: (6) Could not resolve host: www.google.com curl -4 works just fine. curent config is: BOOTPROTO=dhcp DEFROUTE=yes DEVICE=eth0 DNS1=8.8.8.8 DNS2=8.8.6.6 HWADDR=96:00:0xxxxxxxxxx IPADDR=94.1xxxxxxx ONBOOT=yes TYPE=Ethernet USERCTL=no NETMASK=255.255.255.192 IPV6INIT=yes IPV6ADDR=2a01:4f8:xxxxxxxxxx::1/64 IPV6_DEFAULTGW=fe8xxxxxx::1 IPV6_DEFROUTE=no IPV6_AUTOCONF=yes IPV6_FAILURE_FATAL=no IPV6_DEFAULTDEV=eth0 Thank you! Andrei
    0
  • AzeDK
    Hallo, I have the same issue on a cloud server. Now the system is stuck in the middle of an almalinux upgrade and cannot connect to any repository. I tried all of the above ideas and none work. I tried disabling ipv6 completely and no change. Any other ideas? curl -v www.google.com/ * Could not resolve host: www.google.com curl -4 works just fine. curent config is: BOOTPROTO=dhcp DEFROUTE=yes DEVICE=eth0 DNS1=8.8.8.8 DNS2=8.8.6.6 HWADDR=96:00:0xxxxxxxxxx IPADDR=94.1xxxxxxx ONBOOT=yes TYPE=Ethernet USERCTL=no NETMASK=255.255.255.192 IPV6INIT=yes IPV6ADDR=2a01:4f8:xxxxxxxxxx::1/64 IPV6_DEFAULTGW=fe8xxxxxx::1 IPV6_DEFROUTE=no IPV6_AUTOCONF=yes IPV6_FAILURE_FATAL=no IPV6_DEFAULTDEV=eth0 Thank you! Andrei

    You have to enable the NetworkManager service as the main network, its the only way almalinux 8.X can work with CPANEL, even though its not supported officially.
    0
  • Andreix
    You have to enable the NetworkManager service as the main network, its the only way almalinux 8.X can work with CPANEL, even though its not supported officially.

    I mean I did that but it can also be I did not do it right. Do you know of any description on how to properly do it? I imagine this has to be done during the upgrade, after the system is stuck. Thank you! Andrei
    0
  • AzeDK
    I mean I did that but it can also be I did not do it right. Do you know of any description on how to properly do it? I imagine this has to be done during the upgrade, after the system is stuck. Thank you! Andrei

    If you have console access, then you can login, and activate networkmanager from there. systemctl start NetworkManager systemctl enable NetworkManager
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post