Platform Configuration

Myst can't connect? Should I test SSH connectivity?

Setting up SSH connectivity using username and password or SSH keypairs? Let's start by making you aware of how MyST connects via SSH.

SSH Connectivity between Servers

#

Source

Destination

1

MyST

AdminServer

2

AdminServer

AdminServer

3

AdminServer

Managed Server 1

4

AdminServer

Managed Server 2

5

AdminServer

Managed Server ...

Testing Connectivity

When running SSH commands to test connectivity ensure each command does not prompt and is passwordless.

NOTE: You may need to accept the fingerprint the first time. Once accepted, repeat the tests and ensure this time they are passwordless.

SSH Username and Password

  1. Test the connection #1 from MyST

  2. Test connection #2 from AdminServer to AdminServer

  3. Test connection #3 from AdminServer to Managed Server 1

  4. Test connection # from AdminServer to Managed Server 2

  5. And so on...

SSH Keypair

In this example you will need access to the id_rsa public key.

  1. Test the connection #1 from MyST

    1. ssh -i id_rsa [email protected]

  2. Test connection #2 from AdminServer to AdminServer

    1. ssh -i id_rsa [email protected]

  3. Test connection #3 from AdminServer to Managed Server 1

    1. ssh -i id_rsa [email protected]

  4. Test connection # from AdminServer to Managed Server 2

    1. ssh -i id_rsa [email protected]

  5. And so on...

SUDOERS Disable requiretty

If the logs throw errors about the myst remote agent then make sure to disable requiretty for the SSH user that MyST is connecting with.

See here for requiretty settings: https://docs.rubiconred.com/myst-studio/infrastructure/providers/hosts/‚Äč