<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Volyte</title>
    <description>The latest articles on DEV Community by Volyte (@volyte).</description>
    <link>https://dev.to/volyte</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4206366%2F8b7c5cab-7ff3-4f92-aa2c-0ec8b3e1e0e9.png</url>
      <title>DEV Community: Volyte</title>
      <link>https://dev.to/volyte</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/volyte"/>
    <language>en</language>
    <item>
      <title>cPanel vs Plesk: Which Control Panel to Choose?</title>
      <dc:creator>Volyte</dc:creator>
      <pubDate>Fri, 20 Nov 2026 08:19:14 +0000</pubDate>
      <link>https://dev.to/volyte/cpanel-vs-plesk-which-control-panel-to-choose-1a6</link>
      <guid>https://dev.to/volyte/cpanel-vs-plesk-which-control-panel-to-choose-1a6</guid>
      <description>&lt;p&gt;&lt;strong&gt;cPanel&lt;/strong&gt; and &lt;strong&gt;Plesk&lt;/strong&gt; are the two best-known control panels for running websites on a server. Both let you add domains, create email accounts, manage databases and get free SSL certificates from a browser, without typing commands. Both are good. The right one depends mostly on &lt;strong&gt;what your sites are built with&lt;/strong&gt; and &lt;strong&gt;how many you host&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Here is the short version, then the details.&lt;/p&gt;

&lt;h2&gt;
  
  
  The short answer
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Your sites use ASP.NET, .NET or Microsoft SQL Server?&lt;/strong&gt; Choose &lt;strong&gt;Plesk on Windows&lt;/strong&gt;. cPanel does not run on Windows at all.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You host many PHP or WordPress sites for clients, and your team already knows cPanel?&lt;/strong&gt; Choose &lt;strong&gt;cPanel&lt;/strong&gt;. It is the panel most web hosts use, so clients and freelancers find it familiar.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You want one clean panel for a handful of your own sites, on Linux or Windows?&lt;/strong&gt; Choose &lt;strong&gt;Plesk&lt;/strong&gt;. Its single, site-focused screen is easier for beginners, and its licence costs less for a few sites.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Only one or two small websites?&lt;/strong&gt; You may not need either on a VPS. Shared &lt;a href="https://volyte.com/web-hosting" rel="noopener noreferrer"&gt;web hosting&lt;/a&gt; already includes cPanel, email and SSL, and the host manages the server.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  cPanel vs Plesk at a glance
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;cPanel &amp;amp; WHM&lt;/th&gt;
&lt;th&gt;Plesk&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Operating system&lt;/td&gt;
&lt;td&gt;Linux only (AlmaLinux, Ubuntu and similar)&lt;/td&gt;
&lt;td&gt;Linux &lt;strong&gt;and&lt;/strong&gt; Windows Server&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Layout&lt;/td&gt;
&lt;td&gt;Two panels: &lt;strong&gt;WHM&lt;/strong&gt; for the server, &lt;strong&gt;cPanel&lt;/strong&gt; for each site's account&lt;/td&gt;
&lt;td&gt;One panel with a "Websites &amp;amp; Domains" view, for admin and site owners&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Best known for&lt;/td&gt;
&lt;td&gt;Hosting companies, agencies, many separate client accounts&lt;/td&gt;
&lt;td&gt;Windows / ASP.NET hosting, WordPress, developers&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Languages&lt;/td&gt;
&lt;td&gt;PHP (several versions), Node.js, Python, Ruby&lt;/td&gt;
&lt;td&gt;PHP, Node.js, Python, Ruby; on Windows also ASP.NET and .NET&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Databases&lt;/td&gt;
&lt;td&gt;MySQL / MariaDB, PostgreSQL&lt;/td&gt;
&lt;td&gt;MySQL / MariaDB, PostgreSQL; on Windows also MSSQL&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;WordPress&lt;/td&gt;
&lt;td&gt;WP Toolkit for installs and updates&lt;/td&gt;
&lt;td&gt;WP Toolkit (Plesk built it): installs, updates, staging, security checks&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Free SSL&lt;/td&gt;
&lt;td&gt;AutoSSL, automatic for every site and mailbox&lt;/td&gt;
&lt;td&gt;Let's Encrypt / SSL It!, a few clicks per site&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Licence is priced by&lt;/td&gt;
&lt;td&gt;Number of cPanel accounts&lt;/td&gt;
&lt;td&gt;Edition, by number of domains (10 / 30 / unlimited)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  1. Operating system: the one hard rule
&lt;/h2&gt;

&lt;p&gt;This is the only point that decides things on its own. &lt;strong&gt;cPanel runs only on Linux.&lt;/strong&gt; If your website or app is built on &lt;strong&gt;ASP.NET, classic ASP or .NET Framework&lt;/strong&gt;, or needs &lt;strong&gt;Microsoft SQL Server&lt;/strong&gt;, you need a Windows server, and on Windows the panel to use is Plesk.&lt;/p&gt;

&lt;p&gt;If your sites are PHP, WordPress, Laravel, Node.js or Python, both panels work. Keep reading. (Not sure which operating system you need? See &lt;a href="https://volyte.com/blog/linux-vps-vs-windows-vps" rel="noopener noreferrer"&gt;Linux VPS vs Windows VPS&lt;/a&gt;.)&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Ease of use
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;cPanel&lt;/strong&gt; splits the work in two. You log in to &lt;strong&gt;WHM&lt;/strong&gt; (WebHost Manager) as the server owner to create accounts, set PHP versions and manage the server. Each website then gets its own &lt;strong&gt;cPanel&lt;/strong&gt; account, with its own login, files, email and databases. The cPanel screen is a grid of icons: File Manager, Email Accounts, MySQL Databases and so on. It is not modern, but millions of people already know where everything is.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Plesk&lt;/strong&gt; uses one panel. You see a list of your websites, and everything for a site (files, databases, SSL, PHP settings, WordPress, Git) sits on that site's card. Most first-time users find Plesk quicker to learn, and it feels more like a modern web app.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;In short:&lt;/strong&gt; Plesk is easier for beginners. cPanel is easier if you or your clients already use it.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Hosting many clients
&lt;/h2&gt;

&lt;p&gt;This is where cPanel is strongest. Each client gets a &lt;strong&gt;completely separate cPanel account&lt;/strong&gt; with their own login, disk space and email, and you manage all of them from WHM. One client's mistake stays inside their own account. You can also create &lt;strong&gt;reseller accounts&lt;/strong&gt; in WHM if you sell hosting to others.&lt;/p&gt;

&lt;p&gt;Plesk can do this too. You add "customers" and "subscriptions", and give each client their own login. Reseller accounts need the top &lt;strong&gt;Web Host&lt;/strong&gt; edition. For an agency that already sells cPanel hosting, cPanel is usually less work. For a business running its own sites, Plesk's single view is simpler.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. WordPress
&lt;/h2&gt;

&lt;p&gt;Both panels include &lt;strong&gt;WP Toolkit&lt;/strong&gt;, which Plesk created. It installs WordPress in one click, updates core, plugins and themes, makes a &lt;strong&gt;staging copy&lt;/strong&gt; to test changes and checks basic security settings. Some advanced features, such as Smart Updates, need the Deluxe add-on on cPanel or the Web Pro / Web Host edition on Plesk. Plesk has had it longer and builds it into its main screen, so it feels slightly smoother there. Either way, managing many WordPress sites from one place is easy.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Email
&lt;/h2&gt;

&lt;p&gt;Both give you mailboxes, forwarders, autoresponders, webmail and spam filtering on your own domains, with no fee per mailbox. Email is a draw. Whichever panel you choose, set up &lt;strong&gt;SPF, DKIM and DMARC&lt;/strong&gt; records so your mail lands in the inbox and not in spam. Both panels can create them for you.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Developers
&lt;/h2&gt;

&lt;p&gt;Both support several PHP versions per site, Node.js and Python apps, Git deployment, cron jobs and SSH. Plesk adds Docker and more developer extensions from its built-in catalogue. cPanel leans on WHM settings and full root access. On a VPS you get &lt;strong&gt;root (or Administrator) access&lt;/strong&gt; with either panel, so nothing stops you installing what you need.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Price
&lt;/h2&gt;

&lt;p&gt;Both are paid licences, billed monthly on top of the server.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;cPanel&lt;/strong&gt; is priced by the &lt;strong&gt;number of cPanel accounts&lt;/strong&gt; (roughly one per website or client). Prices have gone up several times in recent years, which is why cPanel is now the more expensive of the two for most people.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Plesk&lt;/strong&gt; is priced by &lt;strong&gt;edition&lt;/strong&gt;: Web Admin (up to 10 sites), Web Pro (up to 30) and Web Host (unlimited).&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  8. Moving between them
&lt;/h2&gt;

&lt;p&gt;Already on one panel and thinking of switching? Plesk has a free &lt;strong&gt;Plesk Migrator&lt;/strong&gt; that can import sites, databases and email from a cPanel server. Going the other way, or between cPanel servers, WHM has its own Transfer Tool. Some settings may still need a manual check after a move.&lt;/p&gt;

&lt;h2&gt;
  
  
  What about free panels?
&lt;/h2&gt;

&lt;p&gt;If the licence cost matters more than the brand, free panels such as &lt;strong&gt;CyberPanel&lt;/strong&gt; and &lt;strong&gt;aaPanel&lt;/strong&gt;, or the low-cost &lt;strong&gt;DirectAdmin&lt;/strong&gt;, can run your sites well. They have smaller communities and fewer ready answers when something breaks. You can also skip the panel entirely: developers often run a plain Linux VPS and manage everything over SSH. Start with &lt;a href="https://volyte.com/blog/secure-linux-vps" rel="noopener noreferrer"&gt;securing your Linux VPS&lt;/a&gt; if you go that way.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which one to choose
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;If you…&lt;/th&gt;
&lt;th&gt;Choose&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Run ASP.NET, .NET or MSSQL sites&lt;/td&gt;
&lt;td&gt;Plesk on Windows&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Host many client sites, each with its own login&lt;/td&gt;
&lt;td&gt;cPanel&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Have a few of your own PHP or WordPress sites and want the easier panel&lt;/td&gt;
&lt;td&gt;Plesk on Linux&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Are moving from a host that used cPanel and want nothing to change&lt;/td&gt;
&lt;td&gt;cPanel&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Have one or two small sites&lt;/td&gt;
&lt;td&gt;Shared web hosting (cPanel included)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Are a developer and don't want a panel&lt;/td&gt;
&lt;td&gt;A plain Linux VPS&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Is Plesk better than cPanel?&lt;/strong&gt;&lt;br&gt;
Neither is better for everyone. Plesk runs on Linux and Windows and is easier for beginners. cPanel runs only on Linux and is the more familiar choice for hosting many separate client accounts.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can cPanel run on Windows?&lt;/strong&gt;&lt;br&gt;
No. cPanel runs only on Linux. For ASP.NET, .NET or Microsoft SQL Server sites on a Windows server, use Plesk.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Which is cheaper?&lt;/strong&gt;&lt;br&gt;
For most small setups, Plesk. cPanel is priced by the number of accounts, while Plesk is priced by edition (up to 10 sites, up to 30, or unlimited).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can I move my sites from cPanel to Plesk?&lt;/strong&gt;&lt;br&gt;
Yes. Plesk Migrator can import sites, databases and email from a cPanel server.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do I need a control panel on a VPS?&lt;/strong&gt;&lt;br&gt;
No. A panel makes websites, email and SSL easy to manage from a browser, but many developers run a plain Linux VPS and manage everything over SSH.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on the &lt;a href="https://volyte.com/blog/cpanel-vs-plesk" rel="noopener noreferrer"&gt;Volyte blog&lt;/a&gt;. Want either panel ready to go? Our &lt;a href="https://volyte.com/cpanel-vps" rel="noopener noreferrer"&gt;cPanel VPS&lt;/a&gt; and &lt;a href="https://volyte.com/plesk-vps" rel="noopener noreferrer"&gt;Plesk VPS&lt;/a&gt; run on NVMe in India, Europe or the US, same price at renewal.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>cpanel</category>
      <category>plesk</category>
      <category>webdev</category>
      <category>devops</category>
    </item>
    <item>
      <title>How to Install WordPress on a VPS (Nginx + PHP + MariaDB + Free SSL)</title>
      <dc:creator>Volyte</dc:creator>
      <pubDate>Fri, 13 Nov 2026 02:37:11 +0000</pubDate>
      <link>https://dev.to/volyte/how-to-install-wordpress-on-a-vps-nginx-php-mariadb-free-ssl-3fj5</link>
      <guid>https://dev.to/volyte/how-to-install-wordpress-on-a-vps-nginx-php-mariadb-free-ssl-3fj5</guid>
      <description>&lt;p&gt;Running WordPress on your own &lt;strong&gt;VPS&lt;/strong&gt; gives you full control: your own PHP settings, no "resource limit reached" emails, and room to grow. This guide installs it the fast, modern way, on what's called a &lt;strong&gt;LEMP stack&lt;/strong&gt;: &lt;strong&gt;L&lt;/strong&gt;inux, &lt;strong&gt;N&lt;/strong&gt;ginx ("engine-x"), &lt;strong&gt;M&lt;/strong&gt;ariaDB (a drop-in MySQL) and &lt;strong&gt;P&lt;/strong&gt;HP, plus a free SSL certificate. It takes about 20 minutes.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you need
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A Linux VPS with &lt;strong&gt;Ubuntu 24.04&lt;/strong&gt;. One small business site runs well on 2 GB RAM; for WooCommerce or several sites, choose 4 GB or more (see &lt;a href="https://volyte.com/blog/how-much-ram-cpu-vps" rel="noopener noreferrer"&gt;how much RAM and CPU your VPS needs&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;Your &lt;strong&gt;domain&lt;/strong&gt; pointing to the server: an &lt;strong&gt;A record&lt;/strong&gt; for &lt;code&gt;example.com&lt;/code&gt; and one for &lt;code&gt;www&lt;/code&gt;. Follow &lt;a href="https://volyte.com/blog/point-domain-to-vps" rel="noopener noreferrer"&gt;how to point your domain to your VPS&lt;/a&gt; first; the SSL step fails if DNS isn't ready.&lt;/li&gt;
&lt;li&gt;A secured server. On a brand-new VPS, do the &lt;a href="https://volyte.com/blog/secure-linux-vps" rel="noopener noreferrer"&gt;first security steps&lt;/a&gt; before anything else.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In every command and file below, replace &lt;code&gt;example.com&lt;/code&gt; with your own domain.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Install Nginx, PHP and MariaDB
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo apt update
sudo apt install -y nginx mariadb-server php-fpm php-mysql php-curl php-gd php-intl php-mbstring php-xml php-zip php-imagick unzip
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Ubuntu 24.04 installs &lt;strong&gt;PHP 8.3&lt;/strong&gt;. Check the version and the PHP-FPM socket name, because you need it in step 4:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;php -v
ls /run/php/
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You should see &lt;code&gt;php8.3-fpm.sock&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Open the firewall
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo ufw allow &lt;span class="s1"&gt;'Nginx Full'&lt;/span&gt;
sudo ufw status
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This opens ports 80 and 443. Port 80 is needed for the free certificate in step 6.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Create the database
&lt;/h2&gt;

&lt;p&gt;First run the security script: press Enter for the current root password (there is none), then answer &lt;strong&gt;Y&lt;/strong&gt; to the questions that remove test users and the test database.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo mariadb-secure-installation
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then create a database and a user just for WordPress. Choose your own strong password:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo mariadb
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="k"&gt;CREATE&lt;/span&gt; &lt;span class="k"&gt;DATABASE&lt;/span&gt; &lt;span class="n"&gt;wordpress&lt;/span&gt; &lt;span class="k"&gt;DEFAULT&lt;/span&gt; &lt;span class="kt"&gt;CHARACTER&lt;/span&gt; &lt;span class="k"&gt;SET&lt;/span&gt; &lt;span class="n"&gt;utf8mb4&lt;/span&gt; &lt;span class="k"&gt;COLLATE&lt;/span&gt; &lt;span class="n"&gt;utf8mb4_unicode_ci&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;CREATE&lt;/span&gt; &lt;span class="no"&gt;USER&lt;/span&gt; &lt;span class="s1"&gt;'wpuser'&lt;/span&gt;@&lt;span class="s1"&gt;'localhost'&lt;/span&gt; &lt;span class="no"&gt;IDENTIFIED&lt;/span&gt; &lt;span class="k"&gt;BY&lt;/span&gt; &lt;span class="s1"&gt;'Use-A-Strong-Password-Here'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;GRANT&lt;/span&gt; &lt;span class="k"&gt;ALL&lt;/span&gt; &lt;span class="no"&gt;PRIVILEGES&lt;/span&gt; &lt;span class="k"&gt;ON&lt;/span&gt; &lt;span class="n"&gt;wordpress&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="k"&gt;TO&lt;/span&gt; &lt;span class="s1"&gt;'wpuser'&lt;/span&gt;@&lt;span class="s1"&gt;'localhost'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="no"&gt;FLUSH&lt;/span&gt; &lt;span class="no"&gt;PRIVILEGES&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="no"&gt;EXIT&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;WordPress gets its own user with access to &lt;strong&gt;only its own database&lt;/strong&gt;, so a problem in one site can't touch anything else.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Download WordPress and set up Nginx
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;cd&lt;/span&gt; /tmp
curl -O https://wordpress.org/latest.tar.gz
tar xzf latest.tar.gz
sudo mv wordpress /var/www/example.com
sudo chown -R www-data:www-data /var/www/example.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Now tell Nginx about the site:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo nano /etc/nginx/sites-available/example.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight nginx"&gt;&lt;code&gt;&lt;span class="n"&gt;server&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;listen&lt;/span&gt; &lt;span class="mi"&gt;80&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="n"&gt;server_name&lt;/span&gt; &lt;span class="n"&gt;example&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;com&lt;/span&gt; &lt;span class="n"&gt;www&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;example&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;com&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="n"&gt;root&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="kd"&gt;var&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;www&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;example&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;com&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="n"&gt;index&lt;/span&gt; &lt;span class="n"&gt;index&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;php&lt;/span&gt; &lt;span class="n"&gt;index&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;html&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="n"&gt;client_max_body_size&lt;/span&gt; &lt;span class="mi"&gt;64M&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

    &lt;span class="n"&gt;location&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="n"&gt;try_files&lt;/span&gt; $&lt;span class="n"&gt;uri&lt;/span&gt; $&lt;span class="n"&gt;uri&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;index&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;php&lt;/span&gt;&lt;span class="o"&gt;?&lt;/span&gt;$&lt;span class="n"&gt;args&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;

    &lt;span class="n"&gt;location&lt;/span&gt; &lt;span class="o"&gt;~&lt;/span&gt; \&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;php&lt;/span&gt;$ &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="n"&gt;include&lt;/span&gt; &lt;span class="n"&gt;snippets&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;fastcgi&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;php&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;conf&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
        &lt;span class="n"&gt;fastcgi_pass&lt;/span&gt; &lt;span class="n"&gt;unix&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;run&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;php&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;php8&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;3&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;fpm&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;sock&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;

    &lt;span class="na"&gt;location&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;xmlrpc&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;php&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;deny&lt;/span&gt; &lt;span class="n"&gt;all&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="n"&gt;location&lt;/span&gt; &lt;span class="o"&gt;~&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt;\&lt;span class="p"&gt;.&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;deny&lt;/span&gt; &lt;span class="n"&gt;all&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Enable it, switch off the default page, test and reload:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo ln -s /etc/nginx/sites-available/example.com /etc/nginx/sites-enabled/
sudo rm /etc/nginx/sites-enabled/default
sudo nginx -t
sudo systemctl reload nginx
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;What the important lines do:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;try_files … /index.php?$args&lt;/code&gt; makes WordPress "pretty" links (like &lt;code&gt;/about-us/&lt;/code&gt;) work. Without it they show 404.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;client_max_body_size 64M&lt;/code&gt; lets you upload themes, plugins and images up to 64 MB.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;xmlrpc.php&lt;/code&gt; is blocked because bots use it for password-guessing attacks, and most sites don't need it. If you use the Jetpack plugin or the WordPress mobile app, remove that line.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  5. Raise PHP's upload and memory limits
&lt;/h2&gt;

&lt;p&gt;PHP's defaults (2 MB uploads) are too small for WordPress. Open the settings file:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo nano /etc/php/8.3/fpm/php.ini
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Find and change these lines (in nano, &lt;strong&gt;Ctrl+W&lt;/strong&gt; searches):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight ini"&gt;&lt;code&gt;&lt;span class="na"&gt;upload_max_filesize&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;64M&lt;/span&gt;
&lt;span class="na"&gt;post_max_size&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;64M&lt;/span&gt;
&lt;span class="na"&gt;memory_limit&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;256M&lt;/span&gt;
&lt;span class="na"&gt;max_execution_time&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;120&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo systemctl restart php8.3-fpm
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  6. Get a free SSL certificate
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo apt install -y certbot python3-certbot-nginx
sudo certbot --nginx -d example.com -d www.example.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Enter your email and agree to the terms. Certbot gets a free &lt;strong&gt;Let's Encrypt&lt;/strong&gt; certificate, adds HTTPS to your Nginx file and redirects HTTP to HTTPS. Certificates &lt;strong&gt;renew automatically&lt;/strong&gt;; check renewal works with:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo certbot renew --dry-run
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  7. Run the WordPress installer
&lt;/h2&gt;

&lt;p&gt;Open &lt;code&gt;https://example.com&lt;/code&gt;. Choose your language, then enter:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Database name:&lt;/strong&gt; &lt;code&gt;wordpress&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Username:&lt;/strong&gt; &lt;code&gt;wpuser&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Password:&lt;/strong&gt; the one you chose in step 3&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Database host:&lt;/strong&gt; &lt;code&gt;localhost&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Table prefix:&lt;/strong&gt; keep &lt;code&gt;wp_&lt;/code&gt;, or change it to something like &lt;code&gt;v7k_&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Then set your site title and admin account. &lt;strong&gt;Don't use "admin" as the username&lt;/strong&gt;; bots try it first. Use a long password.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. Five things to do right after
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Permalinks:&lt;/strong&gt; Settings → Permalinks → &lt;strong&gt;Post name&lt;/strong&gt;. Clean URLs are better for visitors and Google.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Block file editing in the dashboard&lt;/strong&gt;, so a stolen password can't be used to change PHP code. Add this line to &lt;code&gt;/var/www/example.com/wp-config.php&lt;/code&gt;, above "That's all, stop editing": &lt;code&gt;define('DISALLOW_FILE_EDIT', true);&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Updates:&lt;/strong&gt; keep WordPress, themes and plugins up to date, and delete the ones you don't use. Outdated plugins are the most common way WordPress sites get hacked.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Backups:&lt;/strong&gt; turn on server snapshots, and add a backup plugin that copies your files and database off the server (for example to Google Drive).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Caching:&lt;/strong&gt; install a caching plugin to make pages load faster and use less CPU.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Common problems
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Problem&lt;/th&gt;
&lt;th&gt;Usual fix&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;502 Bad Gateway&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;The PHP socket name in your Nginx file doesn't match. Run &lt;code&gt;ls /run/php/&lt;/code&gt;, fix the &lt;code&gt;fastcgi_pass&lt;/code&gt; line, then &lt;code&gt;sudo nginx -t &amp;amp;&amp;amp; sudo systemctl reload nginx&lt;/code&gt;.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Error establishing a database connection&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Wrong database name, user or password in &lt;code&gt;wp-config.php&lt;/code&gt;, or MariaDB is stopped: &lt;code&gt;sudo systemctl status mariadb&lt;/code&gt;.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pages other than the home page show &lt;strong&gt;404&lt;/strong&gt;
&lt;/td&gt;
&lt;td&gt;The &lt;code&gt;try_files&lt;/code&gt; line is missing from the Nginx file.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;"The uploaded file exceeds the upload_max_filesize"&lt;/td&gt;
&lt;td&gt;Raise both PHP's limits (step 5) and Nginx's &lt;code&gt;client_max_body_size&lt;/code&gt;, then restart PHP-FPM and reload Nginx.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;WordPress asks for FTP details to install plugins&lt;/td&gt;
&lt;td&gt;File ownership is wrong. Run &lt;code&gt;sudo chown -R www-data:www-data /var/www/example.com&lt;/code&gt;.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Certbot fails&lt;/td&gt;
&lt;td&gt;The domain doesn't point to the server yet, or port 80 is closed. Check with &lt;code&gt;dig +short example.com&lt;/code&gt; and &lt;code&gt;sudo ufw status&lt;/code&gt;.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;p&gt;&lt;em&gt;Originally published on the &lt;a href="https://volyte.com/blog/install-wordpress-on-vps" rel="noopener noreferrer"&gt;Volyte blog&lt;/a&gt;. Rather not manage the server yourself? Our &lt;a href="https://volyte.com/wordpress-hosting" rel="noopener noreferrer"&gt;WordPress hosting&lt;/a&gt; runs on NVMe with free SSL and weekly backups, same price at renewal.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>nginx</category>
      <category>linux</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>How to Install n8n on a VPS (Docker + Free HTTPS)</title>
      <dc:creator>Volyte</dc:creator>
      <pubDate>Fri, 06 Nov 2026 06:20:02 +0000</pubDate>
      <link>https://dev.to/volyte/how-to-install-n8n-on-a-vps-docker-free-https-3jeb</link>
      <guid>https://dev.to/volyte/how-to-install-n8n-on-a-vps-docker-free-https-3jeb</guid>
      <description>&lt;p&gt;&lt;strong&gt;n8n&lt;/strong&gt; is a workflow automation tool, like Zapier or Make, that you can run on your own server. Self-hosting it means &lt;strong&gt;no limit on workflow executions&lt;/strong&gt;: you pay for the server, not per run, and your API keys and data stay on a machine you control.&lt;/p&gt;

&lt;p&gt;This guide sets up n8n the clean way: in &lt;strong&gt;Docker&lt;/strong&gt;, behind &lt;strong&gt;Caddy&lt;/strong&gt;, a small web server that gets a free HTTPS certificate automatically and renews it on its own. It takes about 15 minutes.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you need
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A Linux VPS with &lt;strong&gt;Ubuntu 24.04&lt;/strong&gt; (Debian 12 works the same). 2 GB RAM is enough to try n8n; for real business workflows choose 4 GB or more (see &lt;a href="https://volyte.com/blog/how-much-ram-cpu-vps" rel="noopener noreferrer"&gt;how much RAM and CPU your VPS needs&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;subdomain&lt;/strong&gt; for n8n, for example &lt;code&gt;n8n.example.com&lt;/code&gt;, with an &lt;strong&gt;A record&lt;/strong&gt; pointing to your server's IP. Not sure how? Follow &lt;a href="https://volyte.com/blog/point-domain-to-vps" rel="noopener noreferrer"&gt;how to point your domain to your VPS&lt;/a&gt; first. The subdomain must already point to the server, or the certificate can't be issued.&lt;/li&gt;
&lt;li&gt;A secured server. If it's brand new, do the &lt;a href="https://volyte.com/blog/secure-linux-vps" rel="noopener noreferrer"&gt;8 first security steps&lt;/a&gt; before anything else.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In the commands below, replace &lt;code&gt;n8n.example.com&lt;/code&gt; with your own subdomain.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Install Docker
&lt;/h2&gt;

&lt;p&gt;Docker's official install script adds Docker and the Compose plugin in one go:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-fsSL&lt;/span&gt; https://get.docker.com | &lt;span class="nb"&gt;sudo &lt;/span&gt;sh
&lt;span class="nb"&gt;sudo &lt;/span&gt;usermod &lt;span class="nt"&gt;-aG&lt;/span&gt; docker &lt;span class="nv"&gt;$USER&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Log out and log back in so the second line takes effect, then check it works:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker &lt;span class="nt"&gt;--version&lt;/span&gt;
docker compose version
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  2. Check the subdomain points to the server
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;dig +short n8n.example.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It should print your server's IP. If it prints nothing or an old IP, wait a few minutes for DNS to update before going on.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Open ports 80 and 443
&lt;/h2&gt;

&lt;p&gt;Caddy needs both: port 80 to prove you own the domain, and port 443 for HTTPS.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;ufw allow 80,443/tcp
&lt;span class="nb"&gt;sudo &lt;/span&gt;ufw status
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Note that we will &lt;strong&gt;not&lt;/strong&gt; open n8n's own port, 5678. n8n is only reachable through Caddy, over HTTPS.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Create the n8n folder and settings
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;mkdir&lt;/span&gt; ~/n8n &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="nb"&gt;cd&lt;/span&gt; ~/n8n
nano docker-compose.yml
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Paste this in, change the two lines with &lt;code&gt;n8n.example.com&lt;/code&gt;, and set your time zone if you are not in India:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;services&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;n8n&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;image&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;docker.n8n.io/n8nio/n8n&lt;/span&gt;
    &lt;span class="na"&gt;restart&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;unless-stopped&lt;/span&gt;
    &lt;span class="na"&gt;environment&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s"&gt;N8N_HOST=n8n.example.com&lt;/span&gt;
      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s"&gt;N8N_PROTOCOL=https&lt;/span&gt;
      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s"&gt;N8N_PORT=5678&lt;/span&gt;
      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s"&gt;WEBHOOK_URL=https://n8n.example.com/&lt;/span&gt;
      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s"&gt;N8N_PROXY_HOPS=1&lt;/span&gt;
      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s"&gt;GENERIC_TIMEZONE=Asia/Kolkata&lt;/span&gt;
      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s"&gt;TZ=Asia/Kolkata&lt;/span&gt;
      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s"&gt;NODE_ENV=production&lt;/span&gt;
    &lt;span class="na"&gt;volumes&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s"&gt;n8n_data:/home/node/.n8n&lt;/span&gt;

  &lt;span class="na"&gt;caddy&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;image&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;caddy:2&lt;/span&gt;
    &lt;span class="na"&gt;restart&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;unless-stopped&lt;/span&gt;
    &lt;span class="na"&gt;ports&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="s"&gt;80:80"&lt;/span&gt;
      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="s"&gt;443:443"&lt;/span&gt;
    &lt;span class="na"&gt;volumes&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s"&gt;./Caddyfile:/etc/caddy/Caddyfile:ro&lt;/span&gt;
      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s"&gt;caddy_data:/data&lt;/span&gt;
      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s"&gt;caddy_config:/config&lt;/span&gt;

&lt;span class="na"&gt;volumes&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;n8n_data&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;caddy_data&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;caddy_config&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Save with &lt;strong&gt;Ctrl+O&lt;/strong&gt;, Enter, then &lt;strong&gt;Ctrl+X&lt;/strong&gt;. Now create the Caddy settings, which are just three lines:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;nano Caddyfile
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight nginx"&gt;&lt;code&gt;&lt;span class="k"&gt;n8n.example.com&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="kn"&gt;reverse_proxy&lt;/span&gt; &lt;span class="nf"&gt;n8n&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="mi"&gt;5678&lt;/span&gt;
&lt;span class="err"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;What the important settings do:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;WEBHOOK_URL&lt;/code&gt;: the address other apps use to call your workflows. Without it, n8n shows webhook links with &lt;code&gt;localhost:5678&lt;/code&gt;, which nothing outside can reach.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;N8N_PROXY_HOPS=1&lt;/code&gt;: tells n8n it sits behind one proxy (Caddy), so it sees the visitor's real IP.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;n8n_data&lt;/code&gt;: a Docker volume that keeps your workflows, credentials and encryption key safe when the container is updated or recreated.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  5. Start n8n
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker compose up &lt;span class="nt"&gt;-d&lt;/span&gt;
docker compose logs &lt;span class="nt"&gt;-f&lt;/span&gt; caddy
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Within a minute you should see a line saying the certificate was &lt;em&gt;obtained successfully&lt;/em&gt;. Press &lt;strong&gt;Ctrl+C&lt;/strong&gt; to leave the log. Both containers should show as running:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker compose ps
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Because of &lt;code&gt;restart: unless-stopped&lt;/code&gt;, n8n starts again on its own after a reboot.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Create your owner account
&lt;/h2&gt;

&lt;p&gt;Open &lt;code&gt;https://n8n.example.com&lt;/code&gt; in your browser. You'll see the padlock and n8n's setup screen. Create the &lt;strong&gt;owner account&lt;/strong&gt; straight away, because until you do, anyone who finds the address could claim it. Use a strong password, and turn on two-factor authentication under &lt;strong&gt;Settings → Personal&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Test it with a simple workflow: add a &lt;strong&gt;Schedule Trigger&lt;/strong&gt; and a &lt;strong&gt;Gmail&lt;/strong&gt; or &lt;strong&gt;Telegram&lt;/strong&gt; node, run it once, and you're automating.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Update n8n
&lt;/h2&gt;

&lt;p&gt;n8n releases new versions often. Take a &lt;strong&gt;snapshot&lt;/strong&gt; of your VPS first, then:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;cd&lt;/span&gt; ~/n8n
docker compose pull
docker compose up &lt;span class="nt"&gt;-d&lt;/span&gt;
docker image prune &lt;span class="nt"&gt;-f&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Your workflows stay in the &lt;code&gt;n8n_data&lt;/code&gt; volume, so nothing is lost. Before a big version jump, read n8n's release notes for breaking changes. If anything misbehaves, you can roll back to the snapshot in minutes.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. Back up your workflows
&lt;/h2&gt;

&lt;p&gt;Turn on automatic backups for the server. For an extra copy of n8n's data you can download anywhere, run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker run &lt;span class="nt"&gt;--rm&lt;/span&gt; &lt;span class="nt"&gt;-v&lt;/span&gt; n8n_n8n_data:/data &lt;span class="nt"&gt;-v&lt;/span&gt; ~/backups:/backup alpine &lt;span class="nb"&gt;tar &lt;/span&gt;czf /backup/n8n-&lt;span class="si"&gt;$(&lt;/span&gt;&lt;span class="nb"&gt;date&lt;/span&gt; +%F&lt;span class="si"&gt;)&lt;/span&gt;.tar.gz &lt;span class="nt"&gt;-C&lt;/span&gt; /data &lt;span class="nb"&gt;.&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The volume name is the folder name plus &lt;code&gt;_n8n_data&lt;/code&gt;; check yours with &lt;code&gt;docker volume ls&lt;/code&gt;. This archive includes n8n's &lt;strong&gt;encryption key&lt;/strong&gt;, and without it saved credentials can't be read on a new server, so keep the file somewhere safe and private.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common problems
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Problem&lt;/th&gt;
&lt;th&gt;Usual fix&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;No certificate, browser shows an error&lt;/td&gt;
&lt;td&gt;The subdomain doesn't point to the server yet, or port 80 is closed. Check &lt;code&gt;dig&lt;/code&gt;, &lt;code&gt;ufw status&lt;/code&gt; and &lt;code&gt;docker compose logs caddy&lt;/code&gt;.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Webhook URLs show &lt;code&gt;localhost:5678&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;WEBHOOK_URL&lt;/code&gt; is missing or misspelled. Fix it and run &lt;code&gt;docker compose up -d&lt;/code&gt;.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Times in workflows are off by 5½ hours&lt;/td&gt;
&lt;td&gt;Set &lt;code&gt;GENERIC_TIMEZONE&lt;/code&gt; and &lt;code&gt;TZ&lt;/code&gt; to &lt;code&gt;Asia/Kolkata&lt;/code&gt;.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;n8n becomes slow or restarts&lt;/td&gt;
&lt;td&gt;The server is out of memory; check with &lt;code&gt;free -h&lt;/code&gt;. Heavy workflows and AI agents need 4–8 GB RAM.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;p&gt;&lt;em&gt;Originally published on the &lt;a href="https://volyte.com/blog/install-n8n-on-vps" rel="noopener noreferrer"&gt;Volyte blog&lt;/a&gt;. Prefer it ready-made? Our &lt;a href="https://volyte.com/n8n-vps" rel="noopener noreferrer"&gt;n8n VPS&lt;/a&gt; comes with n8n, the subdomain and SSL already set up.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>docker</category>
      <category>automation</category>
      <category>selfhosted</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>How to Point Your Domain to Your VPS (DNS A Record + Free SSL)</title>
      <dc:creator>Volyte</dc:creator>
      <pubDate>Fri, 30 Oct 2026 08:19:46 +0000</pubDate>
      <link>https://dev.to/volyte/how-to-point-your-domain-to-your-vps-dns-a-record-free-ssl-kd</link>
      <guid>https://dev.to/volyte/how-to-point-your-domain-to-your-vps-dns-a-record-free-ssl-kd</guid>
      <description>&lt;p&gt;You have a VPS and a domain name. To make &lt;code&gt;example.com&lt;/code&gt; open your website, you add one small DNS record that says &lt;em&gt;"this domain lives at this server's IP address"&lt;/em&gt;. It takes about 5 minutes to set up, and usually works within an hour.&lt;/p&gt;

&lt;p&gt;This guide works wherever your domain is registered — GoDaddy, Hostinger, Namecheap or anyone else — and for Linux and Windows VPS.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you need
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Your VPS IP address&lt;/strong&gt; — in your provider's welcome email or client area. We'll use the example &lt;code&gt;203.0.113.25&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A login to wherever your domain's DNS is managed&lt;/strong&gt; — usually your domain registrar. If you use Cloudflare, make the changes in Cloudflare instead.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Your website ready on the VPS&lt;/strong&gt; — or set it up after Step 3 while DNS updates.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Step 1: Find where your DNS is managed
&lt;/h2&gt;

&lt;p&gt;Your DNS is managed wherever your domain's &lt;strong&gt;nameservers&lt;/strong&gt; point. Open your registrar's domain page and look at "Nameservers":&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;If they are the registrar's own (for example &lt;code&gt;ns1.registrar.com&lt;/code&gt;), edit DNS at the registrar.&lt;/li&gt;
&lt;li&gt;If they say something like &lt;code&gt;xxx.ns.cloudflare.com&lt;/code&gt;, edit DNS in your Cloudflare account.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Step 2: Add the A records
&lt;/h2&gt;

&lt;p&gt;An &lt;strong&gt;A record&lt;/strong&gt; connects a name to an IPv4 address. Add (or edit) these two records:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Type&lt;/th&gt;
&lt;th&gt;Name / Host&lt;/th&gt;
&lt;th&gt;Value / Points to&lt;/th&gt;
&lt;th&gt;TTL&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;A&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;@&lt;/code&gt; (the domain itself)&lt;/td&gt;
&lt;td&gt;&lt;code&gt;203.0.113.25&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Auto or 1 hour&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;A&lt;/td&gt;
&lt;td&gt;&lt;code&gt;www&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;203.0.113.25&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Auto or 1 hour&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;ul&gt;
&lt;li&gt;Some panels want the full name instead of &lt;code&gt;@&lt;/code&gt; — type &lt;code&gt;example.com&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Instead of the second A record, you can use a &lt;strong&gt;CNAME&lt;/strong&gt;: name &lt;code&gt;www&lt;/code&gt;, value &lt;code&gt;example.com&lt;/code&gt;. Either works.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Delete any old A records&lt;/strong&gt; for &lt;code&gt;@&lt;/code&gt; and &lt;code&gt;www&lt;/code&gt; that point somewhere else (such as a "parked" page). Two different A records for the same name make visitors land on either server at random.&lt;/li&gt;
&lt;li&gt;If there is an &lt;strong&gt;AAAA&lt;/strong&gt; record (IPv6) pointing to your old host, delete it too — or change it to your VPS's IPv6 address if it has one.&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Don't touch your MX records.&lt;/strong&gt; They decide where your email goes. Changing A records moves your website only — your email keeps working where it is.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Step 3: Check that DNS has updated
&lt;/h2&gt;

&lt;p&gt;Changes usually show within &lt;strong&gt;5–60 minutes&lt;/strong&gt;. Sometimes it takes a few hours, because internet providers remember (cache) the old address until the old TTL runs out.&lt;/p&gt;

&lt;p&gt;On Windows, open Command Prompt and type:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;nslookup example.com 8.8.8.8
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On Mac or Linux:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;dig +short example.com @8.8.8.8
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;When it shows your VPS IP (&lt;code&gt;203.0.113.25&lt;/code&gt;), DNS is ready. You can also check from many countries at once with a free online "DNS checker".&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Tell your web server about the domain
&lt;/h2&gt;

&lt;p&gt;DNS sends visitors to your server — now the server must know which website to show for that domain.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;cPanel / Plesk:&lt;/strong&gt; add the domain in the panel (cPanel: &lt;em&gt;Domains → Create a New Domain&lt;/em&gt;; Plesk: &lt;em&gt;Websites &amp;amp; Domains → Add Domain&lt;/em&gt;). Done — skip to Step 5.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Nginx:&lt;/strong&gt; put both names in your site's &lt;code&gt;server_name&lt;/code&gt; line, then reload:
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight nginx"&gt;&lt;code&gt;&lt;span class="k"&gt;server_name&lt;/span&gt; &lt;span class="s"&gt;example.com&lt;/span&gt; &lt;span class="s"&gt;www.example.com&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;nginx &lt;span class="nt"&gt;-t&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="nb"&gt;sudo &lt;/span&gt;systemctl reload nginx
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Apache:&lt;/strong&gt; set &lt;code&gt;ServerName example.com&lt;/code&gt; and &lt;code&gt;ServerAlias www.example.com&lt;/code&gt; in your virtual host, then &lt;code&gt;sudo systemctl reload apache2&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Windows VPS (IIS):&lt;/strong&gt; in IIS Manager, open your site → &lt;em&gt;Bindings&lt;/em&gt; → add &lt;code&gt;example.com&lt;/code&gt; and &lt;code&gt;www.example.com&lt;/code&gt; on port 80.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Make sure ports &lt;strong&gt;80 and 443&lt;/strong&gt; are open in your server's firewall.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Add a free SSL certificate (HTTPS)
&lt;/h2&gt;

&lt;p&gt;Once the domain opens your site, add HTTPS so browsers show the padlock. It's free with Let's Encrypt.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;cPanel / Plesk:&lt;/strong&gt; AutoSSL (cPanel) or the Let's Encrypt extension (Plesk) does it automatically, usually within minutes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Nginx on Ubuntu / Debian:&lt;/strong&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;apt &lt;span class="nb"&gt;install &lt;/span&gt;certbot python3-certbot-nginx
&lt;span class="nb"&gt;sudo &lt;/span&gt;certbot &lt;span class="nt"&gt;--nginx&lt;/span&gt; &lt;span class="nt"&gt;-d&lt;/span&gt; example.com &lt;span class="nt"&gt;-d&lt;/span&gt; www.example.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Certbot sets up HTTPS and renews the certificate automatically.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Windows (IIS):&lt;/strong&gt; use the free &lt;em&gt;win-acme&lt;/em&gt; tool, which adds and renews Let's Encrypt certificates for IIS.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;SSL only works &lt;strong&gt;after&lt;/strong&gt; DNS points to your VPS — if Certbot says the domain can't be verified, wait a little and try again.&lt;/p&gt;

&lt;h2&gt;
  
  
  If it doesn't work
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What you see&lt;/th&gt;
&lt;th&gt;What to do&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;The old website still shows&lt;/td&gt;
&lt;td&gt;DNS hasn't updated for you yet. Check with &lt;code&gt;nslookup example.com 8.8.8.8&lt;/code&gt;. If that shows the new IP, clear your browser cache or try mobile data.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Sometimes old site, sometimes new&lt;/td&gt;
&lt;td&gt;There are two A (or AAAA) records for the same name. Delete the one that points to the old server.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;"This site can't be reached"&lt;/td&gt;
&lt;td&gt;DNS is fine but the server isn't answering: check the web server is running and ports 80/443 are open in the firewall.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;The server's default page appears&lt;/td&gt;
&lt;td&gt;Your web server doesn't know the domain yet — repeat Step 4.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Email stopped working&lt;/td&gt;
&lt;td&gt;An MX record was changed or deleted. Put back the MX records your email provider gave you.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;p&gt;&lt;em&gt;Originally published on the &lt;a href="https://volyte.com/blog/point-domain-to-vps" rel="noopener noreferrer"&gt;Volyte blog&lt;/a&gt;. Next step: &lt;a href="https://volyte.com/blog/secure-linux-vps" rel="noopener noreferrer"&gt;secure your Linux VPS in 10 minutes&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>dns</category>
      <category>webdev</category>
      <category>linux</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Secure Your Linux VPS in 10 Minutes: 8 First Steps (Ubuntu, Debian, AlmaLinux)</title>
      <dc:creator>Volyte</dc:creator>
      <pubDate>Sun, 25 Oct 2026 10:27:47 +0000</pubDate>
      <link>https://dev.to/volyte/secure-your-linux-vps-in-10-minutes-8-first-steps-ubuntu-debian-almalinux-38jj</link>
      <guid>https://dev.to/volyte/secure-your-linux-vps-in-10-minutes-8-first-steps-ubuntu-debian-almalinux-38jj</guid>
      <description>&lt;p&gt;A new server with a public IP gets its first login attempts from bots within minutes. The good news: a handful of steps stop almost all of them. Do these &lt;strong&gt;right after your VPS is ready&lt;/strong&gt; — it takes about 10 minutes.&lt;/p&gt;

&lt;p&gt;Commands are for &lt;strong&gt;Ubuntu and Debian&lt;/strong&gt;, with the &lt;strong&gt;AlmaLinux / Rocky Linux&lt;/strong&gt; version where it differs. Log in as &lt;code&gt;root&lt;/code&gt; with the details from your welcome email.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Golden rule:&lt;/strong&gt; when you change SSH settings, keep your current session open and test the new login in a &lt;em&gt;second&lt;/em&gt; window. If something is wrong, you can still fix it from the first one.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  1. Update everything
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;apt update &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; apt upgrade &lt;span class="nt"&gt;-y&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;AlmaLinux / Rocky: &lt;code&gt;dnf upgrade -y&lt;/code&gt;. Reboot if the kernel was updated: &lt;code&gt;reboot&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Create your own user with sudo
&lt;/h2&gt;

&lt;p&gt;Working as &lt;code&gt;root&lt;/code&gt; all the time is risky — one wrong command can damage the system. Create a normal user (replace &lt;code&gt;deploy&lt;/code&gt; with your name):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;adduser deploy
usermod &lt;span class="nt"&gt;-aG&lt;/span&gt; &lt;span class="nb"&gt;sudo &lt;/span&gt;deploy
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Debian says &lt;em&gt;sudo: command not found&lt;/em&gt;? Install it first: &lt;code&gt;apt install sudo -y&lt;/code&gt;. AlmaLinux / Rocky: &lt;code&gt;adduser deploy &amp;amp;&amp;amp; passwd deploy &amp;amp;&amp;amp; usermod -aG wheel deploy&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Log in with an SSH key instead of a password
&lt;/h2&gt;

&lt;p&gt;A key is far harder to guess than any password. On &lt;strong&gt;your own computer&lt;/strong&gt; (Windows PowerShell, Mac or Linux terminal), create a key once:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;ssh-keygen &lt;span class="nt"&gt;-t&lt;/span&gt; ed25519
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Press Enter to accept the defaults (adding a passphrase is a good idea). Then copy it to the server — on Mac / Linux:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;ssh-copy-id deploy@203.0.113.25
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On Windows PowerShell:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="kr"&gt;type&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nv"&gt;$&lt;/span&gt;&lt;span class="nn"&gt;env&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nv"&gt;USERPROFILE&lt;/span&gt;&lt;span class="n"&gt;\.ssh\id_ed25519.pub&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;|&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;ssh&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;deploy&lt;/span&gt;&lt;span class="err"&gt;@&lt;/span&gt;&lt;span class="nx"&gt;203.0.113.25&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"mkdir -p ~/.ssh &amp;amp;&amp;amp; chmod 700 ~/.ssh &amp;amp;&amp;amp; cat &amp;gt;&amp;gt; ~/.ssh/authorized_keys &amp;amp;&amp;amp; chmod 600 ~/.ssh/authorized_keys"&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Now open a &lt;strong&gt;new&lt;/strong&gt; window and check you can log in without a password: &lt;code&gt;ssh deploy@203.0.113.25&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Turn off root login and password login
&lt;/h2&gt;

&lt;p&gt;Only after the key login works, edit the SSH settings:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;nano /etc/ssh/sshd_config
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Set these two lines (remove the &lt;code&gt;#&lt;/code&gt; at the start if there is one):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight ssh"&gt;&lt;code&gt;&lt;span class="k"&gt;PermitRootLogin&lt;/span&gt; &lt;span class="no"&gt;no&lt;/span&gt;
&lt;span class="k"&gt;PasswordAuthentication&lt;/span&gt; &lt;span class="no"&gt;no&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On Ubuntu, also check the files in &lt;code&gt;/etc/ssh/sshd_config.d/&lt;/code&gt; — a file such as &lt;code&gt;50-cloud-init.conf&lt;/code&gt; can switch &lt;code&gt;PasswordAuthentication yes&lt;/code&gt; back on. Change it to &lt;code&gt;no&lt;/code&gt; there too. Then test and restart SSH:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;sshd &lt;span class="nt"&gt;-t&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="nb"&gt;sudo &lt;/span&gt;systemctl restart ssh
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;AlmaLinux / Rocky: the service is called &lt;code&gt;sshd&lt;/code&gt; — &lt;code&gt;sudo systemctl restart sshd&lt;/code&gt;. Test the login again in a new window before closing the old one.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Optional:&lt;/em&gt; moving SSH from port 22 to another port (for example 2222) doesn't make it unbreakable, but it cuts automated login attempts dramatically. If you do, open the new port in the firewall (Step 5) &lt;strong&gt;before&lt;/strong&gt; restarting SSH. On Ubuntu 24.04, also run &lt;code&gt;sudo systemctl daemon-reload &amp;amp;&amp;amp; sudo systemctl restart ssh.socket&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Switch on the firewall
&lt;/h2&gt;

&lt;p&gt;Allow only what you use — SSH, and web traffic if you host websites:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;ufw allow OpenSSH
&lt;span class="nb"&gt;sudo &lt;/span&gt;ufw allow 80,443/tcp
&lt;span class="nb"&gt;sudo &lt;/span&gt;ufw &lt;span class="nb"&gt;enable
sudo &lt;/span&gt;ufw status
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Changed the SSH port? Use &lt;code&gt;sudo ufw allow 2222/tcp&lt;/code&gt; instead of &lt;code&gt;OpenSSH&lt;/code&gt;. AlmaLinux / Rocky use firewalld, which is on by default and already allows SSH:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;firewall-cmd &lt;span class="nt"&gt;--permanent&lt;/span&gt; &lt;span class="nt"&gt;--add-service&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;http &lt;span class="nt"&gt;--add-service&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;https
&lt;span class="nb"&gt;sudo &lt;/span&gt;firewall-cmd &lt;span class="nt"&gt;--reload&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  6. Block repeated login attempts with Fail2ban
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;apt &lt;span class="nb"&gt;install &lt;/span&gt;fail2ban &lt;span class="nt"&gt;-y&lt;/span&gt;
&lt;span class="nb"&gt;sudo &lt;/span&gt;systemctl &lt;span class="nb"&gt;enable&lt;/span&gt; &lt;span class="nt"&gt;--now&lt;/span&gt; fail2ban
&lt;span class="nb"&gt;sudo &lt;/span&gt;fail2ban-client status sshd
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Fail2ban bans an IP for a while after several failed logins. On Ubuntu the SSH protection is on out of the box. On Debian 12, if Fail2ban doesn't start, create &lt;code&gt;/etc/fail2ban/jail.local&lt;/code&gt; with these lines and restart it — Debian 12 keeps logs in the system journal instead of &lt;code&gt;auth.log&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight ini"&gt;&lt;code&gt;&lt;span class="nn"&gt;[sshd]&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="py"&gt;backend&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s"&gt;systemd&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;AlmaLinux / Rocky: install it from EPEL (&lt;code&gt;sudo dnf install epel-release -y &amp;amp;&amp;amp; sudo dnf install fail2ban -y&lt;/code&gt;) and turn on the &lt;code&gt;sshd&lt;/code&gt; jail in &lt;code&gt;/etc/fail2ban/jail.local&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Install security updates automatically
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;apt &lt;span class="nb"&gt;install &lt;/span&gt;unattended-upgrades &lt;span class="nt"&gt;-y&lt;/span&gt;
&lt;span class="nb"&gt;sudo &lt;/span&gt;dpkg-reconfigure &lt;span class="nt"&gt;-plow&lt;/span&gt; unattended-upgrades
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Choose &lt;strong&gt;Yes&lt;/strong&gt;. Security fixes now install by themselves every day. AlmaLinux / Rocky:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;dnf &lt;span class="nb"&gt;install &lt;/span&gt;dnf-automatic &lt;span class="nt"&gt;-y&lt;/span&gt;
&lt;span class="nb"&gt;sudo &lt;/span&gt;systemctl &lt;span class="nb"&gt;enable&lt;/span&gt; &lt;span class="nt"&gt;--now&lt;/span&gt; dnf-automatic.timer
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;(Set &lt;code&gt;apply_updates = yes&lt;/code&gt; in &lt;code&gt;/etc/dnf/automatic.conf&lt;/code&gt; so updates are installed, not just downloaded.)&lt;/p&gt;

&lt;h2&gt;
  
  
  8. Take a snapshot and set up backups
&lt;/h2&gt;

&lt;p&gt;Security also means being able to recover. Now that the server is clean and configured, take a &lt;strong&gt;snapshot&lt;/strong&gt; from your hosting control panel — if anything goes wrong later, you can roll back in minutes. Turn on automatic backups too, so you always have a recent copy kept off the server.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick check: what is listening?
&lt;/h2&gt;

&lt;p&gt;See which services accept connections from the internet:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;ss &lt;span class="nt"&gt;-tulpn&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Anything you don't recognise or don't need (an old database open to the world, a test app) — stop it, or allow it only from your own IP.&lt;/p&gt;

&lt;h2&gt;
  
  
  Your checklist
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Step&lt;/th&gt;
&lt;th&gt;Done when…&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Updates&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;apt upgrade&lt;/code&gt; shows nothing left to install&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Own sudo user&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;sudo whoami&lt;/code&gt; prints &lt;code&gt;root&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SSH key&lt;/td&gt;
&lt;td&gt;You log in without typing the server password&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;No root / password login&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;ssh root@your-ip&lt;/code&gt; is refused&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Firewall&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;ufw status&lt;/code&gt; shows &lt;em&gt;active&lt;/em&gt; with only the ports you need&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Fail2ban&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;fail2ban-client status sshd&lt;/code&gt; shows the jail running&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Auto updates&lt;/td&gt;
&lt;td&gt;unattended-upgrades (or dnf-automatic) is enabled&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Snapshot + backups&lt;/td&gt;
&lt;td&gt;A snapshot exists and backups are on&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;p&gt;&lt;em&gt;Originally published on the &lt;a href="https://volyte.com/blog/secure-linux-vps" rel="noopener noreferrer"&gt;Volyte blog&lt;/a&gt;. Next step: &lt;a href="https://volyte.com/blog/point-domain-to-vps" rel="noopener noreferrer"&gt;point your domain to your VPS&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>linux</category>
      <category>security</category>
      <category>devops</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
