• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Problem with assigning IPv6 to new server

VojinP

Basic Pleskian
I have purchased new Centos 8 server without IPv6 support. Since I needed IPv6, they have added it. When I checked ip a I got:

Code:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 02:00:82:33:b4:3c brd ff:ff:ff:ff:ff:ff
    inet xxx.xx.xxx.xx/24 brd xxx.xx.xxx.xxx scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::82ff:fe33:b43c/64 scope link
       valid_lft forever preferred_lft forever

and sysctl -a | grep ipv6.*disable :

Code:
net.ipv6.conf.all.disable_ipv6 = 0
net.ipv6.conf.all.disable_policy = 0
net.ipv6.conf.default.disable_ipv6 = 0
net.ipv6.conf.default.disable_policy = 0
net.ipv6.conf.eth0.disable_ipv6 = 0
net.ipv6.conf.eth0.disable_policy = 0
net.ipv6.conf.lo.disable_ipv6 = 0
net.ipv6.conf.lo.disable_policy = 0

so it looks all is OK with IPv6. However when I try to reread IP addresses, got nothing, and when want manually to add one, fe80::82ff:fe33:b43c/64, I got following message:

The specified IP address cannot be used on network interface. You need to specify a valid IP address with subnet prefix range or mask.

Any ide why and how to fix that?
 
CentOS 8 is using NetworkManager. The NetworkManager is not supported in Plesk, and it is recommended to disable this component. I think this may be a reason for this issue.
 
I have tried to ping that IPv6 and it looks it is working, but not in plesk yet...

Code:
[root@scala ~]# ping6 fe80::82ff:fe33:b43c
PING fe80::82ff:fe33:b43c(fe80::82ff:fe33:b43c) 56 data bytes
64 bytes from fe80::82ff:fe33:b43c%eth0: icmp_seq=1 ttl=64 time=0.145 ms
64 bytes from fe80::82ff:fe33:b43c%eth0: icmp_seq=2 ttl=64 time=0.068 ms
64 bytes from fe80::82ff:fe33:b43c%eth0: icmp_seq=3 ttl=64 time=0.074 ms
64 bytes from fe80::82ff:fe33:b43c%eth0: icmp_seq=4 ttl=64 time=0.100 ms
 
Hmm.. it looks it was problem with network configuration. Just edited it and it works now like a charm.
 
Back
Top