Cannot save changes in Basic Configuration

janipewter

Active Member
Jan 2, 2013
44
3
8
cPanel Access Level
Root Administrator
I am trying to configure IPv6 on my server.

I have two IPv4 addresses (one physical NIC) both working fine, IPv4 address #1 is the system shared IP and is used for ns1 and everything else, IPv4 address #2 is a dedicated IP and is only used for ns2 and a single site.

My ISP has assigned me an IPv6 /80 I think, and I have successfully configured one address (I just used the very first one) to the server's NIC and can ping other ipv6 hosts on the internet as well ping it from other ipv6 hosts (such as home).

I have configured mailserver and cpanel services to listen on IPv6 also. As per cPanel manual "Guide to IPv6" in the IPv6 Ranges menu I added the IPv6 gateway address as reserved, and also added a small /120 segment at the bottom of the pool as reserved (more on that in a sec). I then added the entire /80 as a shared address pool so I can start assigning IPv6 addresses to my sites.

I go to the Assign IPv6 Address menu and I see a message on the right which says "You have not configured a shared IPv6 address. To do this, use the Basic cPanel & WHM Setup interface." (more on this in a sec too).

I pick a site and select my shared address pool in the drop down menu and click Enable. Now it seems to fail quietly, as all that happens is the drop down menu disappears. No confirmation message, and if I refresh the page, IPv6 has not been enabled for that site.

Anyway, I head on over to the WHM Basic Configuration to set up a shared IPv6 address. I enter the address I intend to use (which is definitely not assigned to anything else, and it's in my reserved range anyway), click Save Changes, then all I get is a page saying "This system has 0 free IP's". No confirmation message again, it just seems to fail silently as if I navigate to the shared IPv6 address setting again in the Basic Configuration, there is nothing in the box.

I also see that I should configure my nameserver address records to add IPv6 addresses, so I try that. Where it says "Enter an IPv6 address to create an AAAA record (optional)" I put in another IPv6 address (a different one in my reserved range, not used by anything else), click on Configure Address Records, and I get some confirmation message which looks promising:

Code:
Configuring Address Records for nameserver...                  
                  
Bind reloading on <server hostname> using rndc zone: [ns1.<mydomain>]


...Done

The following IP addresses have been assigned to the ns1.<mydomain> nameserver:

   IPv4 #1 address
  
   IPv6 address I have chosen for ns1 (also the same IPv6 address assigned to the server's NIC)
I close this window, click Save Changes, then once again it seems to fail quietly and I just get the "This system has 0 free IP's" message and none of the changes have been saved.

So at this moment I cannot use IPv6 in cPanel. Please help.
 
Last edited by a moderator:

24x7server

Well-Known Member
Apr 17, 2013
1,912
99
78
India
cPanel Access Level
Root Administrator
Twitter
Hi,

Have you enabled the IPv6 in the tweak settings?
Home >> Server Configuration >> Tweak Settings and select On for the Listen on IPv6 Addresses setting.

Please check once if this is enable or not..
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,880
2,268
463
Hello,

Feel free to open a support ticket using the link in my signature so we can take a closer look at the affected system. You can post the ticket number here so we can update this thread with the outcome.

Thank you.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,880
2,268
463
Hello,

To note, internal case CPANEL-12476 is open to address an issue where range assignment errors are not presented in the WHM UI when assigning an IPv6 address. I'll monitor this case and update this thread with more information once it's available. In the meantime, you can review /usr/local/cpanel/logs/error_log if you encounter an issue adding IPv6 addresses and no error messages are presented in the UI. Also, feel free to open a support ticket if you'd like us to take a closer look and see why switching to PowerDNS addressed the issue.

Thank you.
 
  • Like
Reactions: cPdans