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
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: