Can't ssh to container on fresh install

Product Support

AI-generated summary

A user, axp, is experiencing issues with SSH access to a container after a fresh Discourse installation on Debian 8.1. Despite attempting to set the root password in app.yml, they are unable to connect via SSH. fefrei suggests using ./launcher enter app as an alternative to gain shell access. However, axp requires SSH for remote access. fefrei proposes SSHing into the host and then entering the container. sam mentions that SSH hacks were removed, making it challenging to configure SSH access, but suggests mixing in the SSH template as a potential solution.

1

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

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.

2

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 :slight_smile:

3

Yes, I really need this for remote access.

4

You could always SSH into the host, and then enter the container :wink:

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

5

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

6

Thanks for info @sam!