• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Question IPv6 Plesk Setup Tutorial

Branko

Branko

Basic Pleskian
Is it possible to get some thorough tutorial how to get Plesk server IPv6 ready?

How to setup properly /etc/sysconfig/network-scripts/ifcfg-eth0 ?
How to setup properly Nginx for IPv6?
How to setup /etc/sysconfig/network and /etc/sysctl.conf?

I ask for this because I haven't found the complete tutorial for this on the web.

Thank you in advance.
 
Last edited:
Branko said:
Is it possible to get some thorough tutorial how to get Plesk server IPv6 ready?

How to setup properly /etc/sysconfig/network-scripts/ifcfg-eth0 ?
How to setup properly Nginx for IPv6?
How to setup /etc/sysconfig/network and /etc/sysctl.conf?

I ask for this because I haven't found the complete tutorial for this on the web.

Thank you in advance.
Click to expand...

This settings depend on your hosting provider, not on Plesk configuration. When you will have configure properly an IPv6 on your server, then you will be able to use the button "re-read IPs" in Tools & Settings > IP Address .
 
Thank you. :)

Let's try like this to make this tutorial. At least for my system, I am sure it will be helpful to many.

My system is:
Version: Plesk Onyx v17.5.3_build1705170317.16 os_CentOS 7
OS: CentOS Linux 7.4.1708 (Core)

After my request, my host enabled IPv6 support on my VPS server.
Also from my host (LeaseWeb), I got this address(es):
2001:1af8:4700:a121:1200:0000:0000:0000
until
2001:1af8:4700:a121:1200:0000:0000:ffff
Netmask: /64
Gateway: 2001:1af8:4700:a121:1200:0000:0000:0001


In Plesk IP Addresses interface, I added 2001:1af8:4700:a121:1200::1 /64 as dedicated (or should I add it as shared?)
Is this ok?

Changed /etc/sysctl.conf to
net.ipv6.conf.all.disable_ipv6=0
net.ipv6.conf.default.disable_ipv6=0

Is this ok so far?
 
Last edited:
Branko said:
Thank you. :)

Let's try like this to make this tutorial. At least for my system, I am sure it will be helpful to many.

My system is:
Version: Plesk Onyx v17.5.3_build1705170317.16 os_CentOS 7
OS: CentOS Linux 7.4.1708 (Core)

After my request, my host enabled IPv6 support on my VPS server.
Also from my host (LeaseWeb), I got this address(es):
2001:1af8:4700:a121:1200:0000:0000:0000
until
2001:1af8:4700:a121:1200:0000:0000:ffff
Netmask: /64
Gateway: 2001:1af8:4700:a121:1200:0000:0000:0001


In Plesk IP Addresses interface, I added 2001:1af8:4700:a121:1200::1 /64 as dedicated (or should I add it as shared?)
Is this ok?

Changed /etc/sysctl.conf to
net.ipv6.conf.all.disable_ipv6=0
net.ipv6.conf.default.disable_ipv6=0

Is this ok so far?
Click to expand...

Hello @Branko, you can choose to use your IPv6 as dedicated or shared IP. You can remove the two lines from your /etc/sysctl.conf file and then apply the new configuration with sysctl -p.
Then check if you can ping under IPv6 with the command : ping6 2001:4860:4860::8888
 
Thank you :)

I did what you said and got this

PING 2001:4860:4860::8888(2001:4860:4860::8888) 56 data bytes
From 2001:1af8:4700:a121:1200::2 icmp_seq=1 Destination unreachable: Address unreachable
From 2001:1af8:4700:a121:1200::2 icmp_seq=2 Destination unreachable: Address unreachable
64 bytes from 2001:4860:4860::8888: icmp_seq=3 ttl=57 time=1.20 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=4 ttl=57 time=1.19 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=5 ttl=57 time=2.23 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=6 ttl=57 time=1.13 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=7 ttl=57 time=1.22 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=8 ttl=57 time=2.31 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=9 ttl=57 time=1.08 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=10 ttl=57 time=1.81 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=11 ttl=57 time=1.62 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=12 ttl=57 time=1.07 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=13 ttl=57 time=1.24 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=14 ttl=57 time=1.90 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=15 ttl=57 time=2.05 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=16 ttl=57 time=1.07 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=17 ttl=57 time=1.22 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=18 ttl=57 time=3.12 ms

Why does it say 2001:1af8:4700:a121:1200::2 when I have 2001:1af8:4700:a121:1200::1 /64 ?

Oh, that address I sent my registrar to connect it to my primary nameserver. Maybe thatsthe reason?
 
Last edited:
Branko said:
Thank you :)

I did what you said and got this

PING 2001:4860:4860::8888(2001:4860:4860::8888) 56 data bytes
From 2001:1af8:4700:a121:1200::2 icmp_seq=1 Destination unreachable: Address unreachable
From 2001:1af8:4700:a121:1200::2 icmp_seq=2 Destination unreachable: Address unreachable
64 bytes from 2001:4860:4860::8888: icmp_seq=3 ttl=57 time=1.20 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=4 ttl=57 time=1.19 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=5 ttl=57 time=2.23 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=6 ttl=57 time=1.13 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=7 ttl=57 time=1.22 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=8 ttl=57 time=2.31 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=9 ttl=57 time=1.08 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=10 ttl=57 time=1.81 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=11 ttl=57 time=1.62 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=12 ttl=57 time=1.07 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=13 ttl=57 time=1.24 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=14 ttl=57 time=1.90 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=15 ttl=57 time=2.05 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=16 ttl=57 time=1.07 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=17 ttl=57 time=1.22 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=18 ttl=57 time=3.12 ms

Why does it say 2001:1af8:4700:a121:1200::2 when I have 2001:1af8:4700:a121:1200::1 /64 ?

Oh, that address I sent my registrar to connect it to my primary nameserver. Maybe thatsthe reason?
Click to expand...

Check if your interface address is 2001:1af8:4700:a121:1200::1 or 2001:1af8:4700:a121:1200::2 with the command ifconfig
 
Thank you, here goes result

[root@web ~]# ifconfig
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0
ether 02:42:38:51:8f:c5 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 5.79.100.17 netmask 255.255.255.0 broadcast 5.79.100.255
inet6 2a05:4f8:111:40a3::2 prefixlen 64 scopeid 0x0<global>
inet6 2001:1af8:4700:a121:1200::1 prefixlen 64 scopeid 0x0<global>
inet6 fe80::4b8:3aff:fe00:1323 prefixlen 64 scopeid 0x20<link>
inet6 2001:1af8:4700:a121:1200::2 prefixlen 128 scopeid 0x0<global>
inet6 2001:1af8:4700:a121:1200::3 prefixlen 128 scopeid 0x0<global>
inet6 2001:1af8:4700:a121:1200::4 prefixlen 128 scopeid 0x0<global>
inet6 2001:1af8:4700:a121:1200::5 prefixlen 128 scopeid 0x0<global>
inet6 2001:1af8:4700:a121:4b8:3aff:fe00:1323 prefixlen 64 scopeid 0x0< global>
ether 06:b8:3a:00:13:23 txqueuelen 1000 (Ethernet)
RX packets 32656 bytes 14533928 (13.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 29177 bytes 42603058 (40.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 26245 bytes 10278666 (9.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 26245 bytes 10278666 (9.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


I see there several addresses I added, and then removed from the panel. I did REREAD IP after removing them.
Now in Plesk IP addresses, I only have my IPv4 and 2001:1af8:4700:a121:1200::1 /64.

What should I do?
 
Last edited:
Branko said:
Thank you, here goes result

[root@web ~]# ifconfig
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0
ether 02:42:38:51:8f:c5 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 5.79.100.17 netmask 255.255.255.0 broadcast 5.79.100.255
inet6 2a05:4f8:111:40a3::2 prefixlen 64 scopeid 0x0<global>
inet6 2001:1af8:4700:a121:1200::1 prefixlen 64 scopeid 0x0<global>
inet6 fe80::4b8:3aff:fe00:1323 prefixlen 64 scopeid 0x20<link>
inet6 2001:1af8:4700:a121:1200::2 prefixlen 128 scopeid 0x0<global>
inet6 2001:1af8:4700:a121:1200::3 prefixlen 128 scopeid 0x0<global>
inet6 2001:1af8:4700:a121:1200::4 prefixlen 128 scopeid 0x0<global>
inet6 2001:1af8:4700:a121:1200::5 prefixlen 128 scopeid 0x0<global>
inet6 2001:1af8:4700:a121:4b8:3aff:fe00:1323 prefixlen 64 scopeid 0x0< global>
ether 06:b8:3a:00:13:23 txqueuelen 1000 (Ethernet)
RX packets 32656 bytes 14533928 (13.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 29177 bytes 42603058 (40.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 26245 bytes 10278666 (9.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 26245 bytes 10278666 (9.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


I see there several addresses I added, and then removed from the panel. I did REREAD IP after removing them.
Now in Plesk IP addresses, I only have my IPv4 and 2001:1af8:4700:a121:1200::1 /64.

What should I do?
Click to expand...

I don't know how leaseweb configure IPv6 networking on their servers, and I'm not sure to understand why ifconfig display several IPv6 on the same interface.
 
Thank you very much, you have been very helpful nevertheless.

I realized now that definitely there is a difference in IPv6 settings from host to host.
 
Ok, I decided to change approach.

Because deleting of old IP addresses from network interface was a realy big workaround, at least form me. See why on Issue - Cannot delete IPv6 addresses

I decided to try to make this IPv6 addresses I already have in my network interface work.

I did REREAD IP in Plesk interface, and this is what I have there now:
2001:1af8:4700:a121:1200::1 /128 eth0 dedicated
2001:1af8:4700:a121:1200::2 /128 eth0 dedicated
2001:1af8:4700:a121:1200::3 /128 eth0 dedicated
2001:1af8:4700:a121:1200::4 /128 eth0 dedicated
2001:1af8:4700:a121:1200::5 /128 eth0 dedicated
2a05:4f8:111:40a3::2 /64 eth0 dedicated (this address I dont realy know where it comes from, I have never added it)
5.79.100.17 /255.255.255.0 eth0 shared


For [root@web ~]# ifconfig
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0
ether 02:42:a5:d2:f3:49 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 5.79.100.17 netmask 255.255.255.0 broadcast 5.79.100.255
inet6 2a05:4f8:111:40a3::2 prefixlen 64 scopeid 0x0<global>
inet6 2001:1af8:4700:a121:1200::1 prefixlen 128 scopeid 0x0<global>
inet6 fe80::4b8:3aff:fe00:1323 prefixlen 64 scopeid 0x20<link>
inet6 2001:1af8:4700:a121:1200::2 prefixlen 128 scopeid 0x0<global>
inet6 2001:1af8:4700:a121:1200::3 prefixlen 128 scopeid 0x0<global>
inet6 2001:1af8:4700:a121:1200::4 prefixlen 128 scopeid 0x0<global>
inet6 2001:1af8:4700:a121:1200::5 prefixlen 128 scopeid 0x0<global>
inet6 2001:1af8:4700:a121:4b8:3aff:fe00:1323 prefixlen 64 scopeid 0x0<global>
ether 06:b8:3a:00:13:23 txqueuelen 1000 (Ethernet)
RX packets 2787253 bytes 1889334522 (1.7 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2283307 bytes 4862104518 (4.5 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 1086461 bytes 617913952 (589.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1086461 bytes 617913952 (589.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


And in /etc/sysconfig/network-scripts/ifcfg-eth0 I have this
DEVICE="eth0"
BOOTPROTO=none
ONBOOT="no"
IPV6INIT=yes
IPV6ADDR=2001:1af8:4700:a121:1200::2/64
IPV6_DEFAULTGW=2001:1af8:4700:a121:1200::1/64
IPV6_DEFAULTDEV=eth0
TYPE=Ethernet
NAME="eth0"
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
PEERDNS=yes
PEERROUTES=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6ADDR_SECONDARIES="2001:1af8:4700:a121:1200::5/128 2001:1af8:4700:a121:1200::4/64 2001:1af8:4700:a121:1200::3/64 2001:1af8:4700:a121:1200::2/64"


I added 2001:1af8:4700:a121:1200::2 IPv6 address to one subscitpion (4 websites).

Problem is when I restart my network IPv6 works for maybe 10 minutes and then stops working.
Checking my network on IPv6 test - web site reachability , Is your site IPv6 ready? , IPv6 domain readiness tester and IPv6 health check | Mythic Beasts

I did not touch anything additionally besides official Plesk instructions.

Can someone plese help a bit?

Thank you!
 
You must log in or register to reply here.

Similar threads

W
Issue IPv6 set up under Plesk, but not served for vhost
Replies
3
Views
416
MartinT
M
M
Question Nginx Bind () issue
Replies
2
Views
203
maximus99
M
Z
Question Woocommerce, Redis, PHP Settings - Newbie questions
Replies
5
Views
722
Zakky
Z
Paul Hermans
Issue Error: ifmng failed: /etc/sysconfig/network-scripts/ifcfg-eth0: No such file or directory
Replies
1
Views
1K
Paul Hermans
Paul Hermans
G
Resolved WP Toolkit setup new password for admin haystack (language) error
Replies
1
Views
629
gmu-jerdj
G
Back
Top