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

SSH access troubles

JuanCar

Regular Pleskian
Hello
I run centos 5.4 Plesk 11.5.30
I cant Access SSH. It gives me a connect time out error.

Neither can Access FTP in pasive mode.

I reinit server and SSH runs Ok as proFTP does.

But after a few minutes SSH gone doan again, the timeout error
And FTP can work in pasive mode.

Any idea?
 
Oh, I'm silly

Thanks for your idea
That's strange.
I couldn't stop IPTablse because I had no SSH Access, so I uninstalled Firewall Extensión, but the problem didnt dissapear. (?)

So I reinstall Firewall Extension from Plesk and I wrote a custom rule with Access to my SSH port (I dont use 22, as a security measurement), and voilá: I can Access SSH. so the problem is fixed. But....

But, and this is the strange thing: I never had needed this rule, I always used the default firewall config from Plesk and I could Access SSH without any trouble (using my particular port, not 22).
Well, perhaps the explanation: ....just before this problem I updated rules with a new one to block an IP (a hacker IP), I suppose the default rule for SSH was not here before now and in the last Plesk update it appeared but it wasn't active. When I update with this IP block this rule was activated and I lost SSH Access.

This is the only explanation I can think of.

And what I have learned: not take anything for granted with Plesk updates ;).


Thanks for your help
Regards.
 
Back
Top