The deploy user's sudo password is emailed to you when your server gets created for the first time.
This email might go to your spam folder, so check there if you didn't see it in your inbox. Keep this password somewhere safe as you'll need it if you plan to install software on your server.
Each server has a separate deploy user password to add some additional security.
You can also reset the deploy user's sudo password on the Server's SSH Keys tab. Just click "Reset Password" and your new password will be emailed to you.
To become root, you can run
Hatchbox is setup so you login as the deploy user and use
sudo to run commands as root.
If you've forgotten your server's sudo password, check your email. Hatchbox sends you the password when the server gets created. You can look that up and use that password to login as deploy and run commands as sudo.
To reset the deploy user's sudo password, visit your cluster's Server page and click on SSH Keys. There you'll see a button called Reset Deploy Password. This will email you new a sudo password for the deploy user. Login to the server as deploy and run you can use this new password to run
sudo commands. To become the root user, you can run
If you reset the password on your hosting provider, you will probably break Hatchbox. We don't recommend doing this. If you need to reset the password, see the previous question.
First, you'll have to login to the server as root and set the password. You'll probably need to do this through the online terminal in the browser at your hosting provider.
Once done, you can try Hatchbox again.
If Hatchbox still fails to connect to the server, you may need to add the Hatchbox SSH key to the server's root user. You can find the key and instructions for this on the server's SSH Keys page.
First, you'll need to add an SSH key to your server. You can do this by visiting the Server's SSH Keys tab.
You can also add SSH keys account-wide to have them automatically installed on new servers.
Once you're done, you can open up your terminal and run the following command:
X.X.X.X with your server's public IP address.
You will then be logged into your server and you should see a list of instructions on how to access your app folders and Rails console.
Welcome to Ubuntu 16.04.4 LTS (GNU/Linux 4.4.0-127-generic x86_64)* Documentation: https://help.ubuntu.com* Management: https://landscape.canonical.com* Support: https://ubuntu.com/advantageGet cloud support with Ubuntu Advantage Cloud Guest:http://www.ubuntu.com/business/services/cloud__ __ __ __ ___/ // /___ _ / /_ ____ / / / _ ) ___ __ __/ _ // _ `// __// __// _ \ / _ |/ _ \ \ \ //_//_/ \_,_/ \__/ \__//_//_//____/ \___//_\_\The following apps deployed to this server:* myappTo open the console:cd ~/myapp/current && bundle exec rails cTo read the logs:tail ~/myapp/current/log/production.log
If your server is marked as failed, that means something failed to install when your server was setting up. This might be a broken package or simply trouble connecting over SSH.
You can click on the failed server and click the "Retry" button to have Hatchbox try to provision your server again.
If it fails again, contact Support and let us know which server is failing to setup and we'll get you sorted out.