Unable to configure shared IPv6

PeteS

• June 19, 2017 03:03

I had everything working for IPv6 (including shared IPv6), but needed to change a range, and since I can't edit an existing one, I had to remove it (and to do that I had to remove all other references to it first). After adding the ranges back in again, I can't add the shared IPv6. All other IPv6 functions seem to be working. It doesn't give an error nor a message that it is updating the shared IPv6. It just returns with the number of IPs (v4) available, and the IPv6 is still blank. Any help here, or links to current discussions appreciated. I Googled but found nothing that matches my problem except this post: Why can't I configure the server's shared IPv6 address?

• 

  cPanelMichael

  • June 19, 2017 16:09

  Hello, Do you notice any output to /usr/local/cpanel/logs/error_log when attempting to update the default shared IPv6 address in WHM? Thank you.

  0
• 

  PeteS

  • June 19, 2017 16:17

  Hello, Do you notice any output to /usr/local/cpanel/logs/error_log when attempting to update the default shared IPv6 address in WHM? Thank you.

  
  No. I ran it again now, and checked the log; no new entry.

  0
• 

  cPanelMichael

  • June 19, 2017 16:21

  Hello, Could you open a support ticket using the link in my signature so we can take a closer look? Thank you.

  0
• 

  PeteS

  • June 19, 2017 17:49

  Hello, Could you open a support ticket using the link in my signature so we can take a closer look? Thank you.

  
  Aftter setting up to submit the ticket it indicates that my license vendor is my first line of support, so I will let them take it from here. If they cannot resolve it, either they or I will submit a ticket directly to cPanel.

  0
• 

  PeteS

  • June 20, 2017 05:36

  Ok, we got it to work. I wasn't using the IPv6 which was bound to the server (ip -6 addr show scope global). I know... "duh," but there should be an error message, IMO. I had no idea it had changed. Initially I was able to it set ...::100, so that address was bound then, right? I'd guess it was because it the first available after the reserved block for the admins. But after removing everything a different, "random" address was bound. Once we discovered that, then we could set that address as the share IPv6. Thoughts?

  0
• 

  cPanelMichael

  • June 20, 2017 15:36

  I wasn't using the IPv6 which was bound to the server (ip -6 addr show scope global). I know... "duh," but there should be an error message, IMO. I had no idea it had changed.

  
  Hello, Internal case CPANEL-7396 will help prevent this from happening in

  0

Please sign in to leave a comment.