You will need this password if you want to run sudo commands or become Root on your server by running "sudo su" - in this case we recommend you enable Passwordless Sudo in your server which you can do on the Shell Users screen in the Webdock Dashboard. This is especially true for the default "admin" user we create for you in our LAMP or LEMP stacks, as the password for this user is only visible if you log in to the Webdock dashboard online. Pro tip: More often than not you do not know the Sudo password for your Shell user.Now you can use the ConnectBot Icon in the bottom navigation bar on the main Server information screen or just tap the Shell User you want to log in with from the Shell Users list for your Server.Tap the shell user you want to connect with, or create a new Shell User and Assign the Public Key for your ConnectBot - you only need to do this once for each Shell User you want to connect with.Go to any server in the Webdock App and go to the Shell Users screen by swiping right a few times.Now that you have installed ConnectBot on your device and copied the Public Key for your ConnectBot installation to your Webdock Account you can now proceed to connect to a Server. Connecting with a Shell user to a Webdock Server with ConnectBot Now you have ConnectBot set up ready to go and your Key has been added to your Webdock Account and is ready to be deployed to any Shell User on any one of your Webdock Servers. Name your Public Key anything you like in the Webdock App and paste the Public Key you just copied from ConnectBot into the appropriate field in the Webdock App.Open the Webdock App and go to Account -> Public Keys and add the Public Key to your Webdock Account by tapping the + Icon down in the bottom right corner.Once the Keypair has been generated, copy the Public Key by long-pressing on the entry in the ConnectBot List of keys.Just go with the defaults on screen, give it a name, no need to add a password unless you are extra paranoid. Start the ConnectBot App and Generate an SSH Keypair by going to Manage Pubkeys in the context menu (three small dots) in the top right corner of the screen.To connect to the application enter the application FQDN in the URL line of your browser or connect through the Management Platform.In order to connect with SSH you need a 3rd party application called ConnectBot.Policy : Leave blank, or choose a policy that was previously created and matches your needs.Access Groups : State the names of the user groups which have access to the SSH application.If a passphrase is a set along with SSH key, enter it as well, otherwise leave blank. Note that a certificate typically starts with a prefix and a suffix such as the following: -BEGIN RSA PRIVATE KEY. Private Key/Username/Passphrase: Enter your RSA-SSH key under Private Key with a correlating username (according to user settings predefined in the server).You will not be required to enter any parameter with the login. Username and Password: Enter one set of credentials as predefined on the server.Authentication : If disabled, you'll need to enter your credentials as predefined on the server with every login.URL Alias (Optional) : See further instructions here.Display Application Icon at Login Screen : Choose according to your preference.Network : Choose the network that contains the gateway from which you created a tunnel to the environment that hosts the server you'd like to connect to.Host : Enter the internal IP address of the server to which you'd like to connect.Icon : Use default or choose an icon of your own choice.Application Name : Enter a name of your choice.Go to the Applications tab in the Perimeter 81 Platform.Make sure you are familiar with the server's authentication methods (username and password or SSH keys) and that you have a tunnel connecting your network and the environment that hosts the server before you begin. This article describes how to configure an SSH connection to a remote server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |