1. How To Configure The Network

After you have received the access details for your project and have logged in to it, you should first configure the network where your instances will work. To do this, go to the PROJECTNETWORKNETWORKS section. To start the network creation process, click the CREATE NETWORK on the page that opens.

Network

In the NETWORK tab, you can enter any name in the NETWORK NAME field. In our example, this will be my_net_1.

Attention! To avoid any errors, all names should be written in Latin letters.

Create network

Next, you should add a subnet for your network. Enter any name in the SUBNET NAME field on the SUBNET tab. We recommend setting different names for the network and subnet — for example, my_subnet_1

Below, in the NETWORK ADDRESS field, specify the address for the subnet to be created, for example: 192.168.201.0/24. You can leave the GATEWAY IP field empty — in this case, the first address of the selected network will be used by default. Alternatively, you can provide a specific gateway IP address.

Create network

Please make sure that all data is correct, then open the SUBNET DETAILS tab. Check the ENABLE DHCP box. In the ALLOCATION POOLS field, enter the start and end values of the issued addresses separated by commas without spaces — for example, 192.168.201.10, 192.168.201.200. You can use our addresses as DNS servers, or any other. Addresses should be written as one per line.

Our DNS addresses for Europe:

  • 193.161.84.90
  • 188.226.189.38
  • 91.109.200.200
Create network

Then click CREATE, and the created network will appear in the list of networks.

You should create and configure a router to ensure the operability of the network you created. Click CREATE ROUTER in the PROJECTNETWORKROUTERS section.

ROUTERS

In the opened router creation window enter the router name (in Latin letters!) - for example, my_router_1. In the ADMIN STATE field, select UP, and in the EXTERNAL NETWORK field, select admin_floating_net, and then click CREATE ROUTER.

CREATE ROUTER

The router will appear in the list. To continue configuration, click on router name.

CREATE ROUTER

On the page that opens, select the INTERFACES tab, then ADD INTERFACE.

ADD INTERFACE

In the SUBNET field, select the previously created network and, if necessary, specify the IP address from the created range, then click SUBMIT.

ADD INTERFACE

This completes the network setup. Now you can create your first VM and configure security rules for it.

2. How To Create An Instance

Before creating an instance, it is first recommended to check the available resources that you can use in your project. To do this, open the COMPUTEOVERVIEW section. On the page that opens, you will see a LIMIT SUMMARY of your resources.

OVERVIEW

You can find all the VMs you created in the COMPUTEINSTANCES section. To create an instance, open the COMPUTEIMAGES section, then select the PUBLIC tab. Here you will see a list of all available images for creating VMs. Once you have decided on the desired image for the instance, click LAUNCH next to the device name. In our example, we used the image of a Debian 10.

IMAGES

In the instance creation window that opens, enter the desired VM name in the INSTANCE NAME field, which will also be used as the hostname, for example, Debian_test. You can increase the number of created instances in the COUNT field — in this case, they will be allocated to the corresponding indexes.

Launch an instance

In the SOURCE menu item (on the left), select CREATE NEW VOLUME and set the volume size. You may also change the image that the VM will be created from, if required.

Launch an instance

In the FLAVOR menu item, please select a template based on which resources will be issued for the VM. If a template exceeds the resources available to you, an exclamation mark will appear next to it. To select a template, click + next to it.

Launch an instance

If you are creating an instance based on a Linux image, you should create a key pair in the KEY PAIR menu section on the left. Without this, you won't be able to connect to the created VM via SSH. You can import an existing key pair using the IMPORT KEY PAIR. If you want to create a new key pair, click on the CREATE KEY PAIR and enter the name in Latin letters (for example, debiankey2). Once created, the key file will be downloaded automatically by your browser.

Launch an instance

Linux/Unix only: if you plan to connect to the VM via the console and you do not need SSH access, you can add the following script to the CUSTOMIZATION SCRIPT field in the CONFIGURATION section:

#cloud-config

password: userpassword

chpasswd: { expire: False }

ssh_pwauth: True

where USERPASSWORD is your connection password.

Launch an instance

After you have finished making changes, click LAUNCH INSTANCE. Your VM will appear in the list of instances, and after a while its status will change to ACTIVE. The next step is to associate a white IP address with your instance. To do this, select ASSOCIATE FLOATING IP from the drop-down menu next to the name of your instance.

ASSOCIATE FLOATING IP

In the window that opens, click «+» under IP ADDRESS.

ASSOCIATE FLOATING IP

In the window that opens, click ALLOCATE IP, and then you will be redirected to the previous page, where an available white IP will appear in the IP ADDRESS drop-down list, which you can associate with the port of your instance. Click ASSOCIATE to complete the configuration.

The user name for Linux instances is the same as the distribution name: DEBIAN for all versions of Debian, FEDORA for Fedora, etc.

If your VM is Windows-based, open the COMPUTEINSTANCES section and click the name of the corresponding instance. On the page that opens, go to the CONSOLE tab and configure the system.

CONSOLE

Your cloud VM is now successfully created, but you still don't have access to it via SSH or RDP. To connect to an instance, you should make changes to the current security group.

3. How To Manage Security Groups

To change security group rules — create new ones and edit existing ones — open the COMPUTEACCESS & SECURITY section.

Click MANAGE RULES next to the DEFAULT rule.

ACCESS & SECURITY

On the page that opens, select ADD RULE.

ADD RULE

In the window that opens, select the required parameter from the RULE drop-down list: SSH for Linux or RDP for Windows.

Attention! You should only change the other fields if you are absolutely sure that these actions are necessary.

Then click ADD and the rule will be saved.

ADD RULE

You can create separate security groups for different VMs. You can do this directly during the instance creation process from the corresponding menu section. You may also change the security group for existing instances in the COMPUTEINSTANCES section. To do this, select EDIT SECURITY GROUPS in the drop-down list next to the desired machine.

INSTANCES

You are now able to easily connect to the VM you created via SSH or RDP.

If you rent or host several servers within our data center, you can combine them into a single closed network based on Private VLAN (PVLAN) technology.

Two servers can be directly connected using an Ethernet cable. This service is provided free of charge.

If you have more than two servers that need to be combined, you will need switches with the configuration of separate VLAN. This service is paid. The current cost of connecting a Private VLAN is provided on the RENT A SERVER and HOST A SERVER pages in the ADDITIONAL SERVICES section.

Please note that a Private VLAN can be set up on either a 100 Mbit/s port or a 1 Gbit/s port.

By default, each server has two network ports: LAN-0 and LAN-1. One port is normally used for Internet access, whilst the second can be configured with a Private VLAN. However, we can install additional network cards, for example to aggregate ports into LACP trunks.

For your high-load projects (cluster systems, disk arrays, etc.), we can offer you optical switches with ports of up to 10 Gbit/s, on individual terms.

Our specialists will set up the Private VLAN within one day. Please contact our technical support to order a service.

If your browser fails to load a website showing the following message:

Your connection to this server has been blocked in this server's firewall.

You need to contact the server owner for further information.

Your blocked IP address is XXX.XXX.XXX.XXX

This server's hostname is YYY.YYY.YYY.YYY

where XXX.XXX.XXX.XXX is your IP-address, then we request that you copy the message and send it to our technical support. You may also only specify the IP address mentioned in the message and the address of your website (your domain). We will find the exact reason why your IP address is blocked and unblock it.

Attention! Showing this message does not mean that the actual website is blocked, but that the specific IP address from which you are trying to access the website has been blocked, for some reason. The website can still be accessed from other IP addresses.

When working with the IPMI View program, while connecting to the server console, you may encounter the CONNECTION FAILED error. To restore the server's connection, follow these steps:

  1. Exit the IPMI View.
  2. Log in to the web interface of the IPMI controller using the same details (please note that the IPMI web address and your authorization data are available in your Personal account and in the email that we sent to you when granting access to the server).
  3. Go to the MAINTENANCE tab.
  4. In the left-hand side menu, select IKVM RESET and click RESET in the window that opens.
  5. Exit the web interface.
  6. Start the IPMI View and try to connect to the server again.
Maintenance

Attention! These actions will not restart the server itself, only the IPMI controller.

The current version of the IPMI View is available here.

When working with a remote access PuTTY client in Windows, an error may occur due to incompatibility of key formats:

Unable to use key file (OpenSSH SSH-2 private key (old PEM format))

To eliminate this error, the key must be converted by the PuTTYgen tool. Download the utility through the website, open it, and select the "Conversions" tab in the top panel. In the menu that opens, press "Import key" and select the key.

Import key

To convert Keys after import, click "Save private key." The key will be saved in a new format (.ppk) with the selected name. If necessary, you can also set the password for the key.

After that, you can connect with a new key to your servers or virtual machines in our data center.

Every dedicated server you ordered includes unlimited KVM access (KVM stands for Keyboard, Video, and Mouse, also it can be named KVM over IP — a virtual remote console for your server). Using this you can work with BIOS and OS directly without our tech support.

For all standard dedicated server plans KVM Virtual Media feature is available. It allows you to upload to the server any files — it’s usually used for ISO images for OS installation. You can then mount it via virtual DVD-ROM.

You can also power cycle your server via KVM web-interface, IPMIview app, or My account.

You can always add authorized users to Your account. Those users would be able to manage services and payments as well as send support requests via tickets and webchat.

To add a new user just click on the Add user button at the top right of the users’ list.

Add user

You’ll need to fill out the following mandatory fields: login and password, email or phone number, name, and last name. As an option, you can add more information.

Please note, that when the new user addition form is opened, some fields may be already filled out. It depends on your browser’s autofill settings, for example, login and password may be filled out with your ones. It makes sense to verify and update it as needed before submitting the form.

Users

Click on the Add user button at the bottom, and the new user should appear in the authorized users’ list.

Users

To delete a user, please click on Remove button in the corresponding row in the users’ list.

IP address for ping/traceroute:

176.74.219.29


Testing files:

You can manage access to your server’s IPMI from the Internet in your Account at Host-telecom.com. Access restriction is implemented due to security reasons.

Here’s what you can do:

  1. Completely block access to the IPMI address
  2. Allow access from specific IP(s) and set the expiration time.
  3. Allow access from specific IP(s) permanently (no expiration date)
  4. Add both temporary and permanent access rules
  5. Allow unrestricted access (we strictly do not recommend this option due to security reasons!)

Once you logged in your Account you can use "IPMI management" menu (picture 1).

IPMI management

You get a list of all your servers equipped with IPMI controller and can select a checkbox for the server you want to change access to. To open the access configuration please click on "Open/prolong access" button (picture 2).

Open/prolong access

Please note that servers without IPMI controller are not displayed on this page.

You can choose between the temporary, permanent or unlimited type of access (1) to be open and also input the IP address (2). The system automatically fills out your current IP for your convenience. You can manually set any other IP though (picture 3).

You can add multiple IPs - one in a row, or add (/24) subnet if you provide 3 out of 4 octets (for instance, 193.161.84).

After you click on the "Run" button, all changes take place after 1 minute.

Run

Set the period of time (3) for the temporary access (by default it’s 30 minutes, the maximum is 24 hours).

Please note that for your convenience you can create lists of IP address and then use it for providing/revoking access in bulk (4).

You can also update the list of IPs and extend access time if it’s already configured for some server. ‘New’ time is added to the remainder and applied to the whole IP address list.

Be careful! Technically you can allow unrestricted access to your server’s IPMI, but we strongly recommend not to do that because of security reasons. In this case, your IPMI address is accessible from any IP on the Internet.

You can combine temporary (if it’s required occasionally) and permanent (for IPs that you constantly use to operate the server) types of access for a server.

If you configure both temporary and permanent access to your server from the same IP, it’s granted with permanent access.

To revoke any type of access, please select server(s) and click on "Close access" button. Changes take place after 1 minute (picture 4).

Close access

You can use SuperMicro IPMIView app to work with IPMI KVM-console. It has a richer feature set compared to web-interface. It’s available for Linux and Windows and as a cross-platform Java app.

The tool is available on the official SuperMicro website (sign in required) or FTP: ftp:// ftp.supermicro.com/utility/IPMIView/

You need Java support on your machine to use KVM console, no matter what you use - web-interface or IPMIView.

If you have issues with the IPMI access, email us at support@host-telecom.com

You can face the following issues if IPMI web-interface of your servers freezes:

  • Virtual Media ISO files mounting works incorrectly
  • IPMI web-interface does not work or works incorrectly
  • Java applet does not start or starts incorrectly
  • Java-applet doest not connect to console or connects incorrectly

You can reset IPMI using your account’s dashboard or IPMIView app

How to reset IPMI using your account dashboard

Use the following steps to reset IPMI from your account’s dashboard:

  1. log in to your account
  2. Go to Servers and equipment menu (on the left)
  3. Push reset button in actions column
  4. Create IPMI cold reset task and run it
create task

Attention! You will reset IPMI controller only, not your server.

How to reset IPMI using IPMIView app.

You can download IPMIView using official website or FTP-server.

UI may slightly differ in different versions

IPMI Device

Run IPMIView app and then choose IPMI device tab at the bottom.

On the screen you'll see Cold Reset button. If you push it, the IPMI controller will be reset (your server will be not).

Cold Reset
3 - 4 1 2 3 4

Guides

Spelling error report

The following text will be sent to our editors: