{"id":2829,"date":"2025-03-08T16:07:57","date_gmt":"2025-03-08T16:07:57","guid":{"rendered":"https:\/\/cybersecurityinfocus.com\/?p=2829"},"modified":"2025-03-08T16:07:57","modified_gmt":"2025-03-08T16:07:57","slug":"the-ultimate-guide-to-transforming-your-old-machine-into-a-vps-server-3","status":"publish","type":"post","link":"https:\/\/cybersecurityinfocus.com\/?p=2829","title":{"rendered":"The Ultimate Guide to Transforming Your Old Machine into a VPS Server"},"content":{"rendered":"

Hey guys, Rocky here!<\/strong> <\/p>\n

So you\u2019ve got a dusty old laptop or computer taking up space in the corner? Perhaps it\u2019s that hulking desktop from 2012 or that gaming machine you upgraded for something new and flashy. Before you throw it on eBay for $5 or repurpose it as an elegant doorstop, let me strike you with a crazy notion: what if you could use that old system as your very own VPS server?<\/strong><\/p>\n

Yes, I told you you could. Instead of paying $5\u2013$50 per month to rent a virtual server from some monolithic corporation, you can repurpose that old hardware into your own self-hosted monster. Host sites, run game servers, manage your smart home, or build a personal Netflix-style media center\u2014all for free (well, aside from the electricity bill).<\/p>\n

Why Bother Doing This?<\/strong><\/h3>\n

Let\u2019s be real:<\/p>\n

Save $$$<\/strong>: No monthly fees. Mic drop.<\/em><\/p>\n

Eco-friendly<\/strong>: Reuse instead of e-waste. Mother Earth approves. <\/p>\n

Full Control<\/strong>: No limits on what you install, tweak, or break (oops).<\/p>\n

Learn Cool Stuff<\/strong>: You\u2019ll level up your tech skills like a boss.<\/p>\n

Wait\u2026 What\u2019s a VPS Again?<\/strong><\/h3>\n

A Virtual Private Server<\/em> (VPS) is basically a slice of a powerful computer that you rent online. It acts like your own mini-server in the cloud. But here\u2019s the twist: your old machine can do the same thing<\/strong>. With the right setup, it\u2019ll mimic those pricey cloud servers\u2014just sitting in your closet, humming away.<\/p>\n

What You\u2019ll Get in This Guide<\/strong><\/h3>\n

No fluff, no confusing jargon. I\u2019ll walk you through:<\/p>\n

Turning your grandma\u2019s PC into a server (no soldering required).<\/p>\n

Choosing the right software (spoiler: Linux is your friend).<\/p>\n

Securing it so hackers don\u2019t throw a party in your living room.<\/p>\n

Cool projects to run on it (game servers, blogs, VPNs\u2014you name it).<\/p>\n

If you\u2019re ready to geek out, grab a snack, and let\u2019s turn that \u201coutdated\u201d machine into something epic. Trust me, by the end of this, you\u2019ll be the MacGyver of DIY servers. <\/p>\n

Let\u2019s dive in!<\/em> <\/p>\n

2. Prerequisites for Conversion<\/h2>\n

Before we start slapping software onto your old machine like it\u2019s a digital art project, let\u2019s make sure you\u2019ve got everything you need. Don\u2019t worry\u2014this isn\u2019t a shopping spree. You probably already own 90% of this stuff. Let\u2019s break it down:<\/p>\n

2.1 Hardware Checklist: What\u2019s Under the Hood?<\/strong><\/h3>\n

Your old machine isn\u2019t useless<\/em>\u2014it just needs a little love. Here\u2019s the bare minimum to make it VPS-worthy:<\/p>\n

CPU<\/strong>: A dual-core processor (Intel i3 or AMD equivalent from ~2010 or newer).<\/p>\n

RAM<\/strong>: 4GB minimum (8GB+ if you want to run multiple apps smoothly).<\/p>\n

Storage<\/strong>: A 64GB hard drive or SSD (SSDs are way faster, but HDDs work in a pinch).<\/p>\n

Internet<\/strong>: A stable connection (5Mbps upload speed or better if you want remote access).<\/p>\n

Power Supply<\/strong>: No frayed wires, please. We\u2019re building a server, not a fire hazard. <\/p>\n

Pro Tip:<\/em><\/strong> Check if your CPU supports virtualization<\/strong> (Intel VT-x or AMD-V).<\/em><\/p>\n

On Linux, run: egrep -c ‘(vmx|svm)’ \/proc\/cpuinfo (a number >0<\/strong> means you\u2019re golden).<\/p>\n

On Windows, use CPU-Z<\/strong> (look for \u201cVirtualization\u201d enabled).<\/p>\n

2.2 Software & Tools: The Digital Toolbox<\/strong><\/h3>\n

You\u2019ll need three things here:<\/p>\n

A Base Operating System<\/strong>:<\/p>\n

Linux<\/strong> is king here. I recommend Ubuntu Server<\/strong> (user-friendly) or Debian<\/strong> (lightweight).<\/p>\n

Not a Linux guru?<\/em> No sweat\u2014I\u2019ll walk you through it.<\/p>\n

Virtualization Software<\/strong>:<\/p>\n

Proxmox VE<\/strong> (my top pick): Free, powerful, and perfect for managing VMs.<\/p>\n

Docker<\/strong>: Super lightweight if you just want containers (apps in isolated bubbles).<\/p>\n

KVM<\/strong>: For Linux purists who like doing everything via command line.<\/p>\n

A Bootable USB Drive<\/strong>:<\/p>\n

Grab Balena Etcher<\/strong> (free) to flash your OS or Proxmox ISO onto a USB stick.<\/p>\n

2.3 Network Setup: Don\u2019t Skip This Part<\/strong><\/h3>\n

Your DIY VPS needs to talk to the outside world. Here\u2019s the lowdown:<\/p>\n

Static IP Address<\/strong>:<\/p>\n

Assign your machine a fixed IP on your home network (so it doesn\u2019t vanish after a router reboot).<\/p>\n

How?<\/em> Log into your router\u2019s admin panel (usually 192.168.1.1) and reserve an IP for your server\u2019s MAC address.<\/p>\n

Port Forwarding<\/strong>:<\/p>\n

Want to host a website or game server? Forward ports like 80 (HTTP)<\/strong> or 25565 (Minecraft)<\/strong> to your server\u2019s IP.<\/p>\n

Router settings are confusing?<\/em> Google \u201c[Your Router Model] + port forwarding guide.\u201d<\/p>\n

Firewall Basics<\/strong>:<\/p>\n

Linux users: UFW<\/strong> (Uncomplicated Firewall) is your friend.<\/p>\n

Windows folks: Stick with Linux. (Just kidding\u2026 but seriously, use Linux.)<\/p>\n

2.4 Optional (But Helpful) Upgrades<\/strong><\/h3>\n

Add More RAM<\/strong>: Old DDR3 sticks are dirt cheap on amazon.<\/p>\n

Swap in an SSD<\/strong>: Even a $20 120GB SSD will make your server feel zippy.<\/p>\n

UPS (Uninterruptible Power Supply)<\/strong>: Keep your server alive during blackouts.<\/p>\n

Got All That? Let\u2019s Move!<\/strong><\/h3>\n

If you\u2019re nodding along like, \u201cYeah Rocky, I\u2019ve got an old PC, a USB stick, and a questionable amount of confidence<\/strong>,\u201d you\u2019re ready. Next up: Prepping your machine<\/strong> (aka cleaning out digital cobwebs and installing Linux). <\/p>\n

3. Preparing Your Old Machine<\/strong><\/h2>\n

Alright, time to dust off that old machine and give it a digital spa day. Think of this as prepping a race car\u2014except instead of a fancy engine, we\u2019re using duct tape and optimism. Let\u2019s roll up our sleeves!<\/p>\n

Step 1: Clean Out the Cobwebs (Literally)<\/strong><\/h3>\n

Unplug everything<\/strong> and crack open the case.<\/p>\n

Warning:<\/em> If it looks like a dust bunny apocalypse inside, grab a can of compressed air. Blow out the fans, vents, and motherboard. Your server shouldn\u2019t sound like a jet engine. <\/p>\n

Check the guts<\/strong>:<\/p>\n

Are the RAM sticks seated properly? Push \u2019em in until they click<\/em>.<\/p>\n

Are the cables connected? No loose SATA or power cables allowed.<\/p>\n

Step 2: Test the Hardware (No Lab Coat Needed)<\/strong><\/h3>\n

Before we install anything, let\u2019s make sure your hardware isn\u2019t secretly broken:<\/p>\n

RAM Test<\/strong>:<\/p>\n

Boot a Ubuntu Live USB<\/strong> (you\u2019ll make this later) and open a terminal.<\/p>\n

Run sudo memtester 2G 5 (tests 2GB of RAM for 5 cycles). If it screams \u201cERROR,\u201d replace the RAM. <\/p>\n

Hard Drive Health<\/strong>:<\/p>\n

Run sudo smartctl -a \/dev\/sda (replace sda with your drive name). Look for \u201cPASSED\u201d or \u201cOK.\u201d If it says \u201cDEATH IMMINENT,\u201d swap the drive.<\/p>\n

Pro Tip:<\/em><\/strong> If your hard drive sounds like a coffee grinder, back up your data<\/em> now<\/em><\/strong>.<\/p>\n

Step 3: Upgrade If You Can (But Don\u2019t Stress)<\/strong><\/h3>\n

RAM<\/strong>: If you\u2019ve got 4GB or less, grab a cheap 8GB stick off eBay ($10\u2013$15).<\/p>\n

Storage<\/strong>: Swap that old spinning hard drive for a $25 SSD. It\u2019s like upgrading from a bicycle to a Tesla.<\/p>\n

Power Supply<\/strong>: If yours is louder than a TikTok prank, replace it with a basic 400W PSU ($30).<\/p>\n

No budget?<\/em> Skip this. Your toaster-tier hardware will still work.<\/p>\n

Step 4: Install a Base OS (Linux, Baby!)<\/strong><\/h3>\n

We\u2019re installing Ubuntu Server<\/strong> because it\u2019s free, stable, and won\u2019t judge your hardware.<\/p>\n

Download Ubuntu Server<\/strong>:<\/p>\n

Go to ubuntu.com\/download\/server<\/a> and grab the LTS version.<\/p>\n

Flash the ISO to a USB<\/strong>:<\/p>\n

Use Balena Etcher<\/strong> (it\u2019s idiot-proof). Plug in a USB stick, select the ISO, and click \u201cFlash.\u201d<\/p>\n

Install Ubuntu<\/strong>:<\/p>\n

Boot from the USB (mash F12\/F2\/DEL during startup to pick the USB).<\/p>\n

Follow the prompts. For partitions, just pick \u201cUse Entire Disk\u201d ( This wipes everything!<\/em>).<\/p>\n

Set a username\/password. Write it down\u2014don\u2019t be that person.<\/p>\n

Fun Fact:<\/em><\/strong> If you mess up, just re-flash the USB and try again. Linux won\u2019t cry about it.<\/em><\/p>\n

Step 5: Update & Party<\/strong><\/h3>\n

Once installed, open the terminal and:<\/p>\n

sudo apt update && sudo apt upgrade -y <\/p>\n

This updates your system. Go grab a snack\u2014it\u2019ll take a minute.<\/p>\n

You\u2019re Ready!<\/strong><\/h3>\n

Congrats! Your old machine now has a fresh OS and a purpose in life. Next up: Installing virtualization software<\/strong> (aka turning your PC into a server superhero). <\/p>\n

4. Setting Up Virtualization <\/h2>\n

Time to turn your old machine into a virtualization beast<\/strong>\u2014this is where the magic happens. Think of it like turning one computer into multiple<\/em> computers (but without the extra electricity bills). Let\u2019s get nerdy!<\/p>\n

Step 1: Pick Your Virtualization Tool<\/strong><\/h3>\n

You\u2019ve got options. Here\u2019s the cheat sheet:<\/p>\n

Proxmox VE<\/strong> (Recommended):<\/p>\n

The Swiss Army knife<\/em>: Free, open-source, and manages VMs + containers.<\/p>\n

Has a slick web interface (no command-line PhD required).<\/p>\n

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

Lightweight and fast<\/em>: Perfect for running apps in isolated \u201ccontainers\u201d (like tiny VMs).<\/p>\n

Great for hosting a blog, VPN, or media server.<\/p>\n

KVM<\/strong> (Kernel-based Virtual Machine):<\/p>\n

For Linux nerds<\/em>: Built into the Linux kernel. Powerful, but needs command-line love.<\/p>\n

I\u2019ll walk you through Proxmox<\/em><\/strong>\u2014it\u2019s the easiest for beginners.<\/p>\n

Step 2: Install Proxmox VE<\/strong><\/h3>\n

(Don\u2019t panic. It\u2019s easier than assembling IKEA furniture.)<\/em><\/p>\n

Download the Proxmox ISO<\/strong>:<\/p>\n

Grab it from proxmox.com<\/a>.<\/p>\n

Flash it to a USB<\/strong>:<\/p>\n

Use Balena Etcher<\/strong> again (you\u2019re a pro at this now).<\/p>\n

Boot from the USB<\/strong>:<\/p>\n

Mash F12, ESC, or DEL during startup to pick the USB drive.<\/p>\n

Follow the Installer<\/strong>:<\/p>\n

Pick your hard drive ( This wipes everything!<\/em>).<\/p>\n

Set a password for the Proxmox web interface. Write it down.<\/strong><\/p>\n

For networking, leave the defaults unless you\u2019re a networking wizard.<\/p>\n

Done?<\/em><\/strong> Reboot, yank the USB, and let Proxmox load.<\/p>\n

Step 3: Access the Proxmox Web Interface<\/strong><\/h3>\n

Find your server\u2019s IP<\/strong>:<\/p>\n

On the Proxmox console, type ip a and look for the inet address under your network interface (usually starts with 192.168.x.x).<\/p>\n

Open a browser on your main computer<\/strong>:<\/p>\n

Go to https:\/\/YOUR_SERVER_IP:8006 (ignore the SSL warning\u2014we\u2019ll fix that later).<\/p>\n

Log in<\/strong>:<\/p>\n

Username: root<\/p>\n

Password: The one you set during installation.<\/em><\/p>\n

Boom!<\/em><\/strong> You\u2019re now staring at the Proxmox dashboard. Feels like you\u2019re in The Matrix<\/em>, right?<\/p>\n

Step 4: Configure Storage & Networks<\/strong><\/h3>\n

(Don\u2019t skip this\u2014your VMs need a home.)<\/em><\/p>\n

Add Storage<\/strong>:<\/p>\n

Go to \u201cDatacenter\u201d > \u201cStorage\u201d > \u201cAdd\u201d > \u201cDirectory\u201d.<\/p>\n

Name it \u201clocal-vms\u201d and pick your hard drive.<\/p>\n

Set Up Networking<\/strong>:<\/p>\n

Stick with the default \u201cvmbr0\u201d bridge (it lets VMs share your server\u2019s internet).<\/p>\n

Pro Tip:<\/em><\/strong> If you added an SSD earlier, assign it to Proxmox for faster VMs.<\/em><\/p>\n

Step 5: Create Your First Virtual Machine<\/strong><\/h3>\n

Let\u2019s spin up a test VM (like a Ubuntu server):<\/p>\n

Download an ISO<\/strong>:<\/p>\n

In Proxmox, go to \u201clocal\u201d storage > \u201cISO Images\u201d > \u201cDownload from URL\u201d.<\/p>\n

Paste a Ubuntu Server ISO link: https:\/\/releases.ubuntu.com<\/a>.<\/p>\n

Click \u201cCreate VM\u201d<\/strong>:<\/p>\n

Name: Test-Ubuntu<\/p>\n

OS: Pick the Ubuntu ISO you downloaded.<\/p>\n

Hard Disk: 20GB (adjust based on your storage).<\/p>\n

CPU: 2 cores.<\/p>\n

RAM: 2048MB (2GB).<\/p>\n

Install the OS<\/strong>:<\/p>\n

Start the VM, follow the Ubuntu install prompts (same as earlier).<\/p>\n

Congrats!<\/em><\/strong> You\u2019ve just created a virtual server<\/em> inside your old machine. Mind = blown. <\/p>\n

Alternative: Docker for Lightweight Apps<\/strong><\/h3>\n

If Proxmox feels overkill, try Docker:<\/p>\n

1. Install Docker on Ubuntu Server<\/strong>:<\/p>\n

sudo apt install docker.io
\nsudo systemctl start docker <\/p>\n

2. Run a Test Container<\/strong>: <\/p>\n

sudo docker run hello-world <\/p>\n

If you see \u201cHello from Docker!\u201d, you\u2019re golden.<\/p>\n

5. <\/strong>Configuring Your VPS Environment<\/strong> <\/h2>\n

Now that your old machine is running Proxmox or Docker, it\u2019s time to turn it into a proper VPS environment<\/em>. Think of this like setting up rooms in your digital house\u2014each VM or container gets its own space to party. Let\u2019s make this thing usable!<\/p>\n

Step 1: Create Your First Real VM (No More \u201cTest\u201d Stuff)<\/strong><\/h3>\n

Let\u2019s say you want to host a website. Here\u2019s how to spin up a production-ready VM<\/strong>:<\/p>\n

In Proxmox<\/strong>:<\/p>\n

Click \u201cCreate VM\u201d again, but this time:<\/p>\n

Name<\/strong>: Web-Server (or something cool like Skynet-Prototype).<\/p>\n

OS<\/strong>: Ubuntu Server 22.04 LTS (or Debian if you\u2019re feeling spicy).<\/p>\n

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

CPU<\/em>: 2-4 cores (don\u2019t be greedy\u2014leave some for other VMs).<\/p>\n

RAM<\/em>: 4GB (adjust later if needed).<\/p>\n

Disk<\/em>: 30GB (SSD storage if you upgraded).<\/p>\n

Start the VM and install the OS (same steps as before).<\/p>\n

Pro Tip:<\/em><\/strong> Enable \u201cStart at boot\u201d so your VM auto-launches if the server reboots.<\/em><\/p>\n

Step 2: Set Up Networking (So You Can Actually Use<\/em> This Thing)<\/strong><\/h3>\n

Your VMs need internet and a way to talk to the outside world.<\/p>\n

Option 1: Bridged Networking<\/strong><\/h4>\n

What it does<\/strong>: Gives your VM its own IP on your home network (like a separate device).<\/p>\n

How to set it in Proxmox<\/strong>:<\/p>\n

When creating the VM, set \u201cNetwork\u201d to vmbr0 (the default bridge).<\/p>\n

Done. Your VM will grab an IP from your router via DHCP.<\/p>\n

Option 2: Port Forwarding<\/strong><\/h4>\n

Use case<\/strong>: Host a website or game server accessible from the internet.<\/p>\n

Example: Forward port 80 (HTTP) and 443 (HTTPS) to your VM\u2019s IP.<\/p>\n

How?<\/em> Go into your router settings (again) and map those ports to the VM\u2019s local IP.<\/p>\n

Got no public IP?<\/em><\/strong> Services like Cloudflare Tunnels<\/strong> can expose your server securely without port forwarding.<\/p>\n

Step 3: Remote Access (AKA \u201cBe the Boss from Your Couch\u201d)<\/strong><\/h3>\n

You don\u2019t want to hunch over your server 24\/7. Set up SSH access<\/strong>:<\/p>\n

On your VM<\/strong>:<\/p>\n

Install OpenSSH:<\/p>\n

sudo apt install openssh-server<\/p>\n

Find the VM\u2019s IP:<\/p>\n

ip a<\/p>\n

On your main computer<\/strong>:<\/p>\n

Connect via SSH:<\/p>\n

ssh your-username@vm-ip-address<\/p>\n

Passwordless login?<\/em> Use SSH keys for extra security (Google \u201cssh-keygen tutorial\u201d).<\/p>\n

Step 4: Storage Solutions (Where to Dump Your Data)<\/strong><\/h3>\n

If you\u2019re hosting files, backups, or media, you\u2019ll need organized storage:<\/p>\n

For Proxmox Users<\/strong>:<\/h4>\n

Add a NAS\/SAN<\/strong>:<\/p>\n

Got a spare hard drive? Mount it in Proxmox under \u201cDatacenter > Storage\u201d.<\/p>\n

Assign it to VMs as needed (great for media servers like Plex).<\/p>\n

For Docker Users<\/strong>:<\/h4>\n

Bind Mounts<\/strong>:<\/p>\n

Link a folder on your host machine to a container:<\/p>\n

docker run -v \/path\/on\/host:\/path\/in\/container my-cool-app<\/p>\n

Step 5: Basic Security (Don\u2019t Get Hacked on Day 1)<\/strong><\/h3>\n

Before you invite the internet over:<\/p>\n

Firewall Rules<\/strong>:<\/p>\n

On your VM, allow only necessary ports:<\/p>\n

sudo ufw allow 22 # SSH sudo ufw allow 80 # HTTP sudo ufw enable<\/p>\n

Disable Root Login<\/strong>:<\/p>\n

Edit \/etc\/ssh\/sshd_config and set PermitRootLogin no.<\/p>\n

Automate Updates<\/strong>:<\/p>\n

Enable unattended upgrades:<\/p>\n

sudo apt install unattended-upgrades sudo dpkg-reconfigure unattended-upgrades<\/p>\n

Step 6: Test Your Setup<\/strong><\/h3>\n

Host a \u201cHello World\u201d website<\/strong>:<\/p>\n

Install NGINX on your VM:<\/p>\n

sudo apt install nginx<\/p>\n

Visit http:\/\/your-vm-ip in a browser. If you see the NGINX welcome page\u2014success!<\/strong> <\/p>\n

What\u2019s Next?<\/strong><\/h3>\n

Your DIY VPS is now alive<\/em>! But we\u2019re not done yet. Next up: Securing your server<\/strong> (because nobody wants crypto miners hijacking your hardware).<\/p>\n

Stay tuned\u2014security is sexy.<\/em> <\/p>\n

6. Securing Your DIY VPS Server <\/h2>\n

Security might sound boring, but trust me\u2014it\u2019s the difference between your DIY server being a reliable workhorse<\/em> and a zombie botnet recruit<\/em>. Let\u2019s lock this thing down like Fort Knox (but without the gold vaults).<\/p>\n

Step 1: Basic Security Must-Dos<\/strong><\/h3>\n

(Do this NOW if you\u2019re exposing your server to the internet.)<\/em><\/p>\n

Change Default Passwords<\/strong><\/p>\n

Proxmox<\/strong>: Change the root password.<\/p>\n

VMs\/Containers<\/strong>: Ditch admin\/password123. Use a password manager like Bitwarden.<\/p>\n

Bonus:<\/em> Use SSH keys instead of passwords (way safer).<\/p>\n

SSH Hardening<\/strong><\/p>\n

Disable root login and password-based SSH: <\/p>\n

sudo nano \/etc\/ssh\/sshd_config <\/p>\n

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

PermitRootLogin no
\nPasswordAuthentication no <\/p>\n

Restart SSH: <\/p>\n

sudo systemctl restart sshd<\/p>\n

Install Fail2Ban<\/strong> <\/p>\n

Stops brute-force attacks by banning sketchy IPs:<\/p>\n

sudo apt install fail2ban<\/p>\n

Default config works, but tweak\u00a0\/etc\/fail2ban\/jail.local\u00a0if you\u2019re paranoid.<\/p>\n

Step 2: Firewall Setup (Your Digital Bouncer)<\/strong><\/h3>\n

Don\u2019t let randos knock on your server\u2019s doors.<\/p>\n

UFW (Uncomplicated Firewall)<\/strong>: <\/p>\n

sudo ufw default deny incoming # Block all incoming traffic
\nsudo ufw allow 22 # Allow SSH (if using keys)
\nsudo ufw allow 80,443 # Allow HTTP\/HTTPS (for websites)
\nsudo ufw enable # Turn it on <\/p>\n

Proxmox Users<\/strong>:<\/p>\n

Use the built-in firewall under \u201cDatacenter > Firewall\u201d. Block everything except ports you need (8006 for the web UI).<\/p>\n

Step 3: Keep Software Updated<\/strong><\/h3>\n

Hackers love outdated software. Don\u2019t give them candy.<\/p>\n

Automate Updates<\/strong>: <\/p>\n

sudo apt install unattended-upgrades
\nsudo dpkg-reconfigure unattended-upgrades # Pick “Yes” <\/p>\n

Manual Check-ins<\/strong>: <\/p>\n

sudo apt update && sudo apt upgrade -y<\/p>\n

Step 4: Monitor Your Server (Like a Hawk)<\/strong><\/h3>\n

Know what\u2019s happening 24\/7:<\/p>\n

htop<\/strong>: sudo apt install htop htop<\/p>\n

Watch CPU\/RAM usage. If it\u2019s at 100%, time to upgrade or kill a process.<\/p>\n

Logwatch<\/strong>: sudo apt install logwatch<\/p>\n

Sends daily summaries of who tried to hack you<\/em> (spoiler: it\u2019s bots from Russia).<\/p>\n

Grafana + Prometheus<\/strong>:<\/p>\n

Fancy dashboards for nerds. Google \u201cProxmox Grafana setup\u201d if you want eye candy.<\/p>\n

Step 5: Backups (Because Stuff Breaks)<\/strong><\/h3>\n

Your server will<\/em> fail eventually. Be ready.<\/p>\n

Proxmox Backups<\/strong>:<\/p>\n

Go to \u201cDatacenter > Storage\u201d and add a backup drive\/NAS.<\/p>\n

Schedule nightly backups of your VMs.<\/p>\n

Docker Users<\/strong>:<\/p>\n

Use docker commit to save container snapshots, or back up bind-mounted folders.<\/p>\n

Offsite Backups<\/strong>:<\/p>\n

Sync critical data to Google Drive<\/strong>, Backblaze<\/strong>, or a friend\u2019s NAS.<\/p>\n

Step 6: Extra Paranoid? Try These<\/strong><\/h3>\n

VPN Access<\/strong>: Only allow SSH through a VPN (WireGuard is easy).<\/p>\n

Cloudflare Tunnel<\/strong>: Hide your server\u2019s IP and block bots.<\/p>\n

2FA for Proxmox<\/strong>: Install Google Authenticator for the web UI.<\/p>\n

Test Your Security<\/strong><\/h3>\n

Run a port scan with nmap<\/strong>: sudo apt install nmap nmap -sV your-server-ip<\/p>\n

If you see open ports you didn\u2019t allow, fix your firewall!<\/p>\n

What\u2019s Next?<\/strong><\/h3>\n

Your server is now safer than a TikTok influencer\u2019s selfie archive. Next up: Maintaining and scaling your setup<\/strong> (because even servers need TLC).<\/p>\n

Stay tuned\u2014let\u2019s keep this party going!<\/em> <\/p>\n

Next Section<\/strong>: [7. Maintaining and Scaling Your Server]<\/p>\n

7. Maintaining and Scaling Your Server<\/h2>\n

Your DIY VPS server is up, running, and secure\u2014nice work! But like a pet cactus, it needs a little care to thrive. Let\u2019s talk about keeping it healthy<\/strong> and scaling it up<\/strong> when you\u2019re ready to go big. No PhD in serverology required.<\/p>\n

Part 1: Routine Maintenance (The Boring-but-Necessary Stuff)<\/strong><\/h3>\n

1.1 Update All the Things<\/strong><\/h3>\n

Weekly Check-ins<\/strong>: <\/p>\n

sudo apt update && sudo apt upgrade -y # For Debian\/Ubuntu
\nsudo dnf update -y # For Fedora\/CentOS <\/p>\n

Pro Tip:<\/em> Set a calendar reminder. Outdated software = hacker candy.<\/p>\n

Update Proxmox\/Docker<\/strong>:<\/p>\n

Proxmox: apt update && apt dist-upgrade from the shell.<\/p>\n

Docker: sudo docker-compose pull if you\u2019re using Compose.<\/p>\n

1.2 Clean Up Digital Junk<\/strong><\/h3>\n

Servers hoard garbage like a reality TV show. Free up space:<\/p>\n

Delete old kernels\/logs<\/strong>: <\/p>\n

sudo apt autoremove && sudo apt clean # Debian\/Ubuntu
\nsudo journalctl –vacuum-time=7d # Clear logs older than 7 days <\/p>\n

Docker Prune<\/strong>: <\/p>\n

docker system prune -a –volumes # Nuke unused containers\/images<\/p>\n

1.3 Monitor Performance<\/strong><\/h3>\n

Is your server sweating bullets? Check its vitals:<\/p>\n

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

Look for CPU\/RAM hogs (if Minecraft is eating 90% RAM, you know why).<\/p>\n

Disk Space<\/strong>: df -h # Check storage usage<\/p>\n

Network Traffic<\/strong>: nload # Real-time bandwidth monitor<\/p>\n

1.4 Test Backups (Seriously, Do This)<\/strong><\/h3>\n

Your backups are useless unless they work<\/em>. Once a month:<\/p>\n

Restore a VM\/container<\/strong> to a test environment.<\/p>\n

Spot-check critical files<\/strong> (like your website\u2019s database).<\/p>\n

Part 2: Scaling Up (When Your Server Needs Steroids)<\/strong><\/h3>\n

2.1 Vertical Scaling: Upgrade Your Hardware<\/strong><\/h3>\n

Translation: Throw more RAM\/CPU\/storage at it.<\/em><\/p>\n

Add RAM<\/strong>: Swap in bigger sticks (check motherboard limits).<\/p>\n

Upgrade to SSD<\/strong>: If you\u2019re still using a 2008-era HDD, stop. Now.<\/p>\n

Attach External Storage<\/strong>: USB drives or NAS boxes for cheap storage.<\/p>\n

2.2 Horizontal Scaling: Add More Servers<\/strong><\/h3>\n

Translation: Turn one server into a cluster<\/strong>.<\/em><\/p>\n

Proxmox Cluster<\/strong>:<\/p>\n

Add more old machines to Proxmox and manage them as a single system.<\/p>\n

Migrate VMs between nodes without downtime.<\/p>\n

Docker Swarm\/Kubernetes<\/strong>:<\/p>\n

Spread containers across multiple machines.<\/p>\n

Example: <\/p>\n

docker swarm init # Make your current server the “manager”
\ndocker swarm join # Add other machines as “workers” <\/p>\n

2.3 Optimize What You\u2019ve Got<\/strong><\/h3>\n

Limit Resource Hogging<\/strong>:<\/p>\n

In Proxmox, set CPU\/RAM limits per VM so one app doesn\u2019t starve others.<\/p>\n

Use Lightweight OSes<\/strong>:<\/p>\n

Switch VMs to Alpine Linux (Docker-friendly) or Ubuntu Core.<\/p>\n

Part 3: Troubleshooting Common Issues<\/strong><\/h3>\n

3.1 \u201cMy Server is Slow!\u201d<\/strong><\/h3>\n

Check RAM\/CPU<\/strong>: htop<\/p>\n

Kill Zombie Processes<\/strong>: <\/p>\n

sudo kill -9 $(pidof annoying-app) # Replace “annoying-app” with the culprit<\/p>\n

Clear Disk Space<\/strong>: Delete old Docker images, logs, or VM snapshots.<\/p>\n

3.2 \u201cThe Internet Can\u2019t Reach My Server!\u201d<\/strong><\/h3>\n

Test Ports<\/strong>: nc -zv your-server-ip 80 # Is port 80 open?<\/p>\n

Check Firewalls<\/strong>:<\/p>\n

Is UFW\/iptables blocking traffic?<\/p>\n

Did your ISP change your public IP?<\/p>\n

3.3 \u201cMy VM Won\u2019t Boot!\u201d<\/strong><\/h3>\n

Restore from Backup<\/strong>: Proxmox lets you roll back to a working snapshot.<\/p>\n

Check Logs<\/strong>: journalctl -xe # Find the error message haunting you<\/p>\n

Part 4: When to Call It Quits<\/strong><\/h3>\n

Even Rocky admits when it\u2019s time to upgrade. Consider a commercial VPS if<\/strong>:<\/p>\n

Your DIY server crashes weekly.<\/p>\n

Your electricity bill costs more than a $5\/month DigitalOcean droplet.<\/p>\n

You need 99.9% uptime for a business.<\/p>\n

What\u2019s Next?<\/strong><\/h3>\n

You\u2019re officially a DIY server guru. The final chapter: Practical Use Cases<\/strong> (host websites, game servers, media hubs\u2014let\u2019s get creative!). <\/p>\n

8. Practical Use Cases<\/strong><\/h2>\n

Now for the fun part<\/em>\u2014what can you actually DO<\/strong> with your DIY VPS server? Turns out, a lot<\/em>. It\u2019s like turning your old PC into a Swiss Army knife for the digital age. Let\u2019s get to it!<\/p>\n

1. Host Your Own Website or Blog<\/strong> <\/h3>\n

Why?<\/strong><\/p>\n

No more paying $10\/month for shared hosting. Your rules, your content.<\/em><\/p>\n

Perfect for portfolios, blogs, or even a small business site.<\/p>\n

How?<\/strong><\/p>\n

Install a LAMP\/LEMP stack<\/strong>: <\/p>\n

# LAMP (Apache, MySQL, PHP):
\nsudo apt install apache2 mysql-server php libapache2-mod-php <\/p>\n

# LEMP (Swap Apache for Nginx):
\nsudo apt install nginx mysql-server php-fpm <\/p>\n

Throw your HTML\/CSS files into \/var\/www\/html or use WordPress: <\/p>\n

sudo apt install wordpress<\/p>\n

Point your domain to your server\u2019s IP (use Cloudflare<\/strong> for free SSL).<\/p>\n

Pro Tip:<\/strong><\/em> Use Let\u2019s Encrypt for free HTTPS certificates. No cap.<\/em><\/p>\n

2. Run a Game Server for You and the Boys<\/strong> <\/h3>\n

Why?<\/strong><\/p>\n

Host Minecraft, Valheim, or CS:GO servers without lagging out.<\/p>\n

Cheaper than renting\u2014and you control who joins.<\/p>\n

How (Minecraft Example):<\/strong><\/p>\n

Install Java: <\/p>\n

sudo apt install openjdk-17-jdk<\/p>\n

Download the Minecraft server .jar: <\/p>\n

wget <https:\/\/piston-data.mojang.com\/v1\/objects\/…\/server.jar><\/p>\n

Run it: <\/p>\n

java -Xmx4G -Xms4G -jar server.jar nogui # Allocate 4GB RAM<\/p>\n

Forward port 25565<\/strong> in your router.<\/p>\n

Pro Tip:<\/strong><\/em> Use Docker for one-click game server setups (check out LinuxGSM<\/strong>).<\/em><\/p>\n

3. Build a Media Streaming Server (Netflix, But Free)<\/strong> <\/h3>\n

Why?<\/strong><\/p>\n

Stream your movie\/TV collection anywhere. No ads, no subscriptions.<\/p>\n

How (With Jellyfin):<\/strong><\/p>\n

Install Docker: <\/p>\n

sudo apt install docker.io<\/p>\n

Run Jellyfin: <\/p>\n

docker run -d
\n–name jellyfin
\n-v \/path\/to\/movies:\/media
\n-p 8096:8096
\njellyfin\/jellyfin <\/p>\n

Access it at http:\/\/your-server-ip:8096 and organize your library.<\/p>\n

Pro Tip:<\/strong><\/em> Pair with Sonarr<\/strong> and Radarr<\/strong> to auto-download new episodes\/movies.<\/em><\/p>\n

4. Create a Smart Home Hub<\/strong> <\/h3>\n

Why?<\/strong><\/p>\n

Control lights, thermostats, or security cams without relying on Big Tech.<\/p>\n

How (Home Assistant):<\/strong><\/p>\n

Install Docker (if you haven\u2019t): <\/p>\n

sudo apt install docker.io<\/p>\n

Run Home Assistant: <\/p>\n

docker run -d
\n–name homeassistant
\n-v \/path\/to\/config:\/config
\n–network=host
\nhomeassistant\/home-assistant <\/p>\n

Integrate with Alexa\/Google Home, Zigbee devices, or ESP32 sensors.<\/p>\n

Pro Tip:<\/strong><\/em> Add Node-RED<\/strong> for fancy automations (like \u201cgoodnight\u201d scenes).<\/em><\/p>\n

5. Host Your Own VPN (Become a Privacy Ninja)<\/strong> <\/h3>\n

Why?<\/strong><\/p>\n

Browse securely on public Wi-Fi.<\/p>\n

Access your home network remotely (like grabbing files while traveling).<\/p>\n

How (WireGuard in 5 Minutes):<\/strong><\/p>\n

Install WireGuard: <\/p>\n

sudo apt install wireguard<\/p>\n

Generate keys: <\/p>\n

wg genkey | sudo tee \/etc\/wireguard\/privatekey | wg pubkey | sudo tee \/etc\/wireguard\/publickey<\/p>\n

Set up config: <\/p>\n

sudo nano \/etc\/wireguard\/wg0.conf <\/p>\n

Paste: <\/p>\n

[Interface]
\nPrivateKey = <your-private-key>
\nAddress = 10.0.0.1\/24
\nListenPort = 51820 <\/p>\n

[Peer]
\nPublicKey = <your-phone\u2019s-public-key>
\nAllowedIPs = 10.0.0.2\/32 <\/p>\n

Start it: <\/p>\n

sudo wg-quick up wg0<\/p>\n

Pro Tip:<\/strong><\/em> Use QR codes to easily connect your phone (Google \u201cwg-quick qr code\u201d).<\/em><\/p>\n

6. Spin Up a Development Sandbox<\/strong> <\/h3>\n

Why?<\/strong><\/p>\n

Test code, learn Kubernetes, or break things without frying your main PC.<\/p>\n

How (VS Code + Docker):<\/strong><\/p>\n

Install Docker and Docker Compose.<\/p>\n

Deploy a code-server<\/strong> (VS Code in your browser): <\/p>\n

docker run -d
\n–name code-server
\n-p 8080:8080
\n-v \/path\/to\/projects:\/home\/coder\/project
\ncodercom\/code-server <\/p>\n

Access it at http:\/\/your-server-ip:8080 and code away.<\/p>\n

Pro Tip:<\/strong><\/em> Add Portainer<\/strong> to manage Docker containers visually.<\/em><\/p>\n

7. Backup Everything (Because Life\u2019s Unpredictable)<\/strong> <\/h3>\n

Why?<\/strong><\/p>\n

Auto-backup photos, documents, or game saves to your own server.<\/p>\n

How (With Nextcloud):<\/strong><\/p>\n

Install Docker.<\/p>\n

Run Nextcloud: <\/p>\n

docker run -d
\n–name nextcloud
\n-v \/path\/to\/data:\/var\/www\/html
\n-p 8080:80
\nnextcloud <\/p>\n

Sync files via the Nextcloud mobile\/desktop app.<\/p>\n

Pro Tip:<\/strong><\/em> Pair with Rclone<\/strong> to mirror backups to Google Drive or Dropbox.<\/em><\/p>\n

8. Run a Private ChatGPT-Style AI<\/strong> <\/h3>\n

Why?<\/strong><\/p>\n

Mess with AI models without sending data to OpenAI.<\/p>\n

How (Ollama + Docker):<\/strong><\/p>\n

Install Docker.<\/p>\n

Run Ollama: <\/p>\n

docker run -d
\n–name ollama
\n-p 11434:11434
\n-v \/path\/to\/models:\/root\/.ollama
\nollama\/ollama <\/p>\n

Pull a model: <\/p>\n

docker exec ollama ollama pull llama2<\/p>\n

Chat via CLI or API.<\/p>\n

Final Thoughts<\/strong><\/h3>\n

Your DIY VPS is limited only by your imagination (and maybe RAM). Start small, break things, and scale up as you go. Who knows? That old machine might just become your favorite tech toy.<\/p>\n

Go build something awesome\u2014and tag me when you do!<\/em> <\/p>\n

Conclusion<\/h2>\n

We\u2019ve come a long way, haven\u2019t we? That dusty old machine you almost tossed out? Now it\u2019s a full-blown VPS server<\/strong> doing things you probably never thought possible. Let\u2019s take a sec to high-five ourselves and recap why this journey was worth it.<\/p>\n

Why This Rocks<\/strong> <\/h3>\n

You Saved Cash<\/strong>: Instead of dropping $5\u2013$50\/month on a cloud VPS, you\u2019re running your own show for free<\/em> (minus snacks and electricity).<\/p>\n

You Helped the Planet<\/strong>: That old hardware isn\u2019t clogging a landfill\u2014it\u2019s now a productivity beast. <\/p>\n

You Leveled Up<\/strong>: You\u2019re now the friend who \u201cknows servers.\u201d Congrats on the newfound tech cred.<\/p>\n

Was It Easy?<\/strong> <\/h3>\n

Let\u2019s be real\u2014this wasn\u2019t a one-click process. You battled terminal commands, wrestled with firewalls, and maybe even cried over a misconfigured VM. But look at you now! You\u2019ve turned a paperweight into a powerhouse.<\/p>\n

Remember<\/em><\/strong>: Servers are like Tamagotchis. They need love (updates), food (electricity), and the occasional reboot. But unlike Tamagotchis, yours can host a blog.<\/p>\n

What\u2019s Next?<\/strong> <\/h3>\n

Your DIY VPS is a blank canvas. Here\u2019s how to keep the fun going:<\/p>\n

Break Stuff<\/strong>: Experiment! Host a Minecraft server for friends, build a private ChatGPT, or automate your home. If it crashes? Restore a backup and try again.<\/p>\n

Upgrade Gradually<\/strong>: Add more RAM, hook up a NAS, or cluster a second old laptop. Sky\u2019s the limit.<\/p>\n

Share the Knowledge<\/strong>: Teach a buddy how to do this. They\u2019ll owe you pizza forever.<\/p>\n

A Final Pep Talk<\/strong> <\/h3>\n

Tech moves fast, but you\u2019ve just proven that \u201cold\u201d doesn\u2019t mean \u201cuseless.\u201d With a little grit and Google-fu, you\u2019ve hacked together a server that rivals paid services. So pat yourself on the back, then go break something else.<\/p>\n

Your closet server might just be the start of something bigger.<\/em> Who knows? Maybe that Raspberry Pi collecting dust is your next project\u2026<\/p>\n

Thanks for rocking with me!<\/strong>
Got questions? Hit me up in the comments. And if you built something cool, I wanna see it<\/em>. Tag me, tweet me, carrier pigeon me\u2014just don\u2019t leave me hanging.<\/p>\n

Rocky out.<\/em> <\/strong><\/p>\n

FAQs<\/strong> <\/h2>\n

Let\u2019s tackle those burning questions you\u2019ve been DMing me about. No jargon, no fluff\u2014just straight answers.<\/p>\n

Q1: Can I use a Raspberry Pi as a VPS server?<\/strong><\/h3>\n

A:<\/strong> Absolutely!<\/em> A Raspberry Pi 4 or 5 can totally handle lightweight VPS duties (hosting a blog, VPN, or small game server). Just slap Ubuntu Server or Docker on it, and you\u2019re golden. But don\u2019t expect it to host Minecraft<\/em> for 20 players\u2014it\u2019s more of a \u201chobbyist hero\u201d than a powerhouse.<\/p>\n

Pro Tip:<\/em><\/strong> Pi\u2019s use way less power than an old PC. Perfect for 24\/7 tinkering!<\/em><\/p>\n

Q2: How much electricity will my DIY VPS consume?<\/strong><\/h3>\n

A:<\/strong> Depends on your hardware:<\/p>\n

Old desktop<\/strong>: 50\u2013150 watts (\u2248$5\u2013$15\/month in electricity).<\/p>\n

Laptop<\/strong>: 20\u201350 watts (\u2248$2\u2013$5\/month).<\/p>\n

Raspberry Pi<\/strong>: 5\u201310 watts (\u2248$0.50\/month).<\/p>\n

Translation:<\/em><\/strong> If your setup costs more than a $5\/month DigitalOcean droplet, it\u2019s time to rethink.<\/em><\/p>\n

Q3: Is this setup reliable for production environments?<\/strong><\/h3>\n

A:<\/strong> Eh\u2026 maybe?<\/em> For personal projects, homelabs, or learning? 100% yes<\/strong>. For a business-critical app? Nope<\/strong>. Commercial VPS providers offer uptime guarantees, backups, and support. Your DIY server might crash during a Netflix binge if your cat unplugs it.<\/p>\n

Q4: How does this compare to commercial VPS providers like AWS or DigitalOcean?<\/strong><\/h3>\n

A:<\/strong> Let\u2019s break it down:<\/p>\n

Cost<\/strong>: DIY = $0\/month (minus electricity). AWS = $5\u2013$50\/month.<\/p>\n

Control<\/strong>: DIY = Full root access. AWS = Their rules.<\/p>\n

Convenience<\/strong>: AWS = 1-click scaling, 24\/7 support. DIY = You<\/em> are the support.<\/p>\n

Verdict:<\/em><\/strong> DIY for fun\/learning. Commercial for \u201cI need this to work<\/em> now<\/em><\/strong>.\u201d*<\/p>\n

Q5: Do I need a static IP from my ISP?<\/strong><\/h3>\n

A:<\/strong> Not really! Use Dynamic DNS<\/strong> (like DuckDNS or Cloudflare) to link a domain to your changing home IP. Or hide behind a Cloudflare Tunnel<\/strong> (free and secure).<\/p>\n

Pro Tip:<\/em><\/strong> Cloudflare Tunnels > Port forwarding. Fight me.<\/em><\/p>\n

Q6: What if my old machine doesn\u2019t support virtualization?<\/strong><\/h3>\n

A:<\/strong> No VT-x\/AMD-V?<\/em> You can still use Docker<\/strong> or lightweight containers. Avoid full VMs\u2014they\u2019ll crawl. Or buy a $10 used CPU that supports virtualization (eBay is your friend).<\/p>\n

Q7: Can I host multiple websites or services on one DIY VPS?<\/strong><\/h3>\n

A:<\/strong> Yup!<\/em> Use Docker<\/strong> or Proxmox<\/strong> to split resources:<\/p>\n

Run 5 WordPress sites in Docker containers.<\/p>\n

Host a game server + media server in separate VMs.
Just don\u2019t overload your RAM\u2014nobody likes a laggy server.<\/p>\n

Q8: How do I access my server remotely?<\/strong><\/h3>\n

A:<\/strong> Two words: SSH<\/strong> and VPN<\/strong>.<\/p>\n

SSH: ssh yourname@server-ip (works anywhere).<\/p>\n

VPN (WireGuard): Tunnel into your home network like a spy.<\/p>\n

Noob move:<\/em><\/strong> Don\u2019t expose SSH port 22 to the internet. Use a VPN or Cloudflare Tunnel.<\/em><\/p>\n

Q9: What are the risks of self-hosting vs. commercial?<\/strong><\/h3>\n

A:<\/strong> Risks include:<\/p>\n

Security<\/strong>: Hackers love poorly secured DIY servers.<\/p>\n

Uptime<\/strong>: Your ISP hiccups = your server dies.<\/p>\n

Data Loss<\/strong>: No RAID? Hope you like backups.<\/p>\n

Fix it:<\/em><\/strong> Use fail2ban, automate backups, and pray to the Wi-Fi gods.<\/em><\/p>\n

Q10: How do I back up my VPS?<\/strong><\/h3>\n

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

Proxmox<\/strong>: Schedule VM snapshots to an external drive.<\/p>\n

Docker<\/strong>: Use docker commit or back up bind-mounted folders.<\/p>\n

Nuclear Option<\/strong>: Clone your entire drive with Clonezilla<\/strong>.<\/p>\n

Pro Tip:<\/em><\/strong> Follow the 3-2-1 rule: 3 copies, 2 formats, 1 offsite.<\/em><\/p>\n

Still stuck?<\/strong> Drop a comment or hit me up. I\u2019ve got your back. <\/p>\n

If you liked the article,\u00a0like and subscribe<\/strong>\u00a0to my channel\u00a0\u201cCodelivly<\/a>\u201d.<\/strong><\/p>","protected":false},"excerpt":{"rendered":"

Hey guys, Rocky here! So you\u2019ve got a dusty old laptop or computer taking up space in the corner? Perhaps it\u2019s that hulking desktop from 2012 or that gaming machine you upgraded for something new and flashy. Before you throw it on eBay for $5 or repurpose it as an elegant doorstop, let me strike […]<\/p>\n","protected":false},"author":0,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2829","post","type-post","status-publish","format-standard","hentry","category-blog"],"_links":{"self":[{"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/posts\/2829"}],"collection":[{"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2829"}],"version-history":[{"count":0,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/posts\/2829\/revisions"}],"wp:attachment":[{"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2829"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2829"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2829"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}