# Can't ssh to container on fresh install

**URL:** <https://meta.discourse.org/t/cant-ssh-to-container-on-fresh-install/35046>\
**Category:** Support\
**Created:** [29 Outubro , 2015 08:30 UTC](https://meta.discourse.org/t/cant-ssh-to-container-on-fresh-install/35046 "2015-10-29T08:30:26Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![axp](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/axp/32/116685_2.png) [@axp](https://meta.discourse.org/u/axp)\
**Post date:** [29 Outubro , 2015 08:30 UTC](https://meta.discourse.org/t/cant-ssh-to-container-on-fresh-install/35046/1 "2015-10-29T08:30:26Z")

</div>

Just set up Discourse (stable) on Debian 8.1 (2 gigs DO droplet) following this guide [discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md)

After bootstraping and starting app I can’t ssh into container because of incorrect root password. I also tried fresh install with this settings in app.yml:

- exec: /usr/sbin/usermod -p “$(mkpasswd -m sha-256 ‘SuperPassword’)” root. Same result.

So what is the correct way to configure ssh access? Thanks.

P.S. Installation was made by root if it does matter.

---

<div class="post-metadata">

**Author:** ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)\
**Post date:** [29 Outubro , 2015 09:38 UTC](https://meta.discourse.org/t/cant-ssh-to-container-on-fresh-install/35046/2 "2015-10-29T09:38:31Z")

</div>

Do you actually need to SSH into the container? A simple `./launcher enter app` should always work to get a shell inside the container. I’ve never really needed SSH 🙂

---

<div class="post-metadata">

**Author:** ![axp](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/axp/32/116685_2.png) [@axp](https://meta.discourse.org/u/axp)\
**Post date:** [29 Outubro , 2015 10:00 UTC](https://meta.discourse.org/t/cant-ssh-to-container-on-fresh-install/35046/3 "2015-10-29T10:00:55Z")

</div>

Yes, I really need this for remote access.

---

<div class="post-metadata">

**Author:** ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)\
**Post date:** [29 Outubro , 2015 10:34 UTC](https://meta.discourse.org/t/cant-ssh-to-container-on-fresh-install/35046/4 "2015-10-29T10:34:11Z")

</div>

You could always SSH into the host, and then `enter` the container 😉

But of course, SSH into the container should also be working. Unluckily, I have no idea why it isn’t working for you.

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [30 Outubro , 2015 11:44 UTC](https://meta.discourse.org/t/cant-ssh-to-container-on-fresh-install/35046/5 "2015-10-30T11:44:24Z")

</div>

I removed most of the ssh hacks a while ago, they were getting a bit unwieldy, you could still mixin the ssh template and figure out how to wire it all up but it’s tricky

---

<div class="post-metadata">

**Author:** ![axp](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/axp/32/116685_2.png) [@axp](https://meta.discourse.org/u/axp)\
**Post date:** [30 Outubro , 2015 11:59 UTC](https://meta.discourse.org/t/cant-ssh-to-container-on-fresh-install/35046/6 "2015-10-30T11:59:02Z")

</div>

Thanks for info @sam!

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [30 Outubro , 2015 19:49 UTC](https://meta.discourse.org/t/cant-ssh-to-container-on-fresh-install/35046/7 "2015-10-30T19:49:22Z")

</div>