⚡ ~/naveed Interview Prep
⚡ Portfolio Home ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 998+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
Senior DevOps / SRE [L2] Linux Linux / SRE — Scenario-Based Interview Questions Production Scenario [L2]

Q: An application tries to bind to port 443 but fails with "Permission denied". The port is not in use. Why is this happening?

In Linux, ports below 1024 are considered "privileged ports." Only processes running as root can bind to them. For security reasons, web ...

#Linux #Linux / SRE — Scenario-Based Interview Questions #L2 #SRE #Systems #Troubleshooting
🎙️ Candidate Opening & Architectural Context
""In an interview, I explain my systematic Linux troubleshooting methodology using Brendan Gregg's USE method. The interviewer is testing: Linux privileged ports, setcap, port forwarding.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
Advertisement

🛠️ Production Runbook & Step-by-Step Resolution

1️⃣

Initial Diagnostics & Root Cause Analysis

In Linux, ports below 1024 are considered "privileged ports." Only processes running as root can bind to them. For security reasons, web servers and applications are typically run as non-root users.

  • Capabilities (Modern/Best Practice): Use setcap to grant the specific binary permission to bind to privileged ports: setcap 'cap_net_bind_service=+ep' /path/to/app.
  • Reverse Proxy: Run a reverse proxy like Nginx or HAProxy as root, bound to 443, and forward traffic to the app running on a high port (e.g., 8443) as a normal user.
  • iptables: Redirect traffic from port 443 to a high port: iptables -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT --to-port 8443.
2️⃣

Remediation & Permanent Safeguards

To fix this without running the application as root, there are three common approaches:

💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Capabilities (Modern/Best Practice): Use setcap to grant the specific binary permission to bind to privileged ports: setcap 'cap_n."
⚡ 60-Second Elevator Pitch Talking Points
  • Capabilities (Modern/Best Practice): Use setcap to grant the specific binary permission to bind t...
  • Reverse Proxy: Run a reverse proxy like Nginx or HAProxy as root, bound to 443, and forward traff...
  • iptables: Redirect traffic from port 443 to a high port: iptables -t nat -A PREROUTING -p tcp --d...
Advertisement
Want more Linux scenarios?
Explore our complete collection of scenario-based Linux interview runbooks.
Browse All Linux Questions →

📚 Related Production Scenarios in Linux