Skip to main content

sshd has failed

Comments

6 comments

  • sserbest
    Forget to add versions; Centos 7.4 and Cpanel version v68.0.16
    0
  • cPanelMichael
    Hello, You can't manipulate file/directory permissions for system files via Web Host Manager, but you could try temporarily starting a new instance of SSH using the SSH autofixer referenced at: SSH Connection Denied Thank you.
    0
  • sserbest
    Hello, You can't manipulate file/directory permissions for system files via Web Host Manager, but you could try temporarily starting a new instance of SSH using the SSH autofixer referenced at: SSH Connection Denied Thank you.

    Yes, I tried this before and here is the result. AutoFixer Execution Requesting script ... Done. Executing script ... Attempting to locate sshd binaries installed on the system ...
    Located /usr/sbin/sshd
    Done.
    Killing exisiting sshd processes...
    Done.
    configuring sshd to run on port 22
    Could not load host key: /etc/ssh/ssh_host_dsa_key /var/empty/sshd must be owned by root and not group or world-writable. failed to start /usr/sbin/sshd ...
    Done.
    0
  • cPanelMichael
    Hello, There's no additional method of solving that issue without console access to the system. Since that's not possible (per your initial post), then you may need to report this to your provider or data center so they can address the issue. Thank you.
    0
  • sserbest
    Thank you, for your response but I wish there is a way to solve this issue easily. I solved the problem with different approach. I'm using Google Cloud Services and I remember Google allows me to run Startup script and I use that to change folder permission and problem solved. Here is the trick :) I hope will help someone else. Under VM instance details, there is place name "Custom metadata" If you add this code (double quotes just for separation each input field) and restart the server, will solve the issue. "startup-script" "chown root:root /var/empty/sshd"
    0
  • cPanelMichael
    Hello, I'm glad to see you were able to solve the issue. Thank you for updating us with the outcome.
    0

Please sign in to leave a comment.