<?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: Priyanshu Khantwal</title>
    <description>The latest articles on DEV Community by Priyanshu Khantwal (@priyanshu69).</description>
    <link>https://dev.to/priyanshu69</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2601600%2Ff4cf3130-91af-45d7-af89-e6bf87dfb6b4.jpg</url>
      <title>DEV Community: Priyanshu Khantwal</title>
      <link>https://dev.to/priyanshu69</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/priyanshu69"/>
    <language>en</language>
    <item>
      <title>Deploying My Headless Ubuntu Server</title>
      <dc:creator>Priyanshu Khantwal</dc:creator>
      <pubDate>Mon, 09 Mar 2026 02:20:15 +0000</pubDate>
      <link>https://dev.to/priyanshu69/deploying-my-headless-ubuntu-server-b0i</link>
      <guid>https://dev.to/priyanshu69/deploying-my-headless-ubuntu-server-b0i</guid>
      <description>&lt;p&gt;Building a home lab is practically a rite of passage in cybersecurity, but you don't need massive enterprise hardware to get started. Today, I focused on building a solid, resource-efficient foundation by deploying a &lt;strong&gt;headless Ubuntu Server&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;My primary host is a Linux Mint machine running on an &lt;strong&gt;Intel i3 11th Gen processor&lt;/strong&gt; with &lt;strong&gt;8GB of RAM&lt;/strong&gt;. To keep the hardware footprint as low as possible while still simulating a realistic remote server environment, I bypassed the Graphical User Interface (GUI) entirely.&lt;/p&gt;




&lt;h3&gt;
  
  
  The VirtualBox Configuration
&lt;/h3&gt;

&lt;p&gt;I used &lt;strong&gt;VirtualBox 7.2.6&lt;/strong&gt; to spin up &lt;strong&gt;Ubuntu Server 24.04 LTS&lt;/strong&gt;. Because a headless server does not need to render graphical elements, I was able to allocate absolute minimal resources:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;RAM:&lt;/strong&gt; 2048 MB&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CPU:&lt;/strong&gt; 1 Core&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Storage:&lt;/strong&gt; 15 GB (Dynamically Allocated)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F2wwg5jwm12b680pbvtaw.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F2wwg5jwm12b680pbvtaw.png" alt="setting up the ubuntu server in virtualbox" width="800" height="583"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Networking and Remote Access
&lt;/h3&gt;

&lt;p&gt;The core challenge of a headless setup is accessing it securely. During the Ubuntu installation, I ensured the &lt;strong&gt;OpenSSH Server&lt;/strong&gt; package was included. To connect from my host terminal to the isolated VirtualBox environment, I used a &lt;strong&gt;NAT network strategy&lt;/strong&gt; with specific &lt;strong&gt;Port Forwarding&lt;/strong&gt; rules.&lt;/p&gt;

&lt;h4&gt;
  
  
  Port Forwarding Rules
&lt;/h4&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Protocol&lt;/th&gt;
&lt;th&gt;Host IP&lt;/th&gt;
&lt;th&gt;Host Port&lt;/th&gt;
&lt;th&gt;Guest Port&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;TCP&lt;/td&gt;
&lt;td&gt;127.0.0.1&lt;/td&gt;
&lt;td&gt;2222&lt;/td&gt;
&lt;td&gt;22&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ftq6t53z19xxnr33plm4u.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ftq6t53z19xxnr33plm4u.png" alt="portforwading settings for the server" width="800" height="616"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;With the VM running quietly in the background, I can now drop into the server directly from my Mint terminal using:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;ssh tommy@127.0.0.1 -p 2222&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fxf3g03sbb2w7py8c58gz.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fxf3g03sbb2w7py8c58gz.png" alt="accessing my headless server from the host os" width="773" height="407"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;h3&gt;
  
  
  The Takeaway
&lt;/h3&gt;

&lt;p&gt;Running headless forces you to interact with the OS exactly how you would in a real-world, remote enterprise environment—&lt;strong&gt;strictly through the command line interface (CLI)&lt;/strong&gt;. It is a highly efficient way to practice systems administration without melting your CPU. Small steps lead to solid foundations.&lt;/p&gt;




</description>
      <category>cybersecurity</category>
      <category>linux</category>
      <category>ubuntu</category>
      <category>homelab</category>
    </item>
  </channel>
</rss>
