- Community Home
- >
- Software
- >
- HPE Morpheus Software
- >
- HPE Morpheus VM Essentials
- >
- SSH doesn't work on fresh install
Categories
Company
Local Language
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
3 hours ago
SSH doesn't work on fresh install
Performing a fresh install of VME on new hosts.
After the initial install we can log into the console directly, but SSH doesn't work.
SSH answers, but the username and password don't work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
3 hours ago
Re: SSH doesn't work on fresh install
I assume you are talking about SSH on the Morpheus appliance, in which case the following are likely causes:
- SSH password auth disabled globally: There is a setting in the VM Essentials appliance to “Disable SSH Password Authentication” so that only SSH keys are allowed for logins. If this is enabled by default in your build or was enabled during setup, any username/password will be rejected over SSH even though the same credentials work on the console
- Different user account for SSH vs UI: VM Essentials manages its own user model and credentials, including Linux/SSH users and keypairs. The account you use for the web UI or the initial console configuration may not correspond to an OS-level user allowed to log in over SSH
- SSH only permitting key‑based auth for provisioned hosts: The same appliance setting also affects VMs and hosts that the platform provisions, where it can intentionally block password-based SSH and only push keys. If you are testing SSH to those new hosts, you may be hitting this policy rather than a bad password
Here are a couple of things you could try to troubleshoot this:
- From the local console (where you can log in): Verify the SSH daemon’s PasswordAuthentication setting in sshd_config and confirm whether it is set to no in which case you want to change this to yes.
- In the VM Essentials UI, go to the main Settings / Appliance Settings and look for the option that disables SSH password authentication, and temporarily turn it off if you intend to use passwords
- From the local console (where you can log in): Confirm which actual Linux user exists for SSH (sudo cat /etc/passwd), and reset that user’s password from the console if needed (sudo passwd <account>)
Hope that helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
3 hours ago
Re: SSH doesn't work on fresh install
No, SSH on the hypervisor doesn't work
We haven't installed the UI yet