• 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 Domain not reachable on ipv6

AdrianC

Basic Pleskian
I noticed some problems (request timeouts) between my servers and it turns out that if a request to my domain is made by ipv6 it returns timeout.

And if I test with online ipv6 tools I get:

Code:
AAAA DNS record: [MY V6 IP]
IPv6 web server: web server is unreachable : Connection timed out

Anything I can change on the server ?
From what I can tell Apache is not listening on ipv6 but before messing with Apache config files, I assume there is something I can do in Plesk web interface ?

Under domains > domain > web hosting access I see both ipv4 and ipv6 being used.

Edit: the command /usr/sbin/lsof -i | grep -i httpd seems to show apache listening on ipv6 from what I can tell

Code:
httpd     13722       apache    4u  IPv6 152015784      0t0  TCP *:http (LISTEN)
httpd     13722       apache    6u  IPv6 152015788      0t0  TCP *:https (LISTEN)
httpd     13723       apache    4u  IPv6 152015784      0t0  TCP *:http (LISTEN)
 
Last edited:
Note to self :) ...
This was fixed by adding this to /etc/sysconfig/network-scripts/ifcfg-eth0

Code:
IPV6INIT=yes
IPV6ADDR=2a05:4f8:111:40a3::2/64
IPV6_DEFAULTGW=fe80::1
IPV6_DEFAULTDEV=eth0
 
How is possible that I have that same address
2a05:4f8:111:40a3::2/64
in my Plesk IP addresses interface?
Never inserted that address, it just poped up after one REREAD IP.

And same problem as you?
 
Last edited:
How is possible that I have that same address
in my Plesk IP addresses interface?

Please ask your provider about this. He may use the same image for installing new systems and might not have changed the IPv6 to the correct individual IP after image installation.

It is possible, too, that the initial poster gave up his server (the post was from 2015) and you now own that server or IPv6 address for your system.
 
Just for the record, I contacted hosting provider, and they fixed the issue. Obvously, it was some problem with the initial server setup.
 
Back
Top