Live Deployment on adam-vps.arepp.cloud • Port 3123

How Web Deployment & Ops Actually Work

A hands-on interactive guide built to demystify Local vs. Public IPs, Domains & DNS, Default vs. Custom Ports, and how Nginx Proxy Manager routes public HTTP (80) & HTTPS (443) traffic to an app running locally on port 3123.

Module 01 • Networking Foundation

Local IP Address vs. Public IP Address

Every computer on a network needs an address so data packets know where to go. Confusion happens because a server actually has two different kinds of IP addresses at the same time: one for inside the building (Local) and one for the outside world (Public).

πŸ“˜ Technical Concept

What is the Difference?

  • Public IP Address (External): Assigned by your Internet Service Provider (ISP) or Cloud Host. It is globally unique across the entire planet. Anyone on the internet can reach this IP (if firewall rules allow).
  • Local / Private IP Address (Internal): Used only inside a private network (like your home Wi-Fi or internal data center LAN). Reserved ranges include 192.168.x.x, 10.x.x.x, and 172.16.x.x.
  • Loopback IP (127.0.0.1 / localhost): A special local address that always means "this exact computer I am running on right now."
🏒 Simple Analogy

Apartment Street Address vs. Room Number

Imagine a giant apartment building or office tower:

  • Public IP = Street Address (175.142.140.243): Every delivery driver in the world uses the official street address to find your building on Google Maps. No two buildings share the same full street address.
  • Local IP = Room Number (172.16.100.202 or 192.168.1.5): Once inside the building, rooms are labeled "Room 202" or "Kitchen". Millions of buildings have a "Room 202"β€”and that's fine because you only use it inside the building!
  • 127.0.0.1 = "My Own Desk": Leaving a sticky note on 127.0.0.1 means leaving it on your own desk for yourself.
⚑ Real-World Server Example

How Our VPS Uses Both

  • When we run ip a inside adam-vps, Linux shows its Local IP is 172.16.100.202. Other machines in the same server rack (like Nginx Proxy Manager) talk to it directly at 172.16.100.202!
  • When a friend on mobile data visits adam-vps.arepp.cloud, their phone cannot reach 172.16.100.202 directly because that's a private room number.
  • Instead, their phone connects to the Public IP 175.142.140.243 at the router gateway, which forwards the traffic inside!
πŸ§ͺ Interactive Lab: Click an IP Address to See Who Can Reach It
INTERACTIVE PACKET SCOPE
πŸ–₯️ Same Server
(Inside OS)
→
πŸ–§ Local Network
(Same Wi-Fi / LAN)
→
🌍 Public Internet
(Anyone Worldwide)
Module 02 • Naming the Internet

What is a Domain Name & What is DNS?

Computers only communicate using numerical IP addresses like 175.142.140.243. Humans are terrible at memorizing strings of numbers, so we invented Domain Names and the Domain Name System (DNS).

πŸ“˜ Technical Concept

Domain vs. DNS

  • Domain Name: The human-readable web address you register (e.g. arepp.cloud) and its subdomains (e.g. adam-vps.arepp.cloud).
  • DNS (Domain Name System): A global distributed database that translates Domain Names into IP Addresses.
  • DNS A Record: The most important DNS entry! An A (Address) Record maps a name directly to an IPv4 Public IP:
    adam-vps.arepp.cloud → 175.142.140.243
πŸ“± Simple Analogy

Your Smartphone's Contacts App

  • Domain Name = Contact Name ("Adam VPS"): It's easy to remember and tell your friends: "Call Adam!"
  • Public IP = Phone Number (175-142-140-243): The cellular network cannot dial lettersβ€”it only dials digits.
  • DNS = The Contacts App Lookup: When you tap "Adam VPS", your phone automatically looks up his contact card (A Record), grabs the number 175.142.140.243, and dials it behind the scenes!
⚑ Real-World Server Example

Why DNS Saves You Headaches

  • Suppose next month you move your server to a new ISP and your Public IP changes from 175.142.140.243 to 203.0.113.88.
  • Without a domain, every user who bookmarked your old IP would get a broken page!
  • With DNS, you just open Cloudflare / your DNS dashboard and update the A Record for adam-vps.arepp.cloud to the new IP. Everyone keeps using the exact same domain name!
πŸ” Interactive DNS Lookup Simulator
LIVE RESOLUTION FLOW
dig
STEP 01 • BROWSER INPUT

User Types Domain

You type adam-vps.arepp.cloud into Chrome. Chrome doesn't know what IP that is yet.

STEP 02 • ASK DNS RESOLVER

Query Phonebook

Your computer asks a DNS Resolver (like Cloudflare 1.1.1.1 or Google 8.8.8.8): "Who has the A Record for adam-vps.arepp.cloud?"

STEP 03 • DNS RECORD MATCH

A-Record Found!

The Authoritative DNS server for arepp.cloud replies: A Record = 175.142.140.243.

STEP 04 • DIRECT CONNECTION

Browser Dials the IP

Chrome now connects directly to Public IP 175.142.140.243 while keeping adam-vps.arepp.cloud in the address bar!

Module 03 • Application Doors

What is a Port? (Default Ports vs. Custom Ports)

The IP address brings traffic to the right server computer. But a single server runs dozens of different programs at the same time (SSH, Nginx, Databases, Python apps, Node.js apps). How does the server know which application should receive a packet? By its Port Number (1 to 65535)!

πŸ“˜ Technical Concept

Default vs. Custom Ports

  • One Rule: Only ONE program can listen on a specific IP + Port number at the same time!
  • Default (Well-Known) Ports: Standardized port numbers built into every browser and tool so you don't have to type them:
    • Port 80 = Default HTTP
    • Port 443 = Default HTTPS
    • Port 22 = Default SSH
  • Custom Application Ports: When you deploy your own apps (Node, Python, Docker), you give each app its own custom port like 3000, 3123, or 8080 so they never collide!
πŸšͺ Simple Analogy

Doors & Room Extensions in One Building

  • Think of the IP Address as the Building Address, and each Port Number as a numbered Door or Service Window inside that building.
  • Default Ports (Doors #80 & #443): These are the Main Front Lobby Doors. When a customer visits a store, they automatically walk to the front entrance without needing instructions.
  • Custom Ports (Room #3123): Inside the building, each workshop gets its own private room number! Our Ops Guide app works inside Studio Room #3123, while another app works in Room #3000.
⚑ Real-World Server Example

What Happens on adam-vps Right Now

  • On adam-vps, there is already a Portfolio web server listening on Port 80.
  • If we tried to start this Ops Education site on Port 80 too, Linux would immediately crash with:
    OSError: [Errno 98] Address already in use!
  • By hosting this new website on custom Port 3123, both websites run side-by-side on the exact same VPS without any conflict!
🏒 Interactive Server Port Inspector β€” Click Any Door on adam-vps
PORT MAP: 1 – 65535
Module 04 • Reverse Proxy Magic

How Nginx Proxy Manager Routes Port 80 & 443 to Local Port 3123

Here is the million-dollar Ops question: If our website is hosted locally on the server at custom port 3123, how do normal visitors access it using a clean URL with http:// (Port 80) or https:// (Port 443) without typing :3123? That is the job of Nginx Proxy Manager (Reverse Proxy)!

πŸ“˜ Technical Concept

What Nginx Proxy Manager Does

  • 1. Guards the Public Doors (80 & 443): Nginx Proxy Manager (NPM) is the only service exposed to the public internet on standard ports 80 (HTTP) and 443 (HTTPS).
  • 2. Handles HTTPS & SSL Certificates: When a user connects on Port 80, NPM redirects them to Port 443 and provides the Let's Encrypt HTTPS padlock automatically.
  • 3. Routes by Domain Name to Custom Port: NPM reads which domain the visitor asked for, then privately forwards (proxies) the request to your app's local IP and custom port (e.g., http://172.16.100.202:3123 or http://127.0.0.1:3123)!
πŸ›ŽοΈ Simple Analogy

The Hotel Front Desk Concierge

  • Imagine a luxury hotel where every guest from the street enters through the Main Lobby Entrance (Port 80 / 443).
  • Nginx Proxy Manager is the Front Desk Receptionist: Guests never wander into the back hallways looking for Room #3123!
  • The guest tells the receptionist: "I'm here for the Ops Guide website."
  • The receptionist checks their lookup sheet, calls Internal Room #3123 (Local IP : 3123), grabs the webpage from your app, puts it in a secure HTTPS envelope (Port 443), and hands it to the guest!
⚑ Real-World Server Example

Hosting 10 Websites on 1 Public IP

  • Because of Nginx Proxy Manager, a single server with one Public IP can host dozens of websites simultaneously:
  • • https://adam-vps.arepp.cloud (Port 443) → NPM routes to 172.16.100.202:80
    • https://edu.arepp.cloud (Port 443) → NPM routes to 172.16.100.202:3123
    • https://api.arepp.cloud (Port 443) → NPM routes to 172.16.100.202:5000
  • Visitors always use clean https:// (Port 443), while each app lives safely on its own custom port!
πŸš€ Interactive Traffic Flow Simulator: Watch How a Request Travels
HTTP (80) / HTTPS (443) → PORT 3123
Practice Lab: Configure Nginx Proxy Manager Rule for Port 3123
Nginx Proxy Manager Admin (:81)
Module 05 • Knowledge Check

Interactive Ops & Deployment Questionnaire

Test your understanding with 12 real-world scenarios! Click any answer option to immediately unlock a Technical Explanation, a Real-World Server Example, and a Simple Analogy.

Score: 0 / 0 Answered