How To Securely Manage Secrets with HashiCorp Vault on Ubuntu 16.04
0

Introduction

The Vesta Management Panel is a free, open supply management panel with web site, e-mail, database, and DNS functionalities. On this tutorial you’ll set up the management panel on an Ubuntu or CentOS server, replace the default admin interface port, and discover ways to migrate person information from an current set up.

Notice: On April eighth, 2018, a vulnerability was found in VestaCP that allowed attackers to compromise host programs and ship malicious visitors concentrating on different servers. In consequence, DigitalOcean has disabled VestaCP’s default port 8083. This tutorial will replace the set up to make use of port 5600 as a substitute. For extra updated info on this vulnerability, please learn this Neighborhood Q&A publish.

Conditions

The next assets are required to finish this tutorial:

  • An Ubuntu 16.04 or CentOS 7 server
  • A website title pointed at your server. How To Set Up a Host Title with DigitalOcean will present you tips on how to handle a website with the DigitalOcean management panel. We’ll use panel.instance.com all through this tutorial
  • Two A data pointing ns1.instance.com and ns2.instance.com to your server

Putting in VestaCP

Log into your server through SSH. As a result of VestaCP handles the creation of particular person person accounts, this tutorial will assume you are logging in because the root person to do the preliminary setup.

After logging in, transfer to the /tmp short-term listing and obtain the set up script:

cd /tmp
curl -O https://assets.digitalocean.com/vesta/install-vesta-do.sh

This script is a wrapper across the official VestaCP set up script. You’ll be able to open it in your favourite textual content editor to see what it does. It makes use of the official script to put in the software program, then updates the admin interface to make use of port 5600.

Make the script executable:

chmod +x install-vesta-do.sh

Lastly, run the script to put in VestaCP. You might go in any of the choices supported by the official set up script, which you could find on VestaCP’s set up web page. We’ll use the --force choice, as a result of in any other case the installer might complain about an current admin group on some machines:

./install-vesta-do.sh --force

The script will interactively ask a couple of questions, then take round 5–15 minutes to finish the set up. The URL on your admin interface can be printed out, together with the admin login info:

Output

Congratulations, you could have simply efficiently put in Vesta Management Panel https://panel.instance.com:8083 username: admin password: a-random-password

Notice: these preliminary URLs can be incorrect, as they’re going to nonetheless be utilizing port 8083. The final line of the set up output must be

Configuring to make use of port 5600 as admin port

Replace all port 8083 references to port 5600 earlier than trying to attach. The instance URL can be https://panel.example.com:5600, as an illustration. After the preliminary set up, any subsequent emails to your customers will use the right port.

VestaCP is now up and working in your server. When you have an current VestaCP set up, proceed on to the following step, the place we’ll migrate your person information to the brand new server.

Migrating VestaCP Consumer Knowledge Between Servers

VestaCP comes with some scripts to assist again up and restore person information. We’ll migrate the admin person utilizing these scripts.

On the server you’re migrating from, use v-backup-user to export the admin backup:

v-backup-user admin

Notice: Should you get a command not discovered error when working the backup program, chances are you’ll have to replace your PATH by working:

export PATH=$PATH:/usr/native/vesta/bin

That is dealt with mechanically in the event you log off and again in after putting in VestaCP.

The command will output some standing info and the filename of your backup:

Output

. . . -- SUMMARY -- 2018-04-10 17:45:42 Native: /backup/admin.2018-04-10_17-45-42.tar 2018-04-10 17:45:42 Measurement: 1 MB 2018-04-10 17:45:42 Runtime: 1 minute

Pay attention to the backup file, highlighted above. Yours can be totally different relying on the present time and the username you are backing up. To switch this file to your new server, we’ll use the scp utility.

Should you’re utilizing password authentication on the brand new server, it is best to switch the file straight from the previous server to the brand new, like so:

scp /backup/admin.2018-04-10_17-45-42.tar [email protected]panel.instance.com:/backup/

This received’t simply work in the event you use SSH keys as a substitute of passwords. In that case it is most likely greatest to obtain the file to your native machine, then add it to the brand new server. In your native command line, do the next:

scp [email protected]old-server.instance.com:/backup/admin.2018-04-10_17-45-42.tar /tmp/
scp /tmp/admin.2018-04-10_17-45-42.tar [email protected]panel.instance.com:/backup/

Now, with the backup .tar file uploaded to the brand new server’s /backup listing, log again in to the brand new server and use the v-restore-user command to finish the method:

v-restore-user admin admin.2018-04-10_17-45-42.tar

The command will output a abstract of the objects it has restored. Your migration of the admin person is now full.

Conclusion

On this tutorial you put in the VestaCP management panel, up to date the port of its default admin interface, and migrated the admin person from a preexisting set up. To be taught extra about utilizing the VestaCP software program to arrange web sites and e-mail, please check with steps three and four of How To Set up VestaCP and Set Up a Website on Ubuntu 14.04. You may as well check with the official documentation.

Relive the 1990s on Home windows 10 with the newly open sourced File Supervisor

Previous article

What Router Settings Ought to You Change?

Next article

You may also like

Comments

Leave a reply

Your email address will not be published. Required fields are marked *