Wednesday, 26 March 2025

How to Restart Network Services in Ubuntu 24.04: 5 Methods

 

How to Restart Network Services in Ubuntu 24.04: 5 Methods

Restart Network Services in Ubuntu 24.04

Ubuntu, the well-known operating system, is known for its ease of use as well as stability. However, like any complex system, sometimes it’s necessary to restart network services to resolve connectivity issues or apply configuration changes. In Ubuntu 24.04, restarting network services can be a routine task for managing connections and troubleshooting issues. The process is straightforward and can be done using the command line or GUI.

Ubuntu 24.04, the latest LTS release, offers several methods to manage network services, ensuring users can maintain a seamless and efficient networking experience.

Table of Content

How to Restart Network Services in Ubuntu 24.04

Before diving into the methods, it’s essential to understand that Ubuntu primarily uses NetworkManager to manage network connections. This service is responsible for handling Wi-Fi, Ethernet, and other network interfaces.

Method 1: Using Systemd

This is the most efficient as well as common method for restarting network services in the Ubuntu system. Systemd is the init system and system manager that has become the new standard for Linux distributions. For restarting network services through systemd, users can utilize the following command:

sudo systemctl restart NetworkManager

This command restarts the NetworkManager service, which is responsible for managing network connections on Ubuntu. This command gracefully stops and starts the NetworkManager service.

Method 2: Using NetworkManager Command Line Interface (nmcli)

For more advanced users, nmcli can be used to manipulate network connections. The nmcli is a utility for reporting network status as well as controlling NetworkManager. To restart network services with nmcli, follow these steps:

List available connections:

For listing available connections, users can utilize the nmcli command:

nmcli connection show

1. Turn off networking:

For turning off networking, users can utilize the sudo nmcli connection down <connection_name> command:

sudo nmcli networking off

2. Turn networking back on:

For turning on networking, users can utilize the nmcli command:

sudo nmcli networking on

3. Reconnect a connection:

For reconnection networking, users can utilize the sudo nmcli connection up <connection_name> command:

sudo nmcli connection up <connection_name>

4. Verifying the Restart

After restarting the network, you can verify the status using:

nmcli general status

This provides information about your network connection. This method is straightforward and is often preferred by system administrators for its simplicity.

Method 3: Using NetworkManager Text User Interface (nmtui)

The nmtui is a text-based user interface for NetworkManager. It provides a simple and interactive way to manage network configurations. To restart network services using nmtui, simply type:

nmtui

Then navigate through the menu to ‘Activate a connection’,

Now, select the desired network, and deactivate/reactivate it as needed:

Note: Remember to always verify the restart and ensure that your network is operational after performing any changes.

Method 4: Using ifup and ifdown

While less common in newer Ubuntu versions, you can still use ifup and ifdown for more granular control over network interfaces. These commands are less common in newer versions of Ubuntu but are still available for use:

Identify your network interface:

This lists all active network interfaces:

ip a

1. Bring the network interface down:

The ifup and ifdown commands are used to bring network interfaces up or down, respectively:

sudo ifdown <interface_name>

Replace <interface_name> with the actual name of your interface (e.g., eth0, wlp0s20f3).

sudo ifdown enp0s3

2. Bring the network interface back up:

Let’s the network interface up with the ifup command:

sudo ifup enp0s3

Note: Be cautious when using these commands, especially if you are connected remotely, as they can disrupt your connection. It’s important to note that if you’re connected remotely, you should be cautious when restarting network services to avoid losing your connection.

Method 5: Restarting Networking Service

Each method of restarting network services in Ubuntu 24.04 has its own use case and benefits. For a more traditional approach, you can restart the entire networking service with:

sudo systemctl restart NetworkManager.service

This command stops and then starts the networking service, effectively restarting it.

By following these methods, you should be able to effectively restart network services in Ubuntu 24.04.

Note: Whether you prefer the simplicity of nmcli, the interactivity of nmtui, or the traditional approach of restarting the networking service, Ubuntu provides the flexibility to manage your network services efficiently.

Conclusion

For the command line, the systemctl command is commonly used to restart the NetworkManager service in Ubuntu. It can be done by executing sudo systemctl restart NetworkManager.service. This command prompts the network icon to disappear momentarily as the service restarts.

Alternatively, the nmcli tool provides a simple way to turn networking off and on with sudo nmcli networking off and sudo nmcli networking on. For those who prefer a graphical interface, the Network Manager GUI offers an intuitive way to manage network connections, including restarting services.

For more detailed information and additional options, you can refer to the official Ubuntu documentation or community resources.

 

 

SOURCE

Tuesday, 28 January 2025

How To Set Up Password Authentication with Apache on Ubuntu

 Introduction

When setting up a web server, there are often sections of the site that you wish to restrict access to. Web applications often provide their own authentication and authorization methods, but the web server itself can be used to restrict access if these are inadequate or unavailable.

In this guide, we’ll demonstrate how to password protect assets on an Apache web server running on Ubuntu 14.04.

Prerequisites

To get started, you will need access to an Ubuntu 14.04 server environment. You will need a non-root user with sudo privileges in order to perform administrative tasks. To learn how to create such a user, follow our Ubuntu 14.04 initial server setup guide.

Install the Apache Utilities Package

In order to create the file that will store the passwords needed to access our restricted content, we will use a utility called htpasswd. This is found in the apache2-utils package within the Ubuntu repositories.

Update the local package cache and install the package by typing this command. We will take this opportunity to also grab the Apache2 server in case it is not yet installed on the server:

  1. sudo apt-get update
  2. sudo apt-get install apache2 apache2-utils

Create the Password File

We now have access to the htpasswd command. We can use this to create a password file that Apache can use to authenticate users. We will create a hidden file for this purpose called .htpasswd within our /etc/apache2 configuration directory.

The first time we use this utility, we need to add the -c option to create the specified file. We specify a username (sammy in this example) at the end of the command to create a new entry within the file:

  1. sudo htpasswd -c /etc/apache2/.htpasswd sammy

You will be asked to supply and confirm a password for the user.

Leave out the -c argument for any additional users you wish to add:

  1. sudo htpasswd /etc/apache2/.htpasswd another_user

If we view the contents of the file, we can see the username and the encrypted password for each record:

  1. cat /etc/apache2/.htpasswd
Output
sammy:$apr1$lzxsIfXG$tmCvCfb49vpPFwKGVsuYz. another_user:$apr1$p1E9MeAf$kiAhneUwr.MhAE2kKGYHK.

Configure Apache Password Authentication

Now that we have a file with our users and passwords in a format that Apache can read, we need to configure Apache to check this file before serving our protected content. We can do this in two different ways.

The first option is to edit the Apache configuration and add our password protection to the virtual host file. This will generally give better performance because it avoids the expense of reading distributed configuration files. If you have this option, this method is recommended.

If you do not have the ability to modify the virtual host file (or if you are already using .htaccess files for other purposes), you can restrict access using an .htaccessfile. Apache uses.htaccess` files in order to allow certain configuration items to be set within a file in a content directory. The disadvantage is that Apache has to re-read these files on every request that involves the directory, which can impact performance.

Choose the option that best suits your needs below.

Configuring Access Control within the Virtual Host Definition

Begin by opening up the virtual host file that you wish to add a restriction to. For our example, we’ll be using the 000-default.conf file that holds the default virtual host installed through Ubuntu’s apache package:

  1. sudo nano /etc/apache2/sites-enabled/000-default.conf

Inside, with the comments stripped, the file should look similar to this:

/etc/apache2/sites-enabled/000-default.conf
<VirtualHost *:80>
    ServerAdmin webmaster@localhost
    DocumentRoot /var/www/html
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

Authentication is done on a per-directory basis. To set up authentication, you will need to target the directory you wish to restrict with a <Directory ___> block. In our example, we’ll restrict the entire document root, but you can modify this listing to only target a specific directory within the web space:

/etc/apache2/sites-enabled/000-default.conf
<VirtualHost *:80>
    ServerAdmin webmaster@localhost
    DocumentRoot /var/www/html
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    <Directory "/var/www/html">
    </Directory>
</VirtualHost>

Within this directory block, specify that we wish to set up Basic authentication. For the AuthName, choose a realm name that will be displayed to the user when prompting for credentials. Use the AuthUserFile directive to point Apache to the password file we created. Finally, we will require a valid-user to access this resource, which means anyone who can verify their identity with a password will be allowed in:

/etc/apache2/sites-enabled/000-default.conf
<VirtualHost *:80>
    ServerAdmin webmaster@localhost
    DocumentRoot /var/www/html
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    <Directory "/var/www/html">
        AuthType Basic
        AuthName "Restricted Content"
        AuthUserFile /etc/apache2/.htpasswd
        Require valid-user
    </Directory>
</VirtualHost>

Save and close the file when you are finished. Restart Apache to implement your password policy:

  1. sudo service apache2 restart

The directory you specified should now be password protected.

Configuring Access Control with .htaccess Files

If you wish to set up password protection using .htaccess files instead, you should begin by editing the main Apache configuration file to allow .htaccess files:

  1. sudo nano /etc/apache2/apache2.conf

Find the <Directory> block for the /var/www directory that holds the document root. Turn on .htaccess processing by changing the AllowOverride directive within that block from “None” to “All”:

/etc/apache2/apache2.conf
. . .

<Directory /var/www/>
    Options Indexes FollowSymLinks
    AllowOverride All
    Require all granted
</Directory>

. . .

Save and close the file when you are finished.

Next, we need to add an .htaccess file to the directory we wish to restrict. In our demonstration, we’ll restrict the entire document root (the entire website) which is based at /var/www/html, but you can place this file in any directory you wish to restrict access to:

  1. sudo nano /var/www/html/.htaccess

Within this file, specify that we wish to set up Basic authentication. For the AuthName, choose a realm name that will be displayed to the user when prompting for credentials. Use the AuthUserFile directive to point Apache to the password file we created. Finally, we will require a valid-user to access this resource, which means anyone who can verify their identity with a password will be allowed in:

/var/www/html/.htaccess
AuthType Basic
AuthName "Restricted Content"
AuthUserFile /etc/apache2/.htpasswd
Require valid-user

Save and close the file. Restart the web server to password protect all content in or below the directory with the .htaccess file:

  1. sudo service apache2 restart

Confirm the Password Authentication

To confirm that your content is protected, try to access your restricted content in a web browser. You should be presented with a username and password prompt that looks like this:

Apache2 password prompt

If you enter the correct credentials, you will be allowed to access the content. If you enter the wrong credentials or hit “Cancel”, you will see the “Unauthorized” error page:

Apache2 unauthorized error

Conclusion

You should now have everything you need to set up basic authentication for your site. Keep in mind that password protection should be combined with SSL encryption so that your credentials are not sent to the server in plain text. To learn how to create a self-signed SSL certificate to use with Apache, follow this guide. To learn how to install a commercial certificate, follow this guide.

 

SOURCE

Wednesday, 15 January 2025

Step-by-Step Guide: Deploying a Next.js Application on an Ubuntu Server with Apache and PM2


Step 1: SSH into the Server

  • Access your server via SSH using the root user or a user with sufficient privileges.
ssh root@195.110.58.215

Step 2: Update System Packages and Install Dependencies

  • Update the server's package list and install necessary software, including Node.js, npm, Git, and Apache.
sudo apt update
sudo apt install nodejs npm git apache2

Step 3: Create Project Directory

  • Set up the directory where your Next.js application will be hosted.
sudo mkdir -p /var/www/hibreton-frontend
sudo chown -R $USER:$USER /var/www/hibreton-frontend

Step 4: Generate an SSH Key (Optional)

  • If you need to access a private Git repository, generate an SSH key to use with Git.
ssh-keygen -t rsa -b 4096 -C "hibreton-frontend" -f ~/.ssh/hibreton_frontend
  • Display the public key and add it to your Git provider:
cat ~/.ssh/hibreton_frontend.pub
  • Add the key to the repository you wish to clone image

Step 5: Clone the Repository

  • Clone your Next.js project from GitHub or another Git provider.
GIT_SSH_COMMAND='ssh -i ~/.ssh/hibreton_frontend' git clone git@github.com:hibretOne-CIC/hibretone-frontend-react.git /var/www/hibreton-frontend

Step 6: Install Project Dependencies

  • Navigate to the project directory and install the necessary Node.js packages.
cd /var/www/hibreton-frontend
npm install

Step 7: Build the Project

  • Build the Next.js project for production.
npm run build

Step 8: Install PM2

  • PM2 is a process manager for Node.js that ensures your application remains online. Install it globally.
pm2 start npm --name "hibreton-frontend" -- start

Step 10: Configure Apache as a Reverse Proxy

  • Apache will serve as a reverse proxy, forwarding requests to the Next.js app running on port 3000.

Step 10.1: Stop Nginx (if running)

  • If Nginx is running, stop it to avoid port conflicts with Apache.
sudo systemctl stop nginx

Step 10.2: Create an Apache Configuration File

  • Create a virtual host configuration for your Next.js application.
sudo nano /etc/apache2/sites-available/hibreton-frontend.conf
  • Add the following content to the file:
<VirtualHost *:80>
    ServerName 195.110.58.215
    ServerAdmin webmaster@localhost
    DocumentRoot /var/www/hibreton-frontend

    ProxyPreserveHost On
    ProxyPass / http://localhost:3000/
    ProxyPassReverse / http://localhost:3000/

    ErrorLog ${APACHE_LOG_DIR}/hibreton-frontend-error.log
    CustomLog ${APACHE_LOG_DIR}/hibreton-frontend-access.log combined
</VirtualHost>

Step 10.3: Enable the Apache Modules

  • Enable the necessary modules for proxying.
sudo a2enmod rewrite
sudo a2enmod proxy
sudo a2enmod proxy_http

Step 10.4: Enable the Site and Disable Default Site

  • Enable your new site and disable the default Apache site.
sudo a2ensite hibreton-frontend.conf
sudo a2dissite 000-default.conf

Step 10.5: Test Apache Configuration

  • Check that the Apache configuration is correct.
sudo apache2ctl configtest

Step 11: Set Up PM2 to Auto-Start on Reboot

  • Ensure that PM2 starts your application automatically when the server reboots.
pm2 startup systemd
pm2 save

Step 12: Configure Firewall

  • Allow Apache traffic through the firewall if UFW is active.
sudo ufw allow 'Apache Full'

Step 13: Access the Application

  • Your Next.js application should now be accessible at http://195.110.58.215.

Troubleshooting

Checking Apache Logs

  • If the application does not load, check the Apache error logs for clues.
sudo tail -f /var/log/apache2/error.log

Checking the PM2 Process

  • Ensure the Node.js process is running correctly.
pm2 list
  • To view logs for the Next.js application:
pm2 logs hibreton-frontend

Restarting or Removing the Application in PM2

  • If you need to restart or remove the application from PM2:
pm2 restart hibreton-frontend
pm2 delete hibreton-frontend

Handling Port Conflicts

  • If port 3000 is already in use, find and kill the process using it.
sudo lsof -i :3000
sudo kill -9 <PID>
  • Afterward, restart the application with PM2:
pm2 start npm --name "hibreton-frontend" -- start

Next.js Application Not Binding to 0.0.0.0

  • Ensure that your Next.js application is configured to listen on 0.0.0.0 instead of localhost to be accessible externally.
// next.config.js
module.exports = {
  server: {
    hostname: '0.0.0.0',
    port: 3000,
  },
};
  • With these steps, your Next.js application should be successfully deployed and served using Apache and PM2!

 

SOURCE