• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Plesk9 and SSH problem

GiulianoP

Basic Pleskian
Hi all,
I use Plesk 9.2.1 with OpenSuse 10.1.

I have a problem with OpenSSH.
I have upgraded my plesk version from 8.6 to 9.2.1.
The SSH daemon running on port 51099 without any problems.
In these days I have change the SSH port from 51099 to 22 because I must use the Plesk Migration Manager and
so is necessary to use the default ssh port.
Now I can't to connect to server with winscp or putty on 22 port.
I have check the plesk firewall but is all rights.

/usr/sbin/iptables -A INPUT -p tcp --dport 22 -j ACCEPT

and the all rules running successfully.

If I change the default port to precedent port 51099 the connection to the server running successfully.

I don't understand the problem, because if I reset the firewall with these rules don't change any.

echo 0 > /proc/sys/net/ipv4/ip_forward
/usr/sbin/iptables -F
/usr/sbin/iptables -X
/usr/sbin/iptables -Z
/usr/sbin/iptables -P INPUT ACCEPT
/usr/sbin/iptables -P OUTPUT ACCEPT
/usr/sbin/iptables -P FORWARD ACCEPT

Thare are the default iptables rules.

I think that Plesk save the ssh socket in some configuration files but I don't know these files.

Any idea?

Thanking in advance and sorry for my english.

Giuliano
 
Plesk doesnt manage ssh, so you can rule that out right away. First I'd make sure the ssh daemon is running, and listening on port 22 with: ps aux |grep sshd and netstat -pan

Then clear your rules with:
/etc/init.d/iptables stop

last but not least, make sure /etc/ssh/sshd_config is set up to Listen on port 22
 
Thank you for your reply.

I have check all, and in this moment with 51099 socket the sshd running successfully.
Now I try to set the default port 22:

a. In the /etc/ssh/sshd_config I change the Port to 22
b. restart the service /etc/init.d/sshd restart
c. with "ps aux" and "nmap -p1-65535 localhost" I see the daemon:

root 3736 0.0 0.1 10692 2728 ? Ss 19:02 0:00 sshd: root@pts/0

22/tcp open ssh

d. I clear the firewall and so I have the original situation with default policy:

srv1:/etc/ssh # iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

e. With netstat -pan I see the daemon:

tcp 0 0 :::22 :::* LISTEN 7471/sshd

Now I try to connect with Putty (set to 22 port) but doesn't running, connection timeout.

f. This server has is public 84.18.157.18 and the second server with 84.18.157.19 has the same problem, but from .19 I can to connect to SSH on 22 port of .18 server.
I know that these IP are in the same subnet but there aren't any rules that enable the ssh connection only for subnet Ip on 22 default port.

I don't understand the problem....

Thank and sorry for my english.
 
Upstream firewall could be blocking it then, or some other filter (router, switch, etc) on a system between you and the server
 
Yes...you are right.....
My god.......I think that the ISP has enable the rules on Alcatel Firewall 1 years ago...but my company doesn't paid any
tax for this service.....
Tomorrow I will call the ISP.........this situation is very strange.....

Thank you very much for your support.

Best Regards.

Giuliano
 
Back
Top