## Install FTP Server
Setting up an FTP server on your Ubuntu server to grant access to the /var/www/yourdomain.com directory is a smart move, especially when dealing with file transfers. The go-to choice for this task is vsftpd, short for Very Secure FTP Daemon.

Now, let's break down the steps to get your FTP server up and running smoothly. First things first, you'll want to install vsftpd using your terminal, then proceed to configure the necessary settings in the `vsftpd.conf` file. 

```bash
# Accessing the server
ssh user@your_server_ip

# Install vsftpd
sudo apt update
sudo apt install vsftpd

# Configure vsftpd
sudo nano /etc/vsftpd.conf
```

Uncomment or add the following lines:

```text
write_enable=YES
local_umask=022
chroot_local_user=YES
allow_writeable_chroot=YES
```

Add the following lines at the end to restrict users to the desired directory:

```text
user_sub_token=$USER
local_root=/var/www/$USER
```

---

## Create an FTP user
Creating an FTP user is a crucial step in customizing your server, ensuring secure and tailored access to specific directories. Let's delve into the nitty-gritty of this process. 

Begin by replacing the generic placeholder `yourdomain.com` with the actual FTP username you desire. The command `sudo adduser --force-badname yourdomain.com` works its magic, initiating the user creation process.

As you run this command, you'll be prompted to set a new password for the user. The system will prompt you to enter additional information, such as Full Name, Room Number, Work Phone, and Home Phone. Feel free to input the relevant details or hit `Enter` to stick with the defaults.

```bash
# Create the user
sudo adduser --force-badname yourdomain.com

# New password:
# Retype new password:
# passwd: password updated successfully
# Changing the user information for yourdomain.com
# Enter the new value, or press ENTER for the default
#         Full Name []:
#         Room Number []:
#         Work Phone []:
#         Home Phone []:
#         Other []:
# Is the information correct? [Y/n] y
```

Now comes the crucial part – setting ownership for the FTP directory. The command 'sudo chown -R yourdomain.com:yourdomain.com /var/www/yourdomain.com' ensures that the newly created user has the reins over the specified directory. This step is vital for smooth and secure file operations within the FTP space.

To seal the deal and make your changes take effect, restart the vsftpd service with `sudo service vsftpd restart`. This step ensures that the adjustments made to user privileges and directory ownership are applied promptly. 

```bash
# Set ownership for the FTP directory
sudo chown -R yourdomain.com:yourdomain.com /var/www/yourdomain.com

# Restart vsftpd for the changes to take effect
sudo service vsftpd restart
```

By following these meticulous steps, you not only create an FTP user but also personalize their experience, setting the stage for efficient and secure file transfers within your Ubuntu server. It's like crafting a key for a specific room – only the designated user gets access, keeping your server's integrity intact. 

---

## FTP Client
FileZilla is my go-to program for seamlessly transferring files from my local computer to the server. The beauty of FileZilla lies in its user-friendly interface, presenting a split-screen view. On the left side, I see the folders and files on my local machine, while the right side displays the directories on the remote server.

![FileZilla FTP Client](/images/articles/en/technology/linux-ftp-server/1.png)
<div class="imgDescription">FileZilla FTP Client</div>

---

What makes FileZilla stand out is the simplicity of dragging and dropping. I can effortlessly move files from my computer to the server's folder or vice versa. This visual representation in the split-screen setup makes file organization a breeze. It's like arranging digital files on shelves, and FileZilla gives me the perfect toolset.

Moreover, FileZilla ensures a secure journey for my files. It supports various security protocols like FTP, SFTP, and FTPS, acting as a reliable guardian during the transfer process. It's not just a file transfer tool; it's a security-savvy companion.

---

Adding a new site in FileZilla is a breeze, and here's the lowdown on how to do it. First off, head to the "File" menu and click on "Site Manager." Once you're there, hit the "New Site" button to start setting up your fresh connection.

Now, it's time to get down to the details. Give your new site a name that makes sense to you – something like "MyServer" or whatever floats your boat. After that, you'll need to specify the host (that's the server's address) and choose the type of protocol (usually FTP or SFTP).

Here's a crucial tip: When you're setting up the login credentials, type the password manually instead of copying and pasting it. It might sound old-school, but it's a smart move. This way, you avoid any sneaky hidden characters that might tag along with a copy-paste, ensuring a smooth login process.

Once you've got all the info plugged in, hit "Connect" and watch the magic happen. FileZilla will remember these details, so the next time you want to visit your site, it's just a click away.

---

## Conclusion
Hey, so wrapping up the article – setting up an FTP server on Ubuntu is a game-changer for smooth file transfers. Vsftpd is your go-to guy for this, and I've broken down the steps for you. Plus, creating a personalized FTP user and diving into FileZilla's split-screen magic makes file management a breeze. It's like handing you the keys to a well-organized digital kingdom. Give it a go, and your file transfers will thank you later!

---

### References
1. <a href="https://security.appspot.com/vsftpd.html" target="_blank" rel="noopener">FTP Server - vsftpd</a>
2. <a href="https://filezilla-project.org" target="_blank" rel="noopener">FTP Client - FileZilla</a>

Mastering FTP on Ubuntu: Install vsftpd with ease and secure file transfers. Plus, a guide to creating users and unleashing the power of FileZilla for seamless file management!

FTP Server Installation Guide for Ubuntu Linux

## Accessing the Server
Use `cmd` or your preferred SSH client to connect to the server:

```bash
ssh user@your_server_ip
```

When typing the password, you do not see letters or asterisks; no worries.

---

## DNS Configuration for Your Domains
you need to make sure that your domain names are correctly mapped to your server's IP address. This involves configuring the Domain Name System (DNS) settings with your domain provider.

1. Login to your domain provider's website.

2. Locate DNS management or name servers settings.

3. Create `A` records.

Example:
  - example1.com `A` record: your_server_IP


![Domain provider DNS](/images/articles/en/technology/host-websites-nginx/2.png)

---

## Install Nginx
Update the package list and install Nginx:

```bash
sudo apt update
sudo apt install nginx
```

To check if Nginx is installed on your Ubuntu server, you can use the following command:

```bash
nginx -v
# nginx version: nginx/1.18.0 (Ubuntu)
```

---

## Start and Enable Nginx
Start the Nginx service and enable it to start on boot:

```bash
sudo service nginx start
sudo systemctl enable nginx
```

---

## Add Domain to Nginx
Replace `/var/www/yourdomain.com` with the path where you want to store the website files:

```bash
# Create a root directory for the domain
sudo mkdir /var/www/yourdomain.com

# Set the correct permissions for the new directory
sudo chown -R www-data:www-data /var/www/yourdomain.com

# Create a sample HTML file for testing
echo '<html><body><h1>Welcome to yourdomain.com!</h1></body></html>' | sudo tee /var/www/yourdomain.com/index.html

# View the folders and files
cd /var/www/
ls
cd yourdomain/
ls

# Create an Nginx configuration file for the new domain
sudo nano /etc/nginx/sites-available/yourdomain.com
```

> The `nano` command is a text editor in Unix-like operating systems.

Paste the following configuration, adjusting the domain name and paths:

```text
server {
    listen 80;
    server_name yourdomain.com www.yourdomain.com;

    root /var/www/yourdomain.com;
    index index.html;

    location / {
        try_files $uri $uri/ =404;
    }
}
```

Press `Ctrl + O` (Write Out) to save the file, and then press `Ctrl + X` to exit the text editor.

Save the file and create a symbolic link to enable the site:
```bash
sudo ln -s /etc/nginx/sites-available/yourdomain.com /etc/nginx/sites-enabled/
```

Test Nginx Configuration:

```bash
sudo nginx -t
# nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
# nginx: configuration file /etc/nginx/nginx.conf test is successful
```

Restart Nginx to apply the changes:

```bash
sudo service nginx restart
```

Make sure the DNS records for `yourdomain.com` is point to your server's IP address.

Test in the Browser: Visit `http://yourdomain.com` and `http://www.yourdomain.com` in your browser to see the welcome message.

![Test in the Browser](/images/articles/en/technology/host-websites-nginx/3.png)

---

## SSL Certificate - HTTPS
Use Let's Encrypt to obtain a free SSL certificate. Many hosting providers and platforms have integrated Let's Encrypt support.

```bash
sudo apt update 

# Install Certbot, the official Let's Encrypt client
sudo apt install certbot

# Install the Certbot Nginx plugin
sudo apt install python3-certbot-nginx

# Run Certbot with Nginx Plugin
sudo certbot --nginx -d yourdomain.com -d www.yourdomain.com

# Test the Nginx configuration
sudo nginx -t

# Restart Nginx to apply the changes
sudo service nginx restart
```

The configuration file after the change:

```text
server {
    server_name yourdomain.com www.yourdomain.com;

    root /var/www/yourdomain.com;
    index index.html;

    location / {
        try_files $uri $uri/ =404;
    }

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/yourdomain.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/yourdomain.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}

server {
    if ($host = www.yourdomain.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


    if ($host = yourdomain.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


    listen 80;
    server_name yourdomain.com www.yourdomain.com;
    return 404; # managed by Certbot
}
```

---

## Nginx Config for www to non-www Redirection
Replace `yourdomain.com` with the actual domain of your website.

```bash
# Edit the Nginx configuration file
sudo nano /etc/nginx/sites-available/yourdomain.com
```

```text
server {
    listen 80;
    server_name www.yourdomain.com yourdomain.com;
    return 301 https://yourdomain.com$request_uri;
}

server {
    listen 443 ssl;
    server_name www.yourdomain.com;

    ssl_certificate /etc/letsencrypt/live/yourdomain.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/yourdomain.com/privkey.pem;
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

    return 301 https://yourdomain.com$request_uri;
}

server {
    listen 443 ssl;
    server_name yourdomain.com;

    root /var/www/yourdomain.com;
    index index.html;

    location / {
        try_files $uri $uri/ =404;
    }

    error_page 404 /404.html;
    location = /404.html {
        internal;
    }

    ssl_certificate /etc/letsencrypt/live/yourdomain.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/yourdomain.com/privkey.pem;
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
```

Press `Ctrl + O` followed by `Enter` to save the file.
Press `Ctrl + X` to exit.

```bash
# Test the Nginx configuration
sudo nginx -t
# nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
# nginx: configuration file /etc/nginx/nginx.conf test is successful
```

After making these changes, restart Nginx:

```bash
sudo service nginx restart
# OR
sudo systemctl restart nginx
```

Ensure testing for all scenarios:

1. `http://yourdomain.com` should redirect to `https://yourdomain.com`
2. `http://www.yourdomain.com` should redirect to `https://yourdomain.com`
3. `https://www.yourdomain.com` should redirect to `https://yourdomain.com`
4. `https://yourdomain.com` should remain unchanged and stay on `https://yourdomain.com`

---

In this configuration:

- The first server block (port 80) handles the redirection from `http://yourdomain.com` to `https://yourdomain.com`.
- The second server block (port 443) with server_name `www.yourdomain.com` explicitly redirects to `https://yourdomain.com`.
- The third server block (port 443) with server_name `yourdomain.com` serves the content for `https://yourdomain.com`.

---


## Setting Up Nginx with Node.js and PM2

Let’s get your Node.js Express app running with PM2 and configure Nginx to handle everything. Here’s the step-by-step process:

1. **Connect to Your Server**: 
   ```bash
   ssh user@SERVER_IP
   ```

2. **Navigate to Your App Directory**:
   ```bash
   cd /var/www/yourdomain.com/
   ```

3. **Install PM2 globally (if not already installed)**:
   ```bash
   sudo npm install -g pm2
   ```

4. **Start Your App with PM2**:
   ```bash
   pm2 start ./server.js --name yourdomain.com
   ```

    `server.js`:
   ```javascript
    const express = require('express');
    const path = require('path');
    const fs = require('fs');

    const app = express();

    // Serve static files from the 'public' directory
    app.use(express.static(path.join(__dirname, 'public')));

    // Dynamic wildcard route
    app.get('/*', (req, res) => {
    const requestedPath = req.params[0];
    const filePath = path.join(__dirname, 'public', requestedPath, 'index.html');

    // Check if the file exists, and if so, serve it
    fs.access(filePath, fs.constants.F_OK, (err) => {
        if (err) {
        // File not found, serve 404 page
        res.status(404).sendFile(path.join(__dirname, 'public', '404.html'));
        } else {
        // File found, serve it
        res.sendFile(filePath);
        }
    });
    });

    // Start the server
    const PORT = 3001; 
    app.listen(PORT, () => {
    console.log(`Server is running at http://localhost:${PORT}`);
    });
   ```

5. **Check PM2 Processes**:
   ```bash
   pm2 list
   ```

Now, let’s set up Nginx:

1. **Edit Nginx Configuration**:
   ```bash
   sudo nano /etc/nginx/sites-available/yourdomain.com
   ```

2. **Nginx Configuration**:

   ```nginx
   server {
       listen 80;
       server_name www.yourdomain.com yourdomain.com;
       return 301 https://yourdomain.com$request_uri;
   }

   server {
       listen 443 ssl;
       server_name www.yourdomain.com;

       ssl_certificate /etc/letsencrypt/live/yourdomain.com/fullchain.pem;
       ssl_certificate_key /etc/letsencrypt/live/yourdomain.com/privkey.pem;
       include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
       ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

       return 301 https://yourdomain.com$request_uri;
   }

   server {
       listen 443 ssl;
       server_name yourdomain.com;

       root /var/www/yourdomain.com;

       location / {
           proxy_pass http://localhost:3001;
           proxy_http_version 1.1;
           proxy_set_header Upgrade $http_upgrade;
           proxy_set_header Connection 'upgrade';
           proxy_set_header Host $host;
           proxy_cache_bypass $http_upgrade;
       }

       ssl_certificate /etc/letsencrypt/live/yourdomain.com/fullchain.pem;
       ssl_certificate_key /etc/letsencrypt/live/yourdomain.com/privkey.pem;
       include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
       ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
   }
   ```

   - The first block redirects all HTTP traffic to HTTPS.
   - The second block handles HTTPS for `www.yourdomain.com` and redirects to `yourdomain.com`.
   - The third block serves `yourdomain.com`, proxies requests to your Node.js app on port 3001, and includes SSL settings.

3. **Test Nginx Configuration**:
   ```bash
   sudo nginx -t
   ```

4. **Restart Nginx**:
   ```bash
   sudo service nginx restart
   # OR
   sudo systemctl restart nginx
   ```

And that’s it! Your Node.js app should now be running smoothly with PM2 and Nginx handling the traffic with SSL.


---

## Conclusion
Hosting multiple websites on a Linux server with Nginx can be a seamless and efficient process, providing a robust platform for web management. 
Here's a summary of the key steps covered in this guide:

1. DNS Configuration for Your Domains.

2. Install Nginx.

3. Start and enable Nginx.

4. Add domain to Nginx.

5. SSL certificate - HTTPS.

6. Nginx config for www to non-www redirection.

---

### References
1. <a href="https://ubuntu.com/tutorials/install-and-configure-nginx#1-overview" target="_blank" rel="noopener">Install and configure Nginx</a>

How to master hosting multiple websites on your Linux server with Nginx. Discover seamless solutions for effortless and efficient web management.

Hosting Multiple Websites with Nginx on a Single Linux Server

## Buying a Server
VPS providers often offer plans with fixed monthly costs, providing predictability in budgeting. This can be particularly beneficial when you have a steady or predictable workload with substantial data transfer requirements. 

The inclusion of features such as unmetered bandwidth in certain plans eliminates concerns about overage charges, making it a cost-effective choice for projects with significant data transfer needs.

While you don't directly need to worry about physical disk damage on a VPS, it's crucial to take proactive measures such as regular backups, monitoring, and choosing a reliable hosting provider. 


![VPS VLE-2](/images/articles/en/technology/new-linux-server/2.png)
<div class="imgDescription">
  <a href="https://www.ovhcloud.com/en/vps/limited-edition/" target="_blank" rel="noopener">OVH VPS Limited Edition</a>
</div>

---

**vCore (Virtual Core):** The vCore is a virtualized processing unit. In this server, there are two virtual cores, which means the server has the equivalent of two physical CPU cores. This allows the server to handle parallel processing and execute multiple tasks simultaneously.

**RAM (Random Access Memory):** The server is equipped with 2 GB of RAM. RAM is a type of volatile memory used by the server to temporarily store and quickly access data that is actively being used or processed. Sufficient RAM is crucial for the smooth functioning of applications and the overall performance of the server.

**Storage: 40 GB SSD NVMe (Solid State Drive Non-Volatile Memory Express):** The server is equipped with a 40 GB SSD NVMe storage. SSDs are faster and more reliable than traditional HDDs (Hard Disk Drives). NVMe is a protocol designed for SSDs, providing even faster data transfer speeds compared to older protocols. The 40 GB storage is where you can store your operating system, applications, and data.

**Bandwidth: 500 Mbps Unmetered:** Bandwidth refers to the data transfer rate of the server's internet connection. In this case, the server has a bandwidth of 500 Megabits per second (Mbps). The term "unmetered" means that there is no set limit on the amount of data that can be transferred over the network within the specified bandwidth. It allows for a consistent and uninterrupted data transfer at the specified rate.

![OVH VPS Server VLE-2](/images/articles/en/technology/new-linux-server/1.png)

**Operating System:** Installing `Ubuntu Server 22.04.3 LTS` on your server offers advantages. It's a Long Term Support (LTS) release, ensuring stable performance and security updates until 2027. The version introduces newer features, enhanced hardware compatibility, and improved software stacks.

---

## Accessing the Server
When setting up a VPS, the process typically involves receiving an email with a temporary password once the server is ready. 

The initial access to the server requires connecting through the command line or your preferred SSH client. Follow these steps:

1. Open your command line interface (cmd) or your chosen SSH client.

2. Use the following command, replacing `user` with your username and `your_server_ip` with the server's IP address:

```shell
ssh user@your_server_ip
# Welcome to Ubuntu 22.04.3 LTS (GNU/Linux 5.15.0-91-generic x86_64)
```
3. Upon executing the command, you will be prompted to enter a password. It's important to note that when typing the password, you won't see letters or asterisks on the screen. This is a security feature, so proceed to type your password without visual feedback.

4. After successfully entering the temporary password, you will gain access to your server.

5. It is crucial to change the temporary password to a new, secure one.

```shell
sudo passwd
```

---

## Changing the Default Username
Changing the default username, such as "ubuntu," is generally considered a good security practice as it adds another layer of complexity for potential attackers. Default usernames are well-known and commonly targeted, so altering the default username makes it less predictable and potentially more secure.

If you decide to change the default username, it's advisable to do this during the initial setup of your VPS to minimize potential complications. Additionally, make sure to document the changes and update any relevant configurations to maintain a clear understanding of your server's setup.

---

However, keep in mind that changing the default username involves additional steps and precautions, and it might have implications on existing configurations and permissions. Here are some considerations:

1. Existing Configurations: Changing the username might require updates to existing configurations, scripts, and permissions associated with the default username. Make sure to review and update these accordingly.

2. System Users: If the default username is used for specific system-level tasks or services, changing it may impact those functionalities. Ensure that you update any dependencies on the old username.

3. Security through Obscurity: While changing the default username adds a layer of security through obscurity, it should not be the sole security measure. Always use strong, unique passwords, implement regular security audits, and keep your system and applications up-to-date with the latest security patches.

```shell
# Create a new user with sudo privileges
sudo adduser newusername
sudo usermod -aG sudo newusername

# Log in as the new user
su - newusername

# Optional: Confirm that you can use sudo
sudo whoami

# Once you're certain, you can disable the original ubuntu user
sudo usermod --expiredate 1 ubuntu
```

Remember to replace `newusername` with your desired new username. Always exercise caution when making changes to user accounts to avoid unintended consequences.

---

## Host Multiple Websites
With Nginx, you can efficiently host multiple websites on a single machine through virtual hosting. Its robust configuration capabilities enable you to define distinct server blocks for each site, directing traffic based on domain names.

This setup optimizes resource usage, saving you money on infrastructure. Additionally, Nginx seamlessly integrates with Let's Encrypt, enabling you to obtain free SSL certificates.

Read more:
<a href="https://1step2learn.com/en/article/technology/host-websites-nginx/" target="_blank" rel="noopener">Hosting Multiple Websites with Nginx on a Single Linux Server</a>


![VPS VLE-2](/images/articles/en/technology/new-linux-server/server.jpg)

---


## Billing Model
VPS (Virtual Private Server), especially a Linux-based one, can be advantageous when specific needs and significant data transfer are key considerations for your project.

---

**VPS Linux Server vs Cloud Hosting:**

<table class="tableClassic">
    <tr>
        <th></th>
        <th>VPS Linux Server</th>
        <th>Cloud Hosting</th>
    </tr>
    <tr>
        <td>Suitable For</td>
        <td>Projects with consistent resource needs</td>
        <td>Projects with dynamic workloads and varying resource requirements</td>
    </tr>
    <tr>
        <td>Cost Model</td>
        <td>Fixed monthly cost, cost-effective for steady workloads</td>
        <td>Pay-as-you-go model, cost-effective for small to medium-sized projects</td>
    </tr>
    <tr>
        <td>Advantages</td>
        <td>Unmetered bandwidth for significant data transfer</td>
        <td>Scalability based on usage, flexibility for dynamic workloads</td>
    </tr>
</table>

---

**Static Website Hosting Comparison:**

Let's break down the billing models for the VPS Linux server and cloud hosting, considering the requirements for hosting a static website with 10GB downloads per day and 1GB storage.

<table class="tableClassic">
    <tr>
        <th>Hosting Service</th>
        <th>Storage Cost</th>
        <th>Bandwidth Cost</th>
        <th>Total Monthly Cost</th>
    </tr>
    <tr>
        <td>VPS Linux Server</td>
        <td>Included (40GB)</td>
        <td>Unmetered (No additional cost for data transfer)</td>
        <td>$5 per month</td>
    </tr>
    <tr>
        <td>Cloud Hosting</td>
        <td>$0.26 for 10GB</td>
        <td>$1.50 for 10GB (Daily downloads: 10GB, Monthly: 300GB) = $45</td>
        <td>$45.26 per month</td>
    </tr>
</table>

---


## Conclusion
Knowing your website needs and traffic patterns? A fixed price for hosting is your go-to solution. It brings predictability to your budget, offering stability for steady workloads. Consider it for a cost-effective and straightforward hosting choice. 

---

### References
1. <a href="https://www.ovhcloud.com/en/vps/limited-edition/" target="_blank" rel="noopener">OVH VPS Limited Edition</a>

Discover the secrets to effective Linux VPS hosting! From setting up your server to optimizing your budget.

Linux

FTP Server Installation Guide for Ubuntu Linux

Hosting Multiple Websites with Nginx on a Single Linux Server

Setting Up a Linux VPS Server for Hosting