• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved IPv6 not working

Creativados

Basic Pleskian
This is se second part for this thread

Let's Encrypt fail over IPv6

Simplifying the subject

# ping6 google.com
connect: Network is unreachable

but

# ip address
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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether d0:50:99:d2:32:82 brd ff:ff:ff:ff:ff:ff
inet 51.83.2.118/24 brd 51.83.2.255 scope global dynamic eno1
valid_lft 76831sec preferred_lft 76831sec
inet6 2001:41d0:203:4b76::/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::d250:99ff:fed2:3282/64 scope link
valid_lft forever preferred_lft forever
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether d0:50:99:d2:32:83 brd ff:ff:ff:ff:ff:ff


where is the problem?

Thanks
 
Hi,

Do you have found a solution?
We have the same problem...
Hi,


It was a problem in the OVH network card that they solved.
This was the explanation they gave me:

We have corrected the space in front of the first `dev eno1`.
No firewall has been detected on the server, so we have executed a software reboot.

The server is booted on disk and is on the login screen. Ping OK and services are up.
 
Back
Top