OPS Notes · Real Fixes & SOPs

IT Operations
Notes

A growing collection of practical IT field notes: incidents, service recovery steps, troubleshooting decisions, and reusable SOPs from real administration work.

OPS
Series Code
1
Published Note
SOP
Documentation Type
Live
Operations Focus
What This Is

Everyday operational work, documented professionally.

This section collects standalone notes from real IT work: when a service breaks, a configuration behaves differently than expected, or a recovery process becomes useful enough to document. The goal is to show how I diagnose issues, restore service, and turn experience into repeatable operating knowledge.

Scope

Small fixes can still show serious skills.

Not every valuable IT story is a large portfolio project. These notes focus on practical judgment: reading symptoms, checking logs, isolating layers, choosing a safe fix, validating recovery, and recording what should be monitored next time.

Incident Response Linux & Web Hosting Service Recovery Cloudflare & DNS Troubleshooting SOPs
Published Notes

Operations Library

Each note is written as a practical recovery record: what failed, how it was checked, what restored service, and what should be improved for the next incident.

OPS-001 · Incident SOP
Apache + Cloudflare Tunnel Downtime SOP
Restoring website availability when the Apache and Cloudflare Tunnel path stops serving traffic.
  • Checks the service path from browser, Cloudflare, tunnel, and Apache layers.
  • Documents recovery commands, restart order, and validation steps.
  • Turns a real downtime fix into a reusable operations procedure.
Downtime Apache Cloudflare Tunnel Linux
Read SOP
OPS-002 · Coming Note
Service Health Check Runbook
A reusable checklist for validating web, DNS, tunnel, and host-level availability.
  • Standard checks for ports, processes, logs, and endpoint response.
  • Simple decision tree for local service vs. external routing problems.
  • Designed as a reusable first-response checklist.
Monitoring Runbook
Coming Soon
OPS-003 · Coming Note
DNS & Tunnel Troubleshooting
A practical note for separating DNS, proxy, certificate, and origin-server failures.
  • Layer-by-layer checks for name resolution and proxy status.
  • Validation path for tunnel service state and origin availability.
  • Clear documentation pattern for future incidents.
DNS Tunnel
Coming Soon
Documentation Pattern

How each operations note is structured

01
Symptom
Capture what users or monitoring would actually see: error page, timeout, failed tunnel, or service refusal.
02
Diagnosis
Check each layer in order, from public access through DNS/proxy to host services and logs.
03
Recovery
Document the exact corrective actions, restart sequence, and commands used to restore service.
04
Prevention
Record what should be monitored, automated, backed up, or improved to reduce repeat incidents.

More Practical Notes Coming

This operations library will grow alongside real troubleshooting work, with each note written to be useful, repeatable, and honest about what happened.