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

Resolved Root SSH port 22 fail - SSH session terminated by remote party

hardbrasil

Regular Pleskian
Hello fellas,
my root login stop from nothing, i am able to login to machine by KVM trough datacenter panel,

all attempt by remote on port 22 with user root i receive an "Disconected" would like to try again?

By KVM i disable denyhosts, Iptables,
By Plesk i disable plesk firewall
Port 22 still open
sshd service is runing...
i've checkd sshd.conf as well

i've tryed many things like:
https://kb.plesk.com/en/127467

and others things...

any light?
 
I discovery that out of my network i am able to login.
i mean trough other ISP conections, its look like and IP blocking...
how can i discovery what is blocking if all firewall are disable?
 
It was denyhosts, for some reason, was missing an ":" between rule and IP.
by the way...

service was disable, and when was active was working...
misterious from linux,

Solved!
 
Back
Top