PROJECT LOG: ASHBUILDS.NZ

Old Laptop → Linux Server

Repurposing a dead-battery laptop into a self-hosted Linux server. This is the foundation everything else on this site runs on. Documented here using a real project management framework, not just a how-to.

STATUS: LIVE HOST: server123 SPEND: ~$30 / $100 budget STACK: Mint · Nginx · Cloudflare Tunnel
01

Charter

Why this project exists, and what "done" looks like.

Having transitioned into ICT study after a decade in outdoor education, I found myself feeling behind my classmates, most of whom are a younger generation. This project converts an old laptop into a self-hosted Linux server: a low-cost, hands-on platform to build real skills in networking, sysadmin work, and web hosting through my own projects, rather than coursework alone.

02

Scope

What's included in this project, and what deliberately isn't.

BoundaryItem
IN SCOPEWipe existing OS, install Linux Mint
IN SCOPEConfigure the laptop as a functioning server
IN SCOPEInstall & configure Nginx to host content
IN SCOPESolve remote access under CGNAT via Cloudflare Tunnel + domain
OUT OF SCOPEPurchasing new hardware
OUT OF SCOPEDirect/external IP hosting (traditional port forwarding)
OUT OF SCOPEThe content hosted on the server (bird AI galleries, Warhammer galleries): separate projects
03

Work Breakdown

Three phases, each ending at a go/no-go checkpoint.

1 Hardware Check
1.1Test old PC health
1.2Diagnose & remove dead battery
1.3Source SSD to hold Linux
2 OS Migration
2.1Wipe Windows
2.2Install Linux Mint
2.3Update system + install base packages
3 Connectivity & Hosting
3.1Attempt public IP hosting (blocked by CGNAT)
3.2Set up Cloudflare Tunnel
3.3Purchase domain: ashbuilds.nz
3.4Build test site to confirm public visibility
04

Constraints & Assumptions

Known limits going in, vs. beliefs that turned out to be tested.

TypeItem
ConstraintHardware capability: old specs capped what the server could realistically handle.
ConstraintBudget: no formal budget set; self-imposed ceiling ~$100 NZD, actual spend ~$30.
ConstraintSkill set: had many individual skills, but not combined in one prior project.
AssumptionRouter would have a public-facing IP. Turned out false (CGNAT).
AssumptionThe project would be too much work / beyond current ability. Turned out false.
05

Risk Register

What could go wrong, and how it was actually handled.

Hardware insufficient for the task
RESOLVED
Impact: High: unplanned spend, budget break  ·  Tested early in Phase 1 before further commitment. Hardware proved adequate.
ISP/network blocks public hosting (CGNAT)
RESOLVED
Impact: High: site unreachable  ·  Occurred as expected. Mitigated via Cloudflare Tunnel workaround.
Server gets hacked / attacked online
ONGOING
Impact: High: data loss, network compromise  ·  Cloudflare Tunnel limits inbound exposure + UFW firewall active (port 22 only). Full hardening pass (key auth, fail2ban) planned as a dedicated future session.
06

Milestones

The build, as it actually happened.

ash@server123: ~/project-log
[ OK ]M1Hardware confirmed working: battery diagnosed & removed, SSD ready 2–3 hrs
[ OK ]M2Linux Mint installed & updated 3–4 hrs
[ OK ]M3Site publicly reachable via ashbuilds.nz 4 days
[ OK ]M4UFW firewall enabled: port 22 only 29 Jul 2026
[ .. ]M5Full security hardening: key auth, fail2ban planned
ash@server123:~$
07

Addendum: Plan vs. Actual

A second scoping document was written separately, targeting SSH access, file upload, and web hosting as three success criteria. It was drafted before the CGNAT issue was discovered, so it's a useful comparison: what was planned vs. what actually happened.

CriterionPlannedActual
1. SSH from outside LAN Via router port forwarding NOT MET  Blocked by CGNAT, same wall hit with the website. SSH currently only reachable from inside the home network.
2. File upload from LAN SFTP over SSH, or Samba share PARTIALLY MET  WinSCP has been used throughout via SFTP over SSH, satisfying the method. No dedicated folder/permissions were deliberately configured for it though, so it wasn't a planned deliverable at the time.
3. Web hosting software installed Install, test on LAN only EXCEEDED  Nginx installed and live publicly via Cloudflare Tunnel + domain, beyond the original LAN-only scope.

Worth logging honestly: criterion 1 remains an open item, tied to the same CGNAT constraint already on this page, and is planned to be addressed as part of the future full security hardening session rather than solved piecemeal now.

08

Lessons Learned

What I'd tell myself before starting this again.

01

IP addressing is more complicated than first understood.

CGNAT wasn't something I could've known without hitting it. Now I check ISP-level networking before assuming direct hosting is possible.
02

There's always a workaround if you stay creative.

Cloudflare Tunnel wasn't the textbook answer; it was a pivot after the first plan failed.
03

Security setup is never wasted effort.

Proven directly during this write-up: enabling UFW took under five minutes and closed a real gap that had sat open the whole time.