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

Debian5/Plesk 10.21 : xinetd sshd stopped ..cannot acces via ssh

kadoudal

Regular Pleskian
I cannot access my server via SSH to restart them...
I guess xinetd and sshd are stopped .. but I cannot check it as no console access

my Plesk console is running , I can login as admin ,
Apache is running ( sites are online) , SMTP, QMAIL are running

this happen after some work on the public keys access ( authorized keys..)
I can access the server config files via a RESCUE console network
but what should I check first ? is there anyway to reset a standard initial ssh access ?

thanks for your help
 
SOLVED ..
I could access via KVM RESCUE Console .. trying to restart ssh gave ma an error
/var/run/sshd must be owned by root and not group or world writable

it was group writable .. ( I surely did a mistake ...) corrected , now ssh restarted
 
Back
Top