{"id":26525,"date":"2025-06-23T11:26:13","date_gmt":"2025-06-23T09:26:13","guid":{"rendered":"https:\/\/tremhost.com\/blog\/?p=26525"},"modified":"2025-06-23T11:26:13","modified_gmt":"2025-06-23T09:26:13","slug":"how-to-set-up-a-vps-for-the-first-time-a-beginners-tutorial","status":"publish","type":"post","link":"https:\/\/tremhost.com\/blog\/how-to-set-up-a-vps-for-the-first-time-a-beginners-tutorial\/","title":{"rendered":"How to set up a VPS for the first time: A beginner’s tutorial.\u00a0"},"content":{"rendered":"
<\/div>

Setting up a VPS for the first time can seem daunting, but it’s a rewarding experience that gives you much more control over your web presence. This tutorial will guide you through the basic steps. We’ll focus on a common scenario: a Linux-based VPS (Ubuntu or CentOS are popular choices) for hosting a website.<\/p>\n

Prerequisites:<\/strong><\/p>\n

    \n
  1. Purchased a VPS:<\/strong> You’ll need to have already chosen a VPS provider (e.g., DigitalOcean, Linode, Vultr, AWS Lightsail, Google Cloud, Contabo, etc.) and completed the purchase process.<\/li>\n
  2. SSH Client:<\/strong>\n
      \n
    • Windows:<\/strong> PuTTY, MobaXterm, or Windows Terminal (with OpenSSH client installed).<\/li>\n
    • macOS\/Linux:<\/strong> Terminal (OpenSSH client is usually pre-installed).<\/li>\n<\/ul>\n<\/li>\n
    • Basic Command Line Knowledge (Optional but helpful):<\/strong> Knowing how to navigate directories and run basic commands will be beneficial, but we’ll cover the essentials.<\/li>\n<\/ol>\n
      \n

      Step 1: Access Your VPS via SSH<\/h3>\n

      After purchasing your VPS, your provider will typically give you:<\/p>\n

        \n
      • IP Address:<\/strong> The unique address of your server (e.g., 192.0.2.1<\/code>).<\/li>\n
      • Root Username:<\/strong> Usually root<\/code>.<\/li>\n
      • Password:<\/strong> A temporary password or instructions to set one.<\/li>\n<\/ul>\n

        Using an SSH Client:<\/strong><\/p>\n

          \n
        • Windows (PuTTY):<\/strong>\n
            \n
          1. Open PuTTY.<\/li>\n
          2. In the “Host Name (or IP address)” field, enter your VPS’s IP address.<\/li>\n
          3. Click “Open.”<\/li>\n
          4. If prompted with a security alert about the host key, click “Accept” or “Yes” to trust the server.<\/li>\n
          5. A terminal window will open. Type root<\/code> for the username and press Enter.<\/li>\n
          6. Enter the password (it won’t show characters as you type) and press Enter.<\/li>\n<\/ol>\n<\/li>\n
          7. macOS\/Linux (Terminal):<\/strong>\n
              \n
            1. Open your Terminal application.<\/li>\n
            2. Type the following command, replacing your_vps_ip<\/code> with your actual IP address:\n
              \n
              Bash<\/span><\/p>\n
              <\/div>\n<\/div>\n
              \n
              \n
              ssh root@your_vps_ip\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/li>\n
            3. If prompted about authenticity, type yes<\/code> and press Enter.<\/li>\n
            4. Enter your password when requested.<\/li>\n<\/ol>\n<\/li>\n<\/ul>\n
              You are now logged into your VPS!<\/strong> You’ll see a command prompt, usually ending with #<\/code> (e.g., root@yourhostname:~#<\/code>).<\/p>\n
              \n
              Step 2: Initial Server Setup and Security Best Practices<\/h3>\n
              This is crucial for securing your server right from the start.<\/p>\n
                \n
              1. \n
                Change the Root Password (If not done during setup):<\/strong><\/p>\n
                  \n
                • Type: passwd<\/code><\/li>\n
                • Enter a strong new password twice. Use a mix of uppercase, lowercase, numbers, and symbols.<\/li>\n
                • Self-note: Store this password securely!<\/em><\/li>\n<\/ul>\n<\/li>\n
                • \n
                  Update Your Server’s Software:<\/strong> It’s vital to ensure all your server’s packages are up to date to patch security vulnerabilities and get the latest features.<\/p>\n
                    \n
                  • For Ubuntu\/Debian:<\/strong>\n
                    \n
                    Bash<\/span><\/p>\n
                    <\/div>\n<\/div>\n
                    \n
                    \n
                    sudo apt update\r\nsudo apt upgrade -y\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/li>\n
                  • For CentOS\/RHEL:<\/strong>\n
                    \n
                    Bash<\/span><\/p>\n
                    <\/div>\n<\/div>\n
                    \n
                    \n
                    sudo yum update -y\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/li>\n<\/ul>\n
                    (Note: sudo<\/code> allows you to run commands with superuser privileges. You’ll be prompted for your password.)<\/p>\n<\/li>\n
                  • \n
                    Create a New Sudo User (Highly Recommended):<\/strong> Logging in as root<\/code> is powerful but risky. It’s better to create a standard user for daily tasks and use sudo<\/code> for administrative commands.<\/p>\n
                      \n
                    • For Ubuntu\/Debian:<\/strong>\n
                      \n
                      Bash<\/span><\/p>\n
                      <\/div>\n<\/div>\n
                      \n
                      \n
                      adduser your_username\r\nusermod -aG sudo your_username\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n
                      (Replace your_username<\/code> with your desired username. You’ll be prompted to set a password and fill in some optional information.)<\/li>\n
                    • For CentOS\/RHEL:<\/strong>\n
                      \n
                      Bash<\/span><\/p>\n
                      <\/div>\n<\/div>\n
                      \n
                      \n
                      adduser your_username\r\npasswd your_username # Set password for the new user<\/span>\r\nusermod -aG wheel your_username # 'wheel' group grants sudo access on CentOS<\/span>\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/li>\n<\/ul>\n<\/li>\n
                    • \n
                      Configure a Firewall (UFW for Ubuntu, firewalld for CentOS):<\/strong> A firewall blocks unwanted traffic and allows only necessary connections (like SSH, HTTP, HTTPS).<\/p>\n
                        \n
                      • \n
                        For Ubuntu (using UFW – Uncomplicated Firewall):<\/strong><\/p>\n
                        \n
                        Bash<\/span><\/p>\n
                        <\/div>\n<\/div>\n
                        \n
                        \n
                        sudo apt install ufw # Install UFW if not already installed<\/span>\r\nsudo ufw allow OpenSSH # Allow SSH connections (so you don't lock yourself out)<\/span>\r\nsudo ufw enable<\/span> # Enable the firewall<\/span>\r\nsudo ufw status # Check status<\/span>\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n
                        (You’ll later open ports for HTTP\/HTTPS once you install a web server.)<\/em><\/p>\n<\/li>\n
                      • \n
                        For CentOS (using firewalld):<\/strong><\/p>\n
                        \n
                        Bash<\/span><\/p>\n
                        <\/div>\n<\/div>\n
                        \n
                        \n
                        sudo systemctl start firewalld\r\nsudo systemctl enable<\/span> firewalld\r\nsudo firewall-cmd --permanent --add-service=ssh # Allow SSH<\/span>\r\nsudo firewall-cmd --reload # Apply changes<\/span>\r\nsudo firewall-cmd --list-all # Check status<\/span>\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/li>\n<\/ul>\n<\/li>\n
                      • \n
                        Disable Root Login via SSH (Strongly Recommended):<\/strong> This prevents direct login attempts as the root<\/code> user, forcing access through your new sudo<\/code> user.<\/p>\n
                          \n
                        • Login as your new sudo<\/code> user first!<\/strong> Open a new<\/em> SSH session and log in with your your_username<\/code> and its password.<\/li>\n
                        • Then, from your new user’s session:\n
                          \n
                          Bash<\/span><\/p>\n
                          <\/div>\n<\/div>\n
                          \n
                          \n
                          sudo nano \/etc\/ssh\/sshd_config\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/li>\n
                        • Find the line PermitRootLogin yes<\/code> and change it to PermitRootLogin no<\/code>.<\/li>\n
                        • Save and exit (Ctrl+X, Y, Enter for nano).<\/li>\n
                        • Restart the SSH service:\n
                            \n
                          • Ubuntu:<\/strong> sudo systemctl restart sshd<\/code><\/li>\n
                          • CentOS:<\/strong> sudo systemctl restart sshd<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
                            Now, you can no longer log in directly as root<\/code> via SSH. Always use your new sudo<\/code> user.<\/em><\/p>\n<\/li>\n<\/ol>\n
                            \n
                            Step 3: Install a Web Server (e.g., Apache or Nginx)<\/h3>\n
                            This software delivers your website content to visitors.<\/p>\n
                              \n
                            • \n
                              Option A: Apache (Very common for beginners)<\/strong><\/p>\n
                                \n
                              • Ubuntu\/Debian:<\/strong>\n
                                \n
                                Bash<\/span><\/p>\n
                                <\/div>\n<\/div>\n
                                \n
                                \n
                                sudo apt install apache2 -y\r\nsudo ufw allow 'Apache'<\/span> # Allow Apache traffic through firewall<\/span>\r\nsudo systemctl status apache2 # Check if it's running<\/span>\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/li>\n
                              • CentOS\/RHEL:<\/strong>\n
                                \n
                                Bash<\/span><\/p>\n
                                <\/div>\n<\/div>\n
                                \n
                                \n
                                sudo yum install httpd -y\r\nsudo systemctl start httpd\r\nsudo systemctl enable<\/span> httpd\r\nsudo firewall-cmd --permanent --add-service=http # Allow HTTP<\/span>\r\nsudo firewall-cmd --permanent --add-service=https # Allow HTTPS (for later SSL)<\/span>\r\nsudo firewall-cmd --reload\r\nsudo systemctl status httpd\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/li>\n
                              • Test:<\/strong> Open your web browser and navigate to your VPS’s IP address. You should see the default Apache welcome page.<\/li>\n<\/ul>\n<\/li>\n
                              • \n
                                Option B: Nginx (Known for high performance, often used with static sites or as a reverse proxy)<\/strong><\/p>\n
                                  \n
                                • Ubuntu\/Debian:<\/strong>\n
                                  \n
                                  Bash<\/span><\/p>\n
                                  <\/div>\n<\/div>\n
                                  \n
                                  \n
                                  sudo apt install nginx -y\r\nsudo ufw allow 'Nginx HTTP'<\/span> # Allow HTTP traffic<\/span>\r\nsudo systemctl status nginx\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/li>\n
                                • CentOS\/RHEL:<\/strong>\n
                                  \n
                                  Bash<\/span><\/p>\n
                                  <\/div>\n<\/div>\n
                                  \n
                                  \n
                                  sudo yum install nginx -y\r\nsudo systemctl start nginx\r\nsudo systemctl enable<\/span> nginx\r\nsudo firewall-cmd --permanent --add-service=http\r\nsudo firewall-cmd --permanent --add-service=https\r\nsudo firewall-cmd --reload\r\nsudo systemctl status nginx\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/li>\n
                                • Test:<\/strong> Open your web browser and navigate to your VPS’s IP address. You should see the default Nginx welcome page.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
                                  \n
                                  Step 4: Install a Database Server (e.g., MySQL\/MariaDB)<\/h3>\n
                                  If your website uses a database (like WordPress), you’ll need one.<\/p>\n
                                    \n
                                  • \n
                                    For MySQL (Ubuntu\/Debian):<\/strong><\/p>\n
                                    \n
                                    Bash<\/span><\/p>\n
                                    <\/div>\n<\/div>\n
                                    \n
                                    \n
                                    sudo apt install mysql-server -y\r\nsudo mysql_secure_installation # Run security script<\/span>\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n
                                    (Follow the prompts. Choose “Y” for most questions, set a strong root password, remove anonymous users, disallow remote root login, and remove test database.)<\/p>\n<\/li>\n
                                  • \n
                                    For MariaDB (CentOS\/RHEL):<\/strong><\/p>\n
                                    \n
                                    Bash<\/span><\/p>\n
                                    <\/div>\n<\/div>\n
                                    \n
                                    \n
                                    sudo yum install mariadb-server mariadb -y\r\nsudo systemctl start mariadb\r\nsudo systemctl enable<\/span> mariadb\r\nsudo mysql_secure_installation # Run security script (similar prompts to MySQL)<\/span>\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/li>\n<\/ul>\n
                                    \n
                                    Step 5: Install PHP (If Your Website Uses It, e.g., WordPress)<\/h3>\n
                                    Most dynamic websites (like WordPress, Joomla, Drupal) are built with PHP.<\/p>\n
                                      \n
                                    • \n
                                      For Apache (Ubuntu\/Debian):<\/strong><\/p>\n
                                      \n
                                      Bash<\/span><\/p>\n
                                      <\/div>\n<\/div>\n
                                      \n
                                      \n
                                      sudo apt install php libapache2-mod-php php-mysql -y\r\nsudo systemctl restart apache2\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/li>\n
                                    • \n
                                      For Nginx (Ubuntu\/Debian – requires PHP-FPM):<\/strong><\/p>\n
                                      \n
                                      Bash<\/span><\/p>\n
                                      <\/div>\n<\/div>\n
                                      \n
                                      \n
                                      sudo apt install php-fpm php-mysql -y\r\nsudo systemctl start php-fpm\r\nsudo systemctl enable<\/span> php-fpm\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n
                                      (You’ll also need to configure Nginx to process PHP files \u2013 this is more advanced and involves editing Nginx’s site configuration files to pass .php<\/code> requests to php-fpm<\/code>. For a beginner, Apache is often simpler to start with for PHP sites.)<\/p>\n<\/li>\n
                                    • \n
                                      For CentOS\/RHEL (Apache or Nginx – using EPEL and Remi repositories for recent PHP versions):<\/strong><\/p>\n
                                      \n
                                      Bash<\/span><\/p>\n
                                      <\/div>\n<\/div>\n
                                      \n
                                      \n
                                      sudo yum install epel-release -y\r\nsudo yum install https:\/\/rpms.remirepo.net\/enterprise\/remi-release-8.rpm -y # For CentOS 8+<\/span>\r\n# For CentOS 7: sudo yum install http:\/\/rpms.remirepo.net\/enterprise\/remi-release-7.rpm -y<\/span>\r\nsudo yum module enable<\/span> php:remi-8.1 # Or whatever PHP version you want (e.g., 8.2, 8.3)<\/span>\r\nsudo yum install php php-mysqlnd php-fpm -y # php-fpm for Nginx, php for Apache<\/span>\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n
                                        \n
                                      • If using Apache: sudo systemctl restart httpd<\/code><\/li>\n
                                      • If using Nginx: sudo systemctl start php-fpm && sudo systemctl enable php-fpm && sudo systemctl restart nginx<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
                                        \n
                                        Step 6: Deploy Your Website<\/h3>\n
                                        Now, put your website files onto the server.<\/p>\n
                                          \n
                                        1. \n
                                          Locate the Web Root Directory:<\/strong><\/p>\n
                                            \n
                                          • Apache (Ubuntu\/Debian):<\/strong> \/var\/www\/html\/<\/code><\/li>\n
                                          • Apache (CentOS\/RHEL):<\/strong> \/var\/www\/html\/<\/code><\/li>\n
                                          • Nginx (Ubuntu\/Debian):<\/strong> \/var\/www\/html\/<\/code> (or often \/usr\/share\/nginx\/html\/<\/code> by default, but \/var\/www\/html\/<\/code> is common for custom sites)<\/li>\n
                                          • Nginx (CentOS\/RHEL):<\/strong> \/usr\/share\/nginx\/html\/<\/code><\/li>\n<\/ul>\n<\/li>\n
                                          • \n
                                            Transfer Files:<\/strong> You can use:<\/p>\n
                                              \n
                                            • SCP (Secure Copy Protocol):<\/strong> Built into Linux\/macOS terminals, or available via tools like WinSCP on Windows.\n
                                              \n
                                              Bash<\/span><\/p>\n
                                              <\/div>\n<\/div>\n
                                              \n
                                              \n
                                              # From your local machine to VPS:<\/span>\r\nscp -r \/path\/to\/your\/local<\/span>\/website\/files your_username@your_vps_ip:\/var\/www\/html\/\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/li>\n
                                            • SFTP (SSH File Transfer Protocol):<\/strong> A more user-friendly graphical interface (e.g., FileZilla, WinSCP). Connect using your VPS IP, your_username<\/code>, and password, then drag and drop files to the web root.<\/li>\n<\/ul>\n<\/li>\n
                                            • \n
                                              Set File Permissions (Crucial for Security):<\/strong><\/p>\n
                                                \n
                                              • The web server (e.g., www-data<\/code> user for Apache\/Nginx on Ubuntu, apache<\/code> user for Apache on CentOS, nginx<\/code> user for Nginx on CentOS) needs read access to your files and write access to specific directories (like wp-content<\/code> for WordPress).<\/li>\n
                                              • A common starting point (adjust as needed for specific applications):\n
                                                \n
                                                Bash<\/span><\/p>\n
                                                <\/div>\n<\/div>\n
                                                \n
                                                \n
                                                sudo chown -R your_username:www-data \/var\/www\/html\/your_website_folder # Or the web root<\/span>\r\nsudo chmod -R 755 \/var\/www\/html\/your_website_folder\r\nsudo find \/var\/www\/html\/your_website_folder -type<\/span> d -exec<\/span> chmod g+s {} \\; # For directory permissions<\/span>\r\n# For writeable folders (e.g., WordPress uploads):<\/span>\r\nsudo chmod -R 775 \/var\/www\/html\/your_website_folder\/wp-content\/uploads\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/li>\n<\/ul>\n<\/li>\n
                                              • \n
                                                Configure Your Web Server (Virtual Hosts):<\/strong> If you’re hosting multiple websites or using a domain name, you’ll need to set up a virtual host (Apache) or server block (Nginx).<\/p>\n
                                                  \n
                                                • Apache Example (Ubuntu):<\/strong>\n
                                                  \n
                                                  Bash<\/span><\/p>\n
                                                  <\/div>\n<\/div>\n
                                                  \n
                                                  \n
                                                  sudo nano \/etc\/apache2\/sites-available\/your_domain.conf\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n
                                                  Add content like this:<\/p>\n
                                                  \n
                                                  Apache<\/span><\/p>\n
                                                  <\/div>\n<\/div>\n
                                                  \n
                                                  \n
                                                  <VirtualHost *:80<\/span>><\/span>\r\n    ServerAdmin<\/span> webmaster@your_domain.com\r\n    ServerName<\/span><\/span> your_domain.com\r\n    ServerAlias<\/span> www.your_domain.com\r\n    DocumentRoot<\/span><\/span> \/var\/www\/html\/your_website_folder\r\n    ErrorLog<\/span> ${APACHE_LOG_DIR}<\/span>\/error.log\r\n    CustomLog<\/span> ${APACHE_LOG_DIR}<\/span>\/access.log combined\r\n\r\n    <Directory \/var\/www\/html\/your_website_folder><\/span>\r\n        Options<\/span><\/span> Indexes FollowSymLinks\r\n        AllowOverride<\/span> All<\/span>\r\n        Require<\/span> all<\/span> granted\r\n    <\/Directory><\/span>\r\n<\/VirtualHost><\/span>\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n
                                                  Enable the site and restart Apache:<\/p>\n
                                                  \n
                                                  Bash<\/span><\/p>\n
                                                  <\/div>\n<\/div>\n
                                                  \n
                                                  \n
                                                  sudo a2ensite your_domain.conf\r\nsudo systemctl restart apache2\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/li>\n
                                                • Nginx Example (Ubuntu):<\/strong>\n
                                                  \n
                                                  Bash<\/span><\/p>\n
                                                  <\/div>\n<\/div>\n
                                                  \n
                                                  \n
                                                  sudo nano \/etc\/nginx\/sites-available\/your_domain.conf\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n
                                                  Add content like this (for static HTML, add index.html<\/code> to index<\/code> directive; for PHP, add index.php<\/code> and uncomment the location ~ \\.php$<\/code> block):<\/p>\n
                                                  \n
                                                  Nginx<\/span><\/p>\n
                                                  <\/div>\n<\/div>\n
                                                  \n
                                                  \n
                                                  server<\/span> {\r\n    listen<\/span> 80<\/span>;\r\n    listen<\/span> [::]:80<\/span>;\r\n\r\n    root<\/span> \/var\/www\/html\/your_website_folder;\r\n    index<\/span> index.html index.htm index.nginx-debian.html;\r\n\r\n    server_name<\/span> your_domain.com www.your_domain.com;\r\n\r\n    location<\/span> \/ {\r\n        try_files<\/span> $uri $uri\/ =404<\/span>;\r\n    }\r\n\r\n    # For PHP websites (uncomment and configure php-fpm socket path)<\/span>\r\n    # location ~ \\.php$ {<\/span>\r\n    #    include snippets\/fastcgi-php.conf;<\/span>\r\n    #    fastcgi_pass unix:\/var\/run\/php\/php8.1-fpm.sock; # Adjust PHP version<\/span>\r\n    # }<\/span>\r\n}\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n
                                                  Link to sites-enabled and restart Nginx:<\/p>\n
                                                  \n
                                                  Bash<\/span><\/p>\n
                                                  <\/div>\n<\/div>\n
                                                  \n
                                                  \n
                                                  sudo ln -s \/etc\/nginx\/sites-available\/your_domain.conf \/etc\/nginx\/sites-enabled\/\r\nsudo nginx -t # Test configuration<\/span>\r\nsudo systemctl restart nginx\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n
                                                  \n
                                                  Step 7: Point Your Domain Name to Your VPS<\/h3>\n
                                                    \n
                                                  1. Go to your domain registrar’s DNS management page.<\/strong><\/li>\n
                                                  2. Find your DNS records.<\/strong><\/li>\n
                                                  3. Edit or add an A record:<\/strong>\n
                                                      \n
                                                    • Host\/Name:<\/strong> @<\/code> (for the main domain)<\/li>\n
                                                    • Value\/IP Address:<\/strong> Your VPS’s IP address<\/li>\n
                                                    • TTL (Time To Live):<\/strong> Often 3600 (1 hour) or less for faster propagation.<\/li>\n<\/ul>\n<\/li>\n
                                                    • Add a CNAME record for www<\/code> (optional but recommended):<\/strong>\n
                                                        \n
                                                      • Host\/Name:<\/strong> www<\/code><\/li>\n
                                                      • Value:<\/strong> your_domain.com<\/code> (or @<\/code>)<\/li>\n<\/ul>\n<\/li>\n
                                                      • Save the changes.<\/strong> DNS propagation can take a few minutes to up to 48 hours, but usually much faster.<\/li>\n<\/ol>\n
                                                        \n
                                                        Step 8: Install SSL (HTTPS) – Highly Recommended<\/h3>\n
                                                        Once your domain is pointing to your VPS, secure your website with an SSL certificate using Let’s Encrypt and Certbot. This is free and essential for security and SEO.<\/p>\n
                                                          \n
                                                        • \n
                                                          For Apache (Ubuntu):<\/strong><\/p>\n
                                                          \n
                                                          Bash<\/span><\/p>\n
                                                          <\/div>\n<\/div>\n
                                                          \n
                                                          \n
                                                          sudo snap install core\r\nsudo snap refresh core\r\nsudo snap install --classic certbot\r\nsudo ln -s \/snap\/bin\/certbot \/usr\/bin\/certbot\r\nsudo certbot --apache\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n
                                                          Follow the prompts.<\/p>\n<\/li>\n
                                                        • \n
                                                          For Nginx (Ubuntu):<\/strong><\/p>\n
                                                          \n
                                                          Bash<\/span><\/p>\n
                                                          <\/div>\n<\/div>\n
                                                          \n
                                                          \n
                                                          sudo snap install core\r\nsudo snap refresh core\r\nsudo snap install --classic certbot\r\nsudo ln -s \/snap\/bin\/certbot \/usr\/bin\/certbot\r\nsudo certbot --nginx\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n
                                                          Follow the prompts.<\/p>\n<\/li>\n
                                                        • \n
                                                          For CentOS (Apache\/Nginx):<\/strong><\/p>\n
                                                          \n
                                                          Bash<\/span><\/p>\n
                                                          <\/div>\n<\/div>\n
                                                          \n
                                                          \n
                                                          sudo yum install epel-release -y\r\nsudo yum install certbot python3-certbot-apache -y # For Apache<\/span>\r\n# Or: sudo yum install certbot python3-certbot-nginx -y # For Nginx<\/span>\r\nsudo certbot --apache # Or --nginx<\/span>\r\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n
                                                          Follow the prompts.<\/p>\n<\/li>\n<\/ul>\n
                                                          After this, your site should be accessible via https:\/\/your_domain.com<\/code>.<\/p>\n
                                                          \n
                                                          Step 9: Ongoing Maintenance<\/h3>\n
                                                            \n
                                                          • Regular Updates:<\/strong> Log in periodically and run sudo apt update && sudo apt upgrade -y<\/code> (Ubuntu) or sudo yum update -y<\/code> (CentOS).<\/li>\n
                                                          • Backups:<\/strong> Set up an automated backup solution. Your VPS provider might offer this, or you can use tools like rsync<\/code> or cloud storage solutions.<\/li>\n
                                                          • Monitoring:<\/strong> Keep an eye on server resource usage (CPU, RAM, disk space). Tools like htop<\/code> (install with sudo apt install htop<\/code> or sudo yum install htop<\/code>) are useful.<\/li>\n
                                                          • Security:<\/strong> Stay informed about common vulnerabilities and best practices.<\/li>\n<\/ul>\n
                                                            \n
                                                            This tutorial covers the absolute basics. A VPS offers immense power, but with that comes responsibility. Don’t be afraid to search online for specific issues or configurations you encounter. Good luck!<\/p>\n","protected":false},"excerpt":{"rendered":"
                                                            Setting up a VPS for the first time can seem daunting, but it’s a rewarding experience that gives you much more control over your web presence. This tutorial will guide you through the basic steps. We’ll focus on a common scenario: a Linux-based VPS (Ubuntu or CentOS are popular choices) for hosting a website. Prerequisites: […]<\/p>\n","protected":false},"author":226,"featured_media":26526,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"tdm_status":"","tdm_grid_status":"","footnotes":""},"categories":[163],"tags":[],"class_list":{"0":"post-26525","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-hosting"},"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/posts\/26525","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/users\/226"}],"replies":[{"embeddable":true,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/comments?post=26525"}],"version-history":[{"count":1,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/posts\/26525\/revisions"}],"predecessor-version":[{"id":26527,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/posts\/26525\/revisions\/26527"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/media\/26526"}],"wp:attachment":[{"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/media?parent=26525"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/categories?post=26525"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/tags?post=26525"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}