Cloud servers from $4/mo - Grab the Deal! Let’s start ->
How to Configure an Additional IP as an Alias in Ubuntu
Ubuntu
29.11.2024
Reading time: 6 min
Share
In the network administration world, the task of setting up additional IP addresses on a single network interface is commonly performed. The technique of IP aliasing, which is a system for a device to reply to several IP addresses on one network interface, penetrates this model. All Ubuntu users should be familiar with modifying and applying these settings to ensure robust networking administration.
This guide will detail the methods of creating an extra IP address in Ubuntu as an alias for both the versions of Ubuntu 24.04 and 22.04.
Prerequisites
Obviously, one first needs to set up the system in a way that would allow for the manipulation of all IP addresses over the same network, using Ubuntu. Here is the list:
- A system running either Ubuntu 24.04 or Ubuntu 22.04
- Admin access to the system (
sudoprivileges) - Basic knowledge of command-line interface operations
- An additional IP address assigned by a network administrator or ISP
- Network interface name information (e.g.,
eth0,ens3)
When troubleshooting problems, we are in danger of causing even more difficulty, as network interfaces provided by networks are not reliable. With this in mind, it would be wise to keep a backup of the configuration files before proceeding with the changes.
Configuring an Additional IP Address within Ubuntu 24.04
Ubuntu 24.04, the latest long-term support release, uses Netplan for network configuration. This configuration is also applicable for Ubuntu 22.04 and beyond.
Netplan is a utility for configuring networking on Linux systems. Here's how to create an additional IP address:
- Check the Network Interface
Primarily, it is necessary to define the network interface that will carry the new address. You can achieve this by running the following command:
ip addr showThe output of this command will display all the interfaces. Find the name of the interface (e.g. ens3, eth0) currently in use.
- Edit the Netplan Configuration File
Normally Netplan configuration files are found in the /etc/netplan/ directory. The file name may be different but most of them end with a .yaml extension. To change the file, use a text editor with root privileges:
sudo nano /etc/netplan/50-cloud-init.yaml- Insert the New IP Address
In the YAML file, add the new IP address under the addresses section of the appropriate network interface. The configuration may appear like this:
network:
version: 2
renderer: networkd
ethernets:
eth0:
addresses:
- "195.133.93.70/24"
- "166.1.227.189/24" #New IP address
- "192.168.1.2/24" #Private IP address
nameservers:
addresses:
- "1.1.1.1"
- "1.0.0.1"
dhcp4: false
dhcp6: false
routes:
- to: "0.0.0.0/0"
via: "195.133.93.1"
- Apply the Changes
Upon saving your edits, you need to apply the new version of the configuration by running this command:
sudo netplan apply- Validate the Configuration
After completing the steps above, you will need to repeat the ip addr show command to confirm that the new IP address is in place. Now the output of this command should also include the new IP address.
Additional Considerations
- Persistent Configuration
The choices made by Netplan are stable and will last through the restart of the device. But, it's a good idea to verify the configuration with a system reboot to make sure everything goes well after the restart.
- Firewall Configuration
When adding a new IP address, you may need to update the firewall rules. Ubuntu traditionally uses UFW (Uncomplicated Firewall). To avoid blocking the new IP, you will have to create new rules to UFW.
- Network Services
If the system has some services running which are linked to specific IP addresses, then you must update their configurations to recognize and utilize the new IP address as well.
- IPv6 Considerations
The above examples talk about IPv4. If you have to use IPv6 addresses, then the procedure is relatively the same; you will have to use a different style of address though. Netplan supports both IPv4 and IPv6 configurations.
Troubleshooting
In case of issues emerging during the configuration stage, try:
- Check for syntax errors in the YAML file with the command:
sudo netplan --debug generate. - Ensure that there are no conflicts with other devices using the same IP address on the network.
- Verify correct setting of the subnet mask and the gateway.
- Check the system logfile for error messages:
journalctl -xe.
Advanced IP Aliasing Techniques
Network administrators can see how advanced IP aliasing plays a key role in improving network management: virtual interfaces make it possible to have several logical interfaces on a physical network interface, wherein all have their IP and network settings.
- Dynamic IP Aliasing
There are cases where network administrators would have to implement dynamic IP aliasing. With the help of scripts, it is possible to add or remove IP aliases according to certain conditions or occurrences. For example, a script can be made to insert an IP alias whenever a particular service starts and remove it every time the service stops.
- IP Aliasing in Containerized Environments
The popularity of containerization in the present age necessitates having IP aliasing in order to control network configuration of Docker containers and any other containerized applications. In such cases, IP aliases are quite often employed to expose multiple services on a container at different IP addresses or assist containers to communicate with one another.
- Docker Network Aliases
In Docker, network aliases can be used to allow multiple containers to respond to the same DNS name on a custom network. Among other things, this is indispensable in microservices architectures where service discovery is a very important issue.
Security Implications of IP Aliasing
Though IP aliasing has a multitude of advantages, the issue of security deserves also to be looked into. Among other things, the more IP addresses you put, the larger the possible security breach of a system. The network administrators must guarantee the applications are protected with:
- Configurations of a firewall that will secure all the IP aliases
- Intrusion Detection Systems (IDS) to record the traffic of all IP addresses
- Periodically checking the use and need of each IP alias
- Enabling of appropriate security tools for those services bound to specific IP aliases
Conclusion
Putting a new IP address as an alias into Ubuntu is a highly efficient process as their utility of Netplan helps greatly. Whether you are using Ubuntu 24.04 or 22.04, the steps remain the same including editing the Netplan configuration file, adding the new IP address, and applying the changes. A system with multiple IP addresses on a single network interface of a single computer can be used to do different tasks on such a network. The ability to respond to several IP addresses on one network interface becomes very useful in several networking situations.
Through these steps, you can increase the Ubuntu computer networking capabilities quickly and effectively. The sequence is always to first back up existing configurations then to make changes followed by in-depth test post-installation. With these skills, a network infrastructure manager or an IT technician can effectively manage and optimize his Ubuntu-powered network infrastructure to cater to diverse networking requirements.
Ubuntu
29.11.2024
Reading time: 6 min
Share
Similar
Wordpress
How to Install WordPress with Nginx and Let’s Encrypt SSL on Ubuntu
WordPress is a simple, popular, open-source, and free CMS (content management system) for creating modern websites. Today, WordPress powers nearly half of the websites worldwide. Hostman offers Wordpress cloud hosting with quick load times, robust security, and simplified management.
However, having just a content management system is not enough. Modern websites require an SSL certificate, which provides encryption and allows using a secure HTTPS connection.
This short guide will show how to install WordPress on a cloud server, perform initial CMS configuration, and add an SSL certificate to the completed site, enabling users to access the website via HTTPS.
The Nginx web server will receive user requests and then proxied to WordPress for processing and generating response content.
A few additional components are also needed: a MySQL database, which serves as the primary data storage in WordPress, and PHP, which WordPress is written in.
This technology stack is known as LEMP: Linux, Nginx, MySQL, PHP.
Step 1. Creating the Server
First, you will need a cloud server with Ubuntu 22.04 installed.
Go to the Hostman control panel.
Select the Cloud servers tab on the left side of the control panel.
Click the Create button.
You’ll need to configure a range of parameters that ultimately determine the server rental cost. The most important of these parameters are:
The operating system distribution and its version (in our case, Ubuntu 22.04).
Data center location.
Physical configuration.
Server information.
Once all the data is filled in, click the Order button.
Upon completion of the server setup, you can view the IP address of the cloud server in the Dashboard tab, and also copy the command for connecting to the server via SSH along with the root password:
Next, open a terminal in your local operating system and connect via SSH with password authentication:
ssh root@server_ip
Replace server_ip with the IP address of your cloud server. You will then be prompted to enter the password, which you can either type manually or paste from the clipboard.
After connecting, the terminal will display information about the operating system. Now you can create a user with sudo priviliges or keep using root.
Step 2. Updating the System
Before beginning the WordPress installation, it’s important to update the list of repositories available through the APT package manager:
sudo apt update -y
It’s also a good idea to upgrade already installed packages to their latest versions:
sudo apt upgrade -y
Now, we can move on to downloading and installing the technology stack components required for running WordPress.
Step 3. Installing PHP
Let's download and install the PHP interpreter.
First, add a specialized repository that provides up-to-date versions of PHP:
sudo add-apt-repository ppa:ondrej/php
In this guide, we are using PHP version 8.3 in FPM mode (FastCGI Process Manager), along with an additional module to enable PHP’s interaction with MySQL:
sudo apt install php8.3-fpm php-mysql -y
The -y flag automatically answers “yes” to any prompts during the installation process.
To verify that PHP is now installed on the system, you can check its version:
php -v
The console output should look like this:
PHP 8.3.13 (cli) (built: Oct 30 2024 11:27:41) (NTS)Copyright (c) The PHP GroupZend Engine v4.3.13, Copyright (c) Zend Technologies with Zend OPcache v8.3.13, Copyright (c), by Zend Technologies
You can also check the status of the FPM service:
sudo systemctl status php8.3-fpm
In the console output, you should see a green status indicator:
Active: active (running)
Step 4. Installing MySQL
The MySQL database is an essential component of WordPress, as it stores all site and user information for the CMS.
Installation
We’ll install the MySQL server package:
sudo apt install mysql-server -y
To verify the installation, check the database version:
mysql --version
If successful, the console output will look something like this:
mysql Ver 8.0.39-0ubuntu0.22.04.1 for Linux on x86_64 ((Ubuntu))
Also, ensure that the MySQL server is currently running by checking the database service status:
sudo systemctl status mysql
The console output should display a green status indicator:
Active: active (running)
MySQL Security
This step is optional in this guide, but it’s worth mentioning. After installing MySQL, you can configure the database’s security settings:
mysql_secure_installation
This command will prompt a series of questions in the terminal to help you configure the appropriate level of MySQL security.
Creating a Database
Next, prepare a dedicated database specifically for WordPress.
First, log in to MySQL:
mysql
Then, execute the following SQL command to create a database:
CREATE DATABASE wordpress_database;
You’ll also need a dedicated user for accessing this database:
CREATE USER 'wordpress_user'@'localhost' IDENTIFIED BY 'wordpress_password';
Grant this user the necessary access permissions:
GRANT ALL PRIVILEGES ON wordpress_database.* TO 'wordpress_user'@'localhost';
Finally, exit MySQL:
quit
Step 5. Downloading and Configuring Nginx
The Nginx web server will handle incoming HTTP requests from users and proxy them to PHP via the FastCGI interface.
Download and Installation
We’ll download and install the Nginx web server using APT:
sudo apt install nginx -y
Next, verify that Nginx is indeed running as a service:
systemctl status nginx
In the console output, you should see a green status indicator:
Active: active (running)
You can also check if the web server is functioning correctly by making an HTTP request through a browser. Enter the IP address of the remote server in the address bar, where you are installing Nginx. For example:
http://166.1.227.189
If everything is set up correctly, Nginx will display its default welcome page.
For good measure, let’s add Nginx to the system’s startup list (though this is typically done automatically during installation):
sudo systemctl enable nginx
Now, you can proceed to make adjustments to the web server configuration.
Configuration
In this example, we’ll slightly modify the default Nginx configuration. For this, we need a text editor. We will use nano.
sudo apt install nano
Now open the configuration file:
sudo nano /etc/nginx/sites-enabled/default
If you remove all the comments, the basic configuration will look like this:
server {
listen 80 default_server;
listen [::]:80 default_server;
root /var/www/html;
index index.html index.htm index.nginx-debian.html;
server_name _;
location / {
try_files $uri $uri/ =404;
}
}
To this configuration, we’ll add the ability to proxy requests to PHP through FastCGI:
server {
listen 80 default_server;
listen [::]:80 default_server;
root /var/www/html;
# added index.php to index files
index index.html index.htm index.nginx-debian.html index.php;
# specify the domain name to obtain an SSL certificate later
server_name mydomain.com www.mydomain.com;
location / {
# try_files $uri $uri/ =404;
# direct root requests to /index.php
try_files $uri $uri/ /index.php?$args;
}
# forward all .php requests to PHP via FastCGI
location ~ \.php$ {
include snippets/fastcgi-php.conf;
fastcgi_pass unix:/run/php/php8.3-fpm.sock;
}
}
Note that the server_name parameter should contain the domain name, with DNS settings including an A record that directs to the configured server with Nginx.
Now, let’s check the configuration syntax for errors:
sudo nginx -t
If everything is correct, you’ll see a confirmation message in the console:
nginx: the configuration file /etc/nginx/nginx.conf syntax is oknginx: configuration file /etc/nginx/nginx.conf test is successful
Then, reload the Nginx service to apply the new configuration:
sudo systemctl reload nginx
Step 6. Installing an SSL Certificate
To obtain an SSL certificate from Let’s Encrypt, we’ll use a special utility called Certbot. In this guide, Certbot will automate several tasks:
Request the SSL certificate.
Create an additional Nginx configuration file.
Edit the existing Nginx configuration file (which currently describes the HTTP server setup).
Restart Nginx to apply the changes.
Obtaining the Certificate
Like other packages, install Certbot via APT:
sudo apt install certbotsudo apt install python3-certbot-nginx
The first command installs Certbot, and the second adds a Python module for Certbot’s integration with Nginx. Alternatively, you can install python3-certbot-nginx directly, which will automatically include Certbot as a dependency:
sudo apt install python3-certbot-nginx -y
Now, let’s initiate the process to obtain and install the SSL certificate:
sudo certbot --nginx
First, Certbot will prompt you to register with Let’s Encrypt. You’ll need to provide an email address, agree to the Terms of Service, and optionally opt-in for email updates (you may decline this if desired).
Then, enter the list of domain names, separated by commas or spaces, for which the certificate should be issued. Specify the exact domain names that are listed in the Nginx configuration file under the server_name directive:
mydomain.com
www.mydomain.com
After the certificate is issued, Certbot will automatically configure it by adding the necessary SSL settings to the Nginx configuration file:
listen 443 ssl; # managed by Certbot
# RSA certificate
ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
# Redirect non-https traffic to https
if ($scheme != "https") {
return 301 https://$host$request_uri;
} # managed by Certbot
So, the complete Nginx configuration file will look as follows:
server {
listen 80 default_server;
listen [::]:80 default_server;
listen 443 ssl; # managed by Certbot
# RSA certificate
ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
root /var/www/html;
index index.html index.htm index.nginx-debian.html index.php;
server_name domain.com www.domain.com;
# Redirect non-https traffic to https
if ($scheme != "https") {
return 301 https://$host$request_uri;
} # managed by Certbot
location / {
# try_files $uri $uri/ =404;
# direct root requests to /index.php
try_files $uri $uri/ /index.php?$args;
}
# forward all .php requests to PHP via FastCGI
location ~ \.php$ {
include snippets/fastcgi-php.conf;
fastcgi_pass unix:/run/php/php8.3-fpm.sock;
}
}
Automatic Certificate Renewal
Let’s Encrypt certificates expire every 90 days, so they need to be renewed regularly. Instead of manually renewing them, you can set up an automated task.
For this purpose, we’ll use Crontab, a scheduling tool in Unix-based systems that uses a specific syntax to define when commands should run.
Install Crontab:
sudo apt install cron
And enable it:
sudo systemctl enable cron
Now open the Crontab file:
crontab -e
Add the following line to schedule the Certbot renewal command:
0 12 * * * /usr/bin/certbot renew --quiet
In this configuration:
The command runs at noon (12:00) every day.
Certbot will check the certificate’s expiration status and renew it if necessary.
The --quiet flag ensures that Certbot runs silently without generating output.
Step 7. Downloading WordPress
In this guide, we’ll use WordPress version 6.5.3, which can be downloaded from the official website:
wget https://wordpress.org/wordpress-6.5.3.tar.gz
Once downloaded, unpack the WordPress archive:
tar -xvf wordpress-*.tar.gz
After unpacking, you can delete the archive file:
rm wordpress-*.tar.gz
This will create a wordpress folder containing the WordPress files.
Most core files are organized in the wp-content, wp-includes, and wp-admin directories. The main entry point for WordPress is index.php.
Moving WordPress Files to the Web Server Directory
You need to copy all files from the wordpress folder to the web server’s root directory (/var/www/html/) so that Nginx can serve the PHP-generated content based on user HTTP requests.
Clear the existing web server directory (as it currently contains only the default Nginx welcome page, which we no longer need):
rm /var/www/html/*
Copy WordPress files to the web server directory:
cp -R wordpress/* /var/www/html/
The -R flag enables recursive copying of files and folders.
Set ownership and permissions. Ensure that Nginx can access and modify these files by setting the www-data user and group ownership, as well as appropriate permissions, for the WordPress directory:
sudo chown -R www-data:www-data /var/www/html/sudo chmod -R 755 /var/www/html/
This allows Nginx to read, write, and modify WordPress files as needed, avoiding permission errors during the WordPress installation process.
Step 8. Configuring WordPress
WordPress configuration is managed through an intuitive web-based admin panel. No programming knowledge is necessary, though familiarity with languages like JavaScript, PHP, HTML, and CSS can be helpful for creating or customizing themes and plugins.
Accessing the Admin Panel
Open a web browser and go to the website using the domain specified in the Nginx configuration, such as:
https://mydomain.com
If all components were correctly set up, you should be redirected to WordPress’s initial configuration page:
https://mydomain.com/wp-admin/setup-config.php
Select Language: Choose your preferred language and click Continue.
Database Configuration: WordPress will prompt you to enter database details. Click Let’s go! and provide the following information:
Database Name: wordpress_database (from the previous setup)
Database Username: wordpress_user
Database Password: wordpress_password
Database Host: localhost
Table Prefix: wp_ (or leave as default)
Click Submit. If the credentials are correct, WordPress will confirm access to the database.
Run Installation: Click Run the installation. WordPress will then guide you to enter site and admin details:
Site Title
Admin Username
Admin Password
Admin Email
Option to discourage search engine indexing (recommended for development/testing sites)
Install WordPress: Click Install WordPress. After installation, you’ll be prompted to log in with the admin username and password you created.
Accessing the Dashboard
Once logged in, you'll see the WordPress Dashboard, which contains customizable widgets. The main menu on the left allows access to core WordPress functions, including:
Posts and Pages for content creation
Comments for moderating discussions
Media for managing images and files
Themes and Plugins for design and functionality
Users for managing site members and roles
Your WordPress site is now fully configured, and you can begin customizing and adding content as needed.
Conclusion
This guide showed how to install WordPress along with all its dependencies and how to connect a domain and add a SSL certificate from Let’s Encrypt to an already functioning website, enabling secure HTTPS connections with the remote server.
The key dependencies required for WordPress to function include:
PHP: The scripting language WordPress is written in.
MySQL: The database system used by WordPress to store content and user data.
Nginx (or Apache in other implementations): The web server that processes user requests initially.
For more detailed information on managing site content through the WordPress admin panel, as well as creating custom themes and plugins, refer to the official WordPress documentation.
Frequently Asked Questions
How do I install WordPress on Ubuntu?
First set up Nginx, PHP, and MySQL. Then either download WordPress manually or use a deployment script.
How do I enable HTTPS with Let’s Encrypt?
Use Certbot to generate a certificate, then automate renewal with a simple cron job.
Is Nginx better than Apache for WordPress?
For performance and memory efficiency, yes. Nginx handles high traffic with fewer resources.
16 June 2025 · 13 min to read
Ubuntu
How to Install and Configure SSH on Ubuntu 22.04
SSH is a network protocol that provides a secure connection between a client and a server. All communication is encrypted, preventing theft of data transmitted over the network and other remote network attacks.
Let’s say you have ordered a cloud server from Hostman. You will need SSH installed and configured to connect to and administer the server.
The guide below will describe how to install SSH on Ubuntu 22.04 and configure it.
Prerequisites
Before proceeding with the installation and configuration of the Secure Shell service, ensure the following requirements are met:
Linux Command Line Skills for Configuration
Having a solid grasp of basic Linux commands like sudo, apt, nano, and systemctl is essential when setting up the service. These commands will be frequently used during the installation and configuration process. It's crucial to be comfortable working within the command line environment to manage the service effectively.
Root or Sudo Access for Setup
To install and configure the server, administrative (root) privileges are required. Users must either have sudo access or be logged in as root. Without these privileges, the setup process cannot proceed.
Internet Connection for Package Download
A stable internet connection is necessary to install the OpenSSH server and any additional related packages. Without a functional connection, the system cannot retrieve the required software components.
Configuring Firewall for Access
If a firewall, like ufw, is enabled on the system, it may block remote access by default. It is essential to configure your firewall to allow incoming connections. Use ufw or another firewall tool to ensure port 22 is open and accessible.
Access to the System (Local or Remote)
You need physical access to your machine to configure the service locally, or it must be remotely accessible via its IP address. Ensure the system is properly connected to the network to establish a connection.
Don't forget, that you can deploy your cloud server fast and cheap by choosing our VPS Server Hosting
Step 1: Prepare Ubuntu
The first thing you need to do before you start installing SSH on Ubuntu is to update all apt packages to the latest versions. To do this, use the following command:
sudo apt update && sudo apt upgrade
Step 2: Install SSH on Ubuntu
OpenSSH is not pre-installed on the system, so let's install it manually. To do this, type in the terminal:
sudo apt install openssh-server
The installation of all the necessary components will begin. Answer "Yes" to all the system prompts.
After the installation is complete, go to the next step to start the service.
Step 3: Start SSH
Now you need to enable the service you just installed using the command below:
sudo systemctl enable --now ssh
On successful startup, you will see the following system message.
The --now key helps you launch the service and simultaneously set it to start when the system boots.
To verify that the service is enabled and running successfully, type:
sudo systemctl status ssh
The output should contain the Active: active (running) line, which indicates that the service is successfully running.
If you want to disable the service, execute:
sudo systemctl disable ssh
It disables the service and prevents it from starting at boot.
Step 4: Configure the firewall
Before connecting to the server via SSH, check the firewall to ensure it is configured correctly.
In our case, we have the UFW installed, so we will use the following command:
sudo ufw status
In the output, you should see that SSH traffic is allowed. If you don't have it listed, you need to allow incoming SSH connections. This command will help with this:
sudo ufw allow ssh
Step 5: Connect to the server
Once you complete all the previous steps, you can log into the server using the SSH protocol.
To do this, you will need the server's IP address or domain name and the name of a user created on the server.
In the terminal line, enter the command:
ssh username@IP_address
Or:
ssh username@domain
Important: To successfully connect to a remote server, SSH must be installed and configured on the remote server and the user's computer from which you make the connection.
-
Step 6 (optional): Create Key Pair for Secure Authentication
For enhanced security, consider configuring a key pair instead of relying on password authentication. To generate one, use the following command:
ssh-keygen
Step 7: Configure SSH
Having completed the previous five steps, you can already connect to the server remotely. However, you can further increase the connection's security by changing the default connection port to another or changing the password authentication to key authentication. These and other changes require editing the SSH configuration file.
The main OpenSSH server settings are stored in the main configuration file sshd_config (location: /etc/ssh). Before you start editing, you should create a backup of this file:
sudo cp /etc/ssh/sshd_config /etc/ssh/sshd_config.initial
If you get any errors after editing the configuration file, you can restore the original file without problems.
After creating the backup, you can proceed to edit the configuration file. To do this, open it using the nano editor:
sudo nano /etc/ssh/sshd_config
In the file, change the port to a more secure one. It is best to set values from the dynamic range of ports (49152 - 65535) and use different numbers for additional security. For example, let's change the port value to 49532. To do this, we uncomment the corresponding line in the file and change the port as shown in the screenshot below.
In addition to this setting, we recommend changing the password authentication mode to a more secure key authentication mode. To do this, uncomment the corresponding line and make sure the value is "Yes", as shown in the screenshot.
Now, let's prohibit logging on to the server as a superuser by changing the corresponding line as shown in the picture below.
There are other settings you can configure to increase the server security:
UseDNS checks if the hostname matches its IP address. The value "Yes" enables this parameter.
PermitEmptyPasswords prohibits using empty passwords for authentication if the value is "No."
MaxAuthTries limits the number of unsuccessful attempts to connect to the server within one communication session.
AllowUsers and AllowGroups are responsible for the list of users and groups allowed to access the server:
# AllowUsers User1, User2, User3# AllowGroups Group1, Group2, Group3
Login GraceTime sets the time provided for successful authorization. We recommend reducing the value of this parameter by four times.
ClientAliveInterval limits the time of user inactivity. After exceeding the specified limit, the user is disconnected.
After making all the changes in the main configuration file, save them and close the editor.
Restart the service to make the changes take effect:
sudo systemctl restart ssh
If you have changed the port in the configuration file, you should connect using the new port:
ssh -p port_number username@IP_address
Or:
ssh -p port_number_port_username@domain
Troubleshooting Connection Issues
Ensure the service is running with:
sudo systemctl status ssh
Restart it if necessary:
sudo systemctl restart ssh
Check firewall settings to allow traffic on port 22:
sudo ufw allow 22
Confirm the system is reachable by running:
ping <server-ip-address>
Disabling the Service
If you need to disable remote access for any reason, follow these steps:
Stop the Service
To temporarily stop accepting connections:
sudo systemctl stop ssh
Prevent Automatic Startup
To disable it from starting on reboot:
sudo systemctl disable ssh
Confirm Inactive Status
Verify that the service is no longer running:
sudo systemctl status ssh
Uninstall the Server
If the service is no longer needed, remove it and its associated configuration files:
sudo apt remove openssh-server
Conclusion
This article presents a step-by-step guide on installing and configuring SSH in Ubuntu 22.04 and describes how to edit the main configuration file to improve security. We hope this guide helps you to set up a secure remote connection to your Ubuntu server.To see more about SSH keys click here.
05 June 2025 · 7 min to read
Ubuntu
How to Install VNC on Ubuntu
If you need to interact with a remote server through a graphical interface, you can use VNC technology.VNC (Virtual Network Computing) allows users to establish a remote connection to a server over a network. It operates on a client-server architecture and uses the RFB protocol to transmit screen images and input data from various devices (such as keyboards or mice). VNC supports multiple operating systems, including Ubuntu, Windows, macOS, and others. Another advantage of VNC is that it allows multiple users to connect simultaneously, which can be useful for collaborative work on projects or training sessions.
In this guide, we will describe how to install VNC on Ubuntu, using a Hostman cloud server with Ubuntu 22.04 as an example.
Step 1: Preparing to Install VNC
Before starting the installation process on both the server and the local machine, there are a few prerequisites to review.
Here is a list of what you’ll need to complete the installation:
A Server Running Ubuntu 22.04. In this guide, we will use a cloud server from Hostman with minimal hardware configuration.
A User with sudo Privileges. You should perform the installation as a regular user with administrative privileges.
Select a Graphical Interface. You’ll need to choose a desktop environment that you will use to interact with the remote server after installing the system on both the server and the local machine.
A Computer with a VNC Client Installed.
Currently, the only way to communicate with a rented server running Ubuntu 22.04 is through the console. To enable remote management via a graphical interface, you’ll need to install a desktop environment along with VNC on the server. Below are lists of available VNC servers and desktop environments that can be installed on an Ubuntu server.
VNC Servers:
TightVNC Server. One of the most popular VNC servers for Ubuntu. It is easy to set up and offers good performance.
RealVNC Server. RealVNC provides a commercial solution for remote access to servers across various Linux distributions, including Ubuntu, Debian, Fedora, Arch Linux, and others.
Desktop Environments:
Xfce. A lightweight and fast desktop environment, ideal for remote sessions over VNC. It uses fewer resources than heavier desktop environments, making it an excellent choice for servers and virtual machines.
GNOME. The default Ubuntu desktop environment, offering a modern and user-friendly interface. It can be used with VNC but will consume more resources than Xfce.
KDE Plasma. Another popular desktop environment that provides a wide range of features and a beautiful design.
The choice of VNC server and desktop environment depends on the user’s specific needs and available resources. TightVNC and Xfce are excellent options for stable remote sessions on Ubuntu, as they do not require high resources. In the next step, we will describe how to install them on the server in detail.
Step 2: Installing the Desktop Environment and VNC Server
To install the VNC server on Ubuntu along with the desktop environment, connect to the server and log in as a regular user with administrative rights.
Update the Package List
After logging into the server, run the following command to update the packages from the connected repositories:
sudo apt update
Install the Desktop Environment
Next, install the previously selected desktop environment. To install Xfce, enter:
sudo apt install xfce4 xfce4-goodies
Here, the first package provides the basic Xfce desktop environment, while the second includes additional applications and plugins for Xfce, which are optional.
Install the TightVNC Server
To install TightVNC, enter:
sudo apt install tightvncserver
Start the VNC Server
Once the installation is complete, initialize the VNC server by typing:
vncserver
This command creates a new VNC session with a specific session number, such as :1 for the first session, :2 for the second, and so on. This session number corresponds to a display port (for example, port 5901 corresponds to :1). This allows multiple VNC sessions to run on the same machine, each using a different display port.
During the first-time setup, this command will prompt you to set a password, which will be required for users to connect to the server’s graphical interface.
Set the View-Only Password (Optional)
After setting the main password, you’ll be prompted to set a password for view-only mode. View-only mode allows users to view the remote desktop without making any changes, which is helpful for demonstrations or when limited access is needed.
If you need to change the passwords set above, use the following command:
vncpasswd
Now you have a VNC session.
In the next step, we will set up VNC to launch the Ubuntu server with the installed desktop environment.
Step 3: Configuring the VNC Server
The VNC server needs to know which desktop environment it should connect to. To set this up, we’ll need to edit a specific configuration file.
Stop Active VNC Instances
Before making any configurations, stop any active VNC server instances. In this guide, we’ll stop the instance running on display port 5901. To do this, enter:
vncserver -kill :1
Here, :1 is the session number associated with display port 5901, which we want to stop.
Create a Backup of the Configuration File
Before editing, it’s a good idea to back up the original configuration file. Run:
mv ~/.vnc/xstartup ~/.vnc/xstartup.bak
Edit the Configuration File
Now, open the configuration file in a text editor:
nano ~/.vnc/xstartup
Replace the contents with the following:
#!/bin/bashxrdb $HOME/.Xresourcesstartxfce4 &
#!/bin/bash – This line is called a "shebang," and it specifies that the script should be executed using the Bash shell.
xrdb $HOME/.Xresources – This line reads settings from the .Xresources file, where desktop preferences like colors, fonts, cursors, and keyboard options are stored.
startxfce4 & – This line starts the Xfce desktop environment on the server.
Make the Configuration File Executable
To allow the configuration file to be executed, use:
chmod +x ~/.vnc/xstartup
Start the VNC Server with Localhost Restriction
Now that the configuration is updated, start the VNC server with the following command:
vncserver -localhost
The -localhost option restricts connections to the VNC server to the local host (the server itself), preventing remote connections from other machines. You will still be able to connect from your computer, as we’ll set up an SSH tunnel between it and the server. These connections will also be treated as local by the VNC server.
The VNC server configuration is now complete.
Step 4: Installing the VNC Client and Connecting to the Server
Now, let’s proceed with installing a VNC client. In this example, we’ll install the client on a Windows 11 computer.
Several VNC clients support different operating systems. Here are a few options:
RealVNC Viewer. The official client from RealVNC, compatible with Windows, macOS, and Linux.
TightVNC Viewer. A free and straightforward VNC client that supports Windows and Linux.
UltraVNC. Another free VNC client for Windows with advanced remote management features.
For this guide, we’ll use the free TightVNC Viewer.
Download and Install TightVNC Viewer
Visit the official TightVNC website, download the installer, and run it.
In the installation window, click Next and accept the license agreement.
Then, select the custom installation mode and disable the VNC server installation, as shown in the image below.
Click Next twice and complete the installation of the VNC client on your local machine.
Set Up an SSH Tunnel for Secure Connection
To encrypt your remote access to the VNC server, use SSH to create a secure tunnel. On your Windows 11 computer, open PowerShell and enter the following command:
ssh -L 56789:localhost:5901 -C -N -l username server_IP_address
Make sure that OpenSSH is installed on your local machine; if not, refer to Microsoft’s documentation to install it.
This command configures an SSH tunnel that forwards the connection from your local computer to the remote server over a secure connection, making VNC believe the connection originates from the server itself. Here’s a breakdown of the flags used:
-L sets up SSH port forwarding, redirecting the local computer’s port to the specified host and server port. Here, we choose port 56789 because it is not bound to any service.
-C enables compression of data before transmitting over SSH.
-N tells SSH not to execute any commands after establishing the connection.
-l specifies the username for connecting to the server.
Connect with TightVNC Viewer
After creating the SSH tunnel, open the TightVNC Viewer and enter the following in the connection field:
localhost:56789
You’ll be prompted to enter the password created during the initial setup of the VNC server.
Once you enter the password, you’ll be connected to the VNC server, and the Xfce desktop environment should appear.
Stop the SSH Tunnel
To close the SSH tunnel, return to the PowerShell or command line on your local computer and press CTRL+C.
Conclusion
This guide has walked you through the step-by-step process of setting up VNC on Ubuntu 22.04. We used TightVNC Server as the VNC server, TightVNC Viewer as the client, and Xfce as the desktop environment for user interaction with the server.
We hope that using VNC technology helps streamline your server administration, making the process easier and more efficient.
We're prepared more detailed instruction on how to create server on Ubuntu if you have some trouble deploying it.
30 May 2025 · 8 min to read
Do you have questions,
comments, or concerns?
Our professionals are available to assist you at any moment,
whether you need help or are just unsure of where to start.
whether you need help or are just unsure of where to start.
