• 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!
  • 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.

Services only available on IPv6

freaky@

Regular Pleskian
Hi there,

just installed Plesk 11.0.9 on CentOS 6.3 and I noticed I can't connect to the majority of the services over IPv4. I haven't added any IPv6 addresses in Plesk yet (the machine does have a link-local address). Didn't forcefully disable it either as we do want to use it in the future.

Anyways, I can access plesk through a little SSH trickery (ssh -L 8443:<local ipv4!! address>:8443 <user>@<host>) and then connect my browser to https://localhost:8443. The odd thing is this uses IPv4 too thus.

Anyone have some tips? If this is how it's supposed to work, what's going to happen once I do enable IPv6? I really don't want to tell most, if not all, of my users that still only have IPv4 they won't be able to access the control panel until they get IPv6 which will probably be years away for most of them.

tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:36944 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:465 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:10001 0.0.0.0:* LISTEN
tcp 0 0 W.X.Y.Z:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:3000 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:12768 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:12768 127.0.0.1:57510 ESTABLISHED
tcp 0 400 W.X.Y.Z:22 83.96.170.135:34430 ESTABLISHED
tcp 0 0 127.0.0.1:52861 127.0.0.1:25 ESTABLISHED
tcp 0 0 127.0.0.1:25 127.0.0.1:52861 ESTABLISHED
tcp 0 0 127.0.0.1:57510 127.0.0.1:12768 ESTABLISHED
tcp 0 0 :::7080 :::* LISTEN
tcp 0 0 :::7081 :::* LISTEN
tcp 0 0 :::106 :::* LISTEN
tcp 0 0 :::110 :::* LISTEN
tcp 0 0 :::143 :::* LISTEN
tcp 0 0 :::111 :::* LISTEN
tcp 0 0 :::8880 :::* LISTEN
tcp 0 0 :::465 :::* LISTEN
tcp 0 0 :::53 :::* LISTEN
tcp 0 0 :::21 :::* LISTEN
tcp 0 0 :::22 :::* LISTEN
tcp 0 0 :::55958 :::* LISTEN
tcp 0 0 :::25 :::* LISTEN
tcp 0 0 :::8443 :::* LISTEN
tcp 0 0 :::993 :::* LISTEN
tcp 0 0 :::995 :::* LISTEN


With exception of a few, most are not accessible thus. Basically anything that's only bound to :::<port> and not to 0.0.0.0:<port> (as SSH is) as well is unreachable.

TIA
 
Last edited:
I noticed I can't connect to the majority of the services over IPv4. I haven't added any IPv6 addresses in Plesk yet

If you havent added IPv6 then how are you able to tell you can't connect via IPv4? How else would you be connecting to the server?

Am trying to drive to the point that the problem might not be the IPs, but rather something with the services, blocked ports or a strict Firewall on the server ...

Am also assuming its a new plesk default installation..
 
Back
Top