How to Configure Virtual Private Server

All of the supported VPS types at Jelastic (i.e. based on CentOS, Ubuntu and Windows) share the similar installation flow and the main management options. So, in order to get your Elastic VPS hosted and configured inside the Jelastic Cloud, follow the next instructions on how to:

How to Get Virtual Private Server

To setup your VPS inside the Jelastic Cloud, follow the next steps.

1. Click the Create environment button at the top pane to access environment topology wizard.

create cloud environment

2. In the opened window, enable the VPS block at the bottom left corner and choose the required server (CentOS 7.2 in our example) from the expendable options list.

centos vps install

Specify cloudlet limits for this node, scale it out (if required), select the preferred region (if several ones are available), type the name of environment and click on Create.

Note: When enabling VPS of any type, you’ll automatically get the Public IP address(es) attached to the corresponding node (one per instance).

Nevertheless, in case of a strict necessity, you can contact your hosting provider and request the option of running VPS with the internal IP only (e.g. when a special application infrastructure, that is partially inaccessible from outside, is required).

3. In a couple of minutes your new environment with the chosen virtual server will appear at the dashboard. You’ll also receive an email notification with its administration data (i.e. login / password credentials, attached Public IP and access URL).

Tips:

 
  • The attached Public IP address can be seen by expanding the Additionally list for your VPS node:

    vps public ip

  • In case you’ve lost access to your VPS server or just want to change the admin credentials for it, click the Reset password button (or Remote desktop > Reset RDP password for Windows VPS) next to the required node:

    vps reset password

    As a result, you’ll receive an email with new authentication data.

That’s it! Your VPS is up and running now.

ELastic VPS Horizontal Scaling

With Jelastic horizontal server scaling functionality, you can easily adjust the number of servers in your environment. Operating several same-type nodes in confines of a single environment highly increases its management capacities.

Upon scaling VPS, you’ll receive a set of independent servers, able to handle separate applications. In order to change the number of VPS instances, access the environment topology wizard and use the appropriate - and + buttons in the central pane to decrease/increase their count correspondingly.

scaling vps

Don’t forget to Apply changes you’ve made.

All the newly added VPS instances will clone the master node (i.e. the initially created container) with all its configurations. However, each node will have its own hostname and administration data, delivered via the corresponding emails.

Note: Every VPS node within a layer also has a separate own Public IP address attached, therefore you’ll be charged for usage of each IP separately. The exact cost of the Public IP usage can be found within the Quotas & Pricing information frame at your dashboard.

In order to start managing your VPS server(s) with the full root privileges granted, connect the required node via Public IP or Jelastic SSH Gate. Also, you can perform some basic configurations right through the dashboard with the help of the dedicated inbuilt tools.

Inbuilt Configuration Tools

The Jelastic Platform provides functionality to accomplish some of the common management operations directly through the dashboard, with the help of:

Note: For Windows VPS, configurations can be applied via the RDP connection only.


File Manager

The inbuilt Configuration Manager is designed to provide an easy and quick access to files, comprised in containers. It can be located by clicking on the Config button next to the required node (CentOS 7.2 in our example).

vps configuration

Use manager to apply the necessary changes to the configurations: create or upload new files, edit or delete the existing ones, setup mount points and manage exported data right via the intuitive dashboard UI.

Pay attention while modifying configuration files, since in case something will go wrong, the applied (i.e. saved) changes can’t be automatically reverted. 

Log Files

One more useful option for the efficient management of your VPS is Logs tracking. The corresponding dedicated dashboard section can be accessed with the same-named button next to the required node.

vps logs tracking

The available files (shown within the list to the left) contain the important information on your server lifecycle and could be useful, for example, while troubleshooting or debugging your app.

Tip: In order to keep only up-to-date information and cut unnecessary spends on the outdated logs storing, Jelastic performs automatic management of the log files list.

Thus, when a log file reaches 50 MB size, it is automatically compressed into .gz archive and moved to a special rotated_logs directory. During next 7 days, if this information is still required, you can enter your container via SSH and download the necessary archive for appropriate examination. And after this period (i.e. 7 days upon archive creation) is finished, archived logs are considered outdated and are automatically removed from a server.