# Cannot SSH after 2.31.139 upgrade EX4100

**URL:** <https://community.wd.com/t/cannot-ssh-after-2-31-139-upgrade-ex4100/240537>\
**Category:** My Cloud OS 3\
**Created:** [August 12, 2019, 2:53am UTC](https://community.wd.com/t/cannot-ssh-after-2-31-139-upgrade-ex4100/240537 "2019-08-12T02:53:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![M\_G](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@M\_G](https://community.wd.com/u/M_G)\
**Post date:** [August 12, 2019, 2:53am UTC](https://community.wd.com/t/cannot-ssh-after-2-31-139-upgrade-ex4100/240537/1 "2019-08-12T02:53:40Z")

</div>

SSH login appeared to stop working after a background upgrate to the 2.31.139 firmware.

Mutliple attempts at rebooting, enabling/disabling SSH, setting the password don’t seem to help.

I see that updates were made to SSH in the latest release notes. Is it possible that the user to log in with is no longer ‘root’ and contextual to the set up ‘Users’? If I am locked out, is there a way to upload an ‘app’ to run a script to re-gain access etc?

`root@<my ex4100>: Permission denied (publickey,password).` - no matter what I do.

---

<div class="post-metadata">

**Author:** ![M\_G](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@M\_G](https://community.wd.com/u/M_G)\
**Post date:** [August 14, 2019, 3:53pm UTC](https://community.wd.com/t/cannot-ssh-after-2-31-139-upgrade-ex4100/240537/2 "2019-08-14T15:53:13Z")

</div>

Similar problem reported: [PR4100: Can't log on with SSH anymore](http://community.wd.com/t/pr4100-cant-log-on-with-ssh-anymore/240598)

---

<div class="post-metadata">

**Author:** ![jebusx](https://avatars.discourse-cdn.com/v4/letter/j/b4bc9f/32.png) [@jebusx](https://community.wd.com/u/jebusx)\
**Post date:** [August 16, 2019, 4:37pm UTC](https://community.wd.com/t/cannot-ssh-after-2-31-139-upgrade-ex4100/240537/3 "2019-08-16T16:37:46Z")

</div>

the default login name is “sshd” and the password is whatever you set.