Cloud Explainers

How to Fix Cloudflare Tunnel Errors in a Homelab

Homelab & self-hosting9 min video

Cloudflare Tunnel errors on a home server, fixed on real tunnels: a 502 Bad Gateway because cloudflared in Docker points at localhost, a 502 when the app is stopped (no such host), error 1033 when no cloudflared is connected (an old quick-tunnel address, no restart policy), a tunnel that runs but gives 1033 for almost two minutes because UDP 7844 is blocked, an x509 error from a NAS's self-signed certificate, and a named tunnel's missing catch-all rule.

Fine at home, 502 outside

Your site works on your own server, but through Cloudflare Tunnel it's a five oh two, Bad Gateway. Ana runs her board game club's site from a mini PC at home. On the server, curl gets the page: two hundred, fine. Ben, a club member, opens the tunnel's address from his laptop: five oh two. So the site is up, the tunnel is up, and nobody outside can see the site. Next: why, and the one-word fix. Then error ten thirty-three, and a tunnel that runs but still fails.

Ana's server, then Ben's laptop
curl -s -o /dev/null -w '%{http_code}\n' localhost:8080200
Ana's server, then Ben's laptop
curl -sI https://moments-yourself-led-relevance.trycloudflare.com | head -1HTTP/2 502

How a tunnel reaches your server

How does a tunnel reach a server at home at all? Ana's home router has no open ports. Instead, cloudflared, a small program on her server, calls out to Cloudflare and keeps that connection open: that's the tunnel. Ana runs both with Docker Compose, each in its own container. When Ben opens the address, Cloudflare sends his request down the tunnel, and cloudflared passes it to the site, at the address Ana typed into its settings: localhost, port eighty-eighty. Keep that in mind. The answer goes back the same way.

The tunnel is a call your server makes: diagram of Ben's laptop, Cloudflare, Home router, cloudflared, Club site, Ana's home

Think of a restaurant with no street door that takes orders through a delivery app. The kitchen keeps the app's tablet on, and every order arrives through it. Tablet off: the app says the restaurant is closed. Tablet on, but the order never reaches the cook: it fails.

A kitchen with no street door: comparison table of Delivery app vs Cloudflare Tunnel, Always on, Tablet off, Order lost inside

Read the tunnel's log

So, start with cloudflared's own log. Filtered down to its errors, it says: unable to reach the origin service. Origin is Cloudflare's word for your app. The last words say why: it tried localhost, port eighty-eighty, and the connection was refused. In the log, localhost is written colon colon one. Guess first: inside the tunnel's container, what is localhost? The tunnel container itself.

Ana on the club server
docker compose logs tunnel | grep -o 'error="[^"]*"' | tail -1error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp [::1]:8080: connect: connection refused"

Every container has its own localhost. The site's container listens on port eighty-eighty, and Compose also opens port eighty-eighty on the server itself and forwards it in, which is why curl on the server worked. But cloudflared runs in a container of its own: its localhost is itself, and nothing in there listens. On the network Compose makes, each service is reachable by its name. The site's name is site.

Every container has its own localhost: diagram of Ana's server, site container, cloudflared container, localhost:8080, club_default network

The fix: the service's name

So the fix is one word in compose dot yaml. The tunnel's URL, localhost, becomes site. The same goes for any app in Compose: point the tunnel at the service's name and the port inside its container.

Point the tunnel at the service's name: code change of ~/club/compose.yaml, command: tunnel --no-autoupdate --url http://site:8080 (the service's name, not localhost), Any Compose app: service name + its port

docker compose up dash d recreates the tunnel. A quick tunnel prints its public address in its log: here it is, but look: a different one. A quick tunnel gets a new address every time it starts; that matters in a minute. Ben opens the new address: two hundred.

Ana's server, then Ben's laptop
docker compose up -d Container club-tunnel-1  Recreate
 Container club-site-1  Running
 Container club-tunnel-1  Recreated
 Container club-tunnel-1  Starting
 Container club-tunnel-1  Started
Ana's server, then Ben's laptop
docker compose logs tunnel | grep -o 'https://[a-z-]*.trycloudflare.com' | tail -1https://grab-election-representatives-participation.trycloudflare.com
Ana's server, then Ben's laptop
curl -sI https://grab-election-representatives-participation.trycloudflare.com | head -1HTTP/2 200

And in his browser, the club's game nights, served from a mini PC in Ana's home, with no port open on her router.

The fix: the service's name: browser screenshot from the video

Two codes, two halves

So which part broke? The error code tells you. There are two halves to check. First, Cloudflare to cloudflared, the tunnel: if no cloudflared is connected, Cloudflare answers status five thirty, and its page says error ten thirty-three. Second, cloudflared to your app. If the tunnel is fine but that last step fails: five oh two. So always ask which half failed first.

Which half failed? The code tells you: diagram of Ben's laptop, Cloudflare, cloudflared, Club site, Ana's home server

Cloudflare's own page says the same. On Ben's first visit, the Bad gateway page showed his browser working, Cloudflare working, and the error at the host: Ana's end.

Two codes, two halves: browser screenshot from the video

When the app is down

A different five oh two. Ana stops the site, the way an update or a crash would. Ben gets five oh two again, but the log's last words changed: lookup site: no such host. A stopped container has no name on the network, so cloudflared can't even find it.

Ana's server, then Ben's laptop
docker compose stop site Container club-site-1  Stopping
 Container club-site-1  Stopped
Ana's server, then Ben's laptop
curl -sI https://grab-election-representatives-participation.trycloudflare.com | head -1HTTP/2 502
Ana's server, then Ben's laptop
docker compose logs tunnel | grep -o 'error="[^"]*"' | tail -1error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp: lookup site on 127.0.0.11:53: no such host"

So read the last words of the error. Connection refused: cloudflared found the place, and nothing listens there, like our localhost mistake. No such host: the name is wrong, misspelled, or the service isn't running. Ana starts the site again.

Same 502, different last words: comparison table of connection refused vs no such host, Means, Usual cause, Check

Error 1033: no tunnel connected

Now the other code. Ben still has the first address from this morning. He opens it: five thirty. In his browser: error ten thirty-three, Cloudflare Tunnel error. A quick tunnel gets a new random address every time cloudflared starts, so nothing is connected behind the old one any more. The tablet that took those orders is gone.

Error 1033: no tunnel connected: browser screenshot from the video

The same code comes after a reboot. Ana restarts Docker, which does to containers what a reboot does. Both containers have stopped, and nothing starts them again, so today's address gives Ben five thirty too.

Ana's server, then Ben's laptop
sudo systemctl restart docker[sudo] password for ana:
Ana's server, then Ben's laptop
docker compose ps -a --format 'table {{.Service}}\t{{.Status}}'SERVICE   STATUS
site      Exited (137) 3 seconds ago
tunnel    Exited (0) 13 seconds ago
Ana's server, then Ben's laptop
curl -sI https://grab-election-representatives-participation.trycloudflare.com | head -1HTTP/2 530

The fix is one line per service: restart, unless stopped: start it whenever Docker starts, unless you stopped it yourself. Docker restarts again, and this time both come back up by themselves. A quick tunnel still comes back with a new address, though. For an address that stays, use a named tunnel: one you create once in a free Cloudflare account, on your own domain. It shows these same errors.

Ana on the club server
grep -n restart compose.yaml9:    restart: unless-stopped
14:    restart: unless-stopped
Ana on the club server
docker compose up -d Container club-site-1  Recreate
 Container club-tunnel-1  Recreate
 Container club-tunnel-1  Recreated
 Container club-site-1  Recreated
 Container club-tunnel-1  Starting
 Container club-site-1  Starting
 Container club-tunnel-1  Started
 Container club-site-1  Started
Ana on the club server
sudo systemctl restart docker
Ana on the club server
docker compose ps -a --format 'table {{.Service}}\t{{.Status}}'SERVICE   STATUS
site      Up 4 seconds
tunnel    Up 4 seconds
Ana on the club server
docker compose logs tunnel | grep -o 'https://[a-z-]*.trycloudflare.com' | tail -1https://parking-husband-positions-paso.trycloudflare.com

Running, and still 1033

Now the tunnel that runs and still fails. Data crosses the internet in two main ways, TCP and UDP, and some strict routers block UDP. cloudflared prefers a protocol called QUIC, which travels over UDP to port seventy-eight forty-four. Ana copies such a router with one firewall rule that drops it. She recreates the tunnel. It's up. Ben gets five thirty, the status behind error ten thirty-three.

Ana's server, then Ben's laptop
sudo iptables -I DOCKER-USER -p udp --dport 7844 -j DROP
Ana's server, then Ben's laptop
docker compose up -d --force-recreate tunnel Container club-tunnel-1  Recreate
 Container club-tunnel-1  Recreated
 Container club-tunnel-1  Starting
 Container club-tunnel-1  Started
Ana's server, then Ben's laptop
docker compose ps --format 'table {{.Service}}\t{{.Status}}'SERVICE   STATUS
site      Up About a minute
tunnel    Up 15 seconds
Ana's server, then Ben's laptop
curl -sI https://intranet-hope-bias-recognised.trycloudflare.com | head -1HTTP/2 530

The log explains. At start, cloudflared's own check says: UDP failed, and it will use HTTP/2, which runs over TCP instead. Then it tries QUIC anyway, again and again: failed to dial to edge with quic; the edge is Cloudflare's servers. Guess first: how long until Ben's page loads? 138 seconds, when it finally switches to HTTP/2.

Ana on the club server
docker compose logs --no-log-prefix tunnel | grep -E '[|]  (UDP|SUMMARY)' | cut -c 26-|  UDP Connectivity  region1.v2.argotunnel.com  FAIL    QUIC connection failed                  |
|  UDP Connectivity  region2.v2.argotunnel.com  FAIL    QUIC connection failed                  |
|  SUMMARY: Environment ready with degraded transport. cloudflared will proceed using 'http2'.  |
Ana on the club server
docker compose logs tunnel | grep -o 'error="[^"]*"' | tail -1error="failed to dial to edge with quic: timeout: no recent network activity"
Ana on the club server
docker compose logs --no-log-prefix tunnel | grep -E 'Switching|Registered' | sed -E 's/^.{11}//; s/ (connIndex|connection|event|ip|location)=[^ ]+//g'14:01:41Z INF Switching to fallback protocol http2
14:01:41Z INF Registered tunnel connection protocol=http2

So don't wait for it to give up. The flag protocol, set to HTTP/2, tells cloudflared to use TCP from the start, and it connects in 6 seconds. If your router allows it, opening outgoing UDP to port seventy-eight forty-four works too.

Ana on the club server
grep -n protocol compose.yaml13:    command: tunnel --no-autoupdate --protocol http2 --url http://site:8080
Ana on the club server
docker compose up -d Container club-site-1  Running
 Container club-tunnel-1  Recreate
 Container club-tunnel-1  Recreated
 Container club-tunnel-1  Starting
 Container club-tunnel-1  Started
Ana on the club server
docker compose logs --no-log-prefix tunnel | grep -E 'Initial protocol|Registered' | sed -E 's/^.{11}//; s/ (connIndex|connection|event|ip|location)=[^ ]+//g'14:01:47Z INF Initial protocol http2
14:01:47Z INF Registered tunnel connection protocol=http2

A NAS on HTTPS

If you put a NAS behind a tunnel, you'll probably hit this next five oh two. The club has a photo NAS. Like most NAS boxes, it serves its page over HTTPS, with a certificate it made for itself. Ana points a second tunnel at that HTTPS address. Five oh two again, and the last words: X five oh nine, certificate signed by unknown authority.

Ana's server, then Ben's laptop
docker compose up -d Container club-nas-tunnel-1  Creating
 Container club-tunnel-1  Running
 Container club-nas-1  Creating
 Container club-site-1  Running
 Container club-nas-tunnel-1  Created
 Container club-nas-1  Created
 Container club-nas-1  Starting
 Container club-nas-tunnel-1  Starting
 Container club-nas-tunnel-1  Started
 Container club-nas-1  Started
Ana's server, then Ben's laptop
curl -sI https://mlb-site-peers-predict.trycloudflare.com | head -1HTTP/2 502
Ana's server, then Ben's laptop
docker compose logs nas-tunnel | grep -o 'error="[^"]*"' | tail -1error="failed to proxy HTTP: Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: tls: failed to verify certificate: x509: certificate signed by unknown authority"

cloudflared checks the NAS's certificate the way a browser would, and nobody it trusts signed it. Dash dash no TLS verify tells it to accept the certificate: two hundred. The only hop left unchecked is the one inside Ana's server; Ben's connection to Cloudflare is checked as always. With a named tunnel, you can instead tell it which certificate to trust.

Ana's server, then Ben's laptop
grep -n tls compose.yaml25:    command: tunnel --no-autoupdate --protocol http2 --no-tls-verify --url https://nas:443
Ana's server, then Ben's laptop
docker compose up -d Container club-tunnel-1  Running
 Container club-nas-1  Running
 Container club-nas-tunnel-1  Recreate
 Container club-site-1  Running
 Container club-nas-tunnel-1  Recreated
 Container club-nas-tunnel-1  Starting
 Container club-nas-tunnel-1  Started
Ana's server, then Ben's laptop
curl -sI https://aus-release-set-sizes.trycloudflare.com | head -1HTTP/2 200

A named tunnel's rules

With a named tunnel, one typo in a hostname sends your visitors a four oh four. Here's how to catch it first. A named tunnel often reads a config file: rules that say which hostname goes to which service. Here cloudflared runs on the server itself, installed as a package, so localhost is right this time. cloudflared tunnel ingress validate checks the file without connecting. On Ana's file it fails: the last rule must match all URLs.

Ana on the club server
cat .cloudflared/config.ymltunnel: 6ff42ae2-765d-4adf-8112-31c55c1551ef
credentials-file: /home/ana/.cloudflared/6ff42ae2-765d-4adf-8112-31c55c1551ef.json

ingress:
  - hostname: games.example.com
    service: http://localhost:8080
  - hostname: photos.example.com
    service: https://localhost:8443
    originRequest:
      noTLSVerify: true
Ana on the club server
cloudflared tunnel ingress validateValidating rules from  /home/ana/.cloudflared/config.yml
Validation failed: The last ingress rule must match all URLs (i.e. it should not have a hostname or path filter)

So every file ends with a catch-all rule, for any address no other rule names. Add one that answers four oh four, and the file is OK. Then ingress rule tests an address. Game dot example dot com, one letter short, falls through to the catch-all, rule number two, so a visitor gets a four oh four. The right name, games dot example dot com, matches rule zero, the first rule: the site.

Ana on the club server
tail -1 .cloudflared/config.yml  - service: http_status:404
Ana on the club server
cloudflared tunnel ingress validateValidating rules from  /home/ana/.cloudflared/config.yml
OK
Ana on the club server
cloudflared tunnel ingress rule https://game.example.comUsing rules from /home/ana/.cloudflared/config.yml
Matched rule #2
	service: http_status:404
Ana on the club server
cloudflared tunnel ingress rule https://games.example.comUsing rules from /home/ana/.cloudflared/config.yml
Matched rule #0
	hostname: games.example.com
	service: http://localhost:8080

Recap

So, start with the code. Error ten thirty-three: no tunnel connected; is cloudflared running and reaching Cloudflare? Five oh two: read the log's last words. Four oh four: check the rules.

Cloudflare Tunnel errors: start with the code: diagram of 530 / error 1033, 502 Bad Gateway, 404

If Ben can see the game nights now, a like helps another homelabber find this, and subscribing brings more fixes, tested on real machines.

Every error in this video came from real Cloudflare tunnels to a real Ubuntu server, and every command and the lab files are linked in the description. Thanks for watching Cloud Explainers.

Sources

Demos: two containers on our own Mac standing in for a home server and a club member's laptop, with real Cloudflare quick tunnels (no account); the club and its members are made up. Every error page, status code and log line was real. Watch the full video on YouTube.

More videos

Python8 min

How to Fix Python ModuleNotFoundError: No Module Named

Go (Golang)5 min

Golang Pointers in 5 Minutes

Kubernetes8 min

How to Fix a Kubernetes Pod Stuck in CrashLoopBackOff

Homelab & self-hosting9 min

How to Fix a Homelab ESXi Host Not Responding

PostgreSQL24 min

PostgreSQL: Full Tutorial for Beginners

Load balancing & Nginx9 min

How a Load Balancer Works with HAProxy

Python9 min

How Python Virtual Environments Work

APIs9 min

How to Fix API CORS Errors: No 'Access-Control-Allow-Origin'

Auth (OAuth, JWT)9 min

How Authenticator App Login Codes Work (TOTP)

Git22 min

Git and GitHub: Full Tutorial for Beginners

Homelab & self-hosting10 min

How a Homelab Hypervisor Works (VMware ESXi)

Kubernetes9 min

How to Fix Kubernetes ImagePullBackOff Errors

DNS8 min

How to Fix DNS 'Temporary Failure in Name Resolution' on Linux

AWS8 min

How to Fix AWS CLI 'Unable to Locate Credentials'

Homelab & self-hosting10 min

Proxmox vs ESXi for Your Homelab: When Each One Wins

PostgreSQL10 min

PostgreSQL UUID vs Auto Increment: Which Primary Key Should You Use?

Kubernetes21 min

Kubernetes: Full Tutorial for Beginners

Networking9 min

How TCP Sockets Work

PostgreSQL7 min

How to Fix PostgreSQL 'Could Not Connect to Server'

Claude & the Claude Developer Platform9 min

Claude Code Hooks Will Finally Make Sense After This

DevOps & CI/CD9 min

DevOps with Ansible Will Finally Make Sense After This

Networking9 min

How SNMP Network Monitoring Works

Git8 min

How to Fix GitHub 'Permission Denied (publickey)' Errors

Docker21 min

Docker: Full Tutorial for Beginners

PostgreSQL7 min

How to Fix PostgreSQL 'Password Authentication Failed'

Linux8 min

Why One Linux Server Handles More Users Than You Think

Networking7 min

How to Fix Network 'Connection Refused' Errors

DevOps & CI/CD9 min

DevOps Pipelines: Jenkins vs GitHub Actions

Linux11 min

Linux Nginx Reverse Proxy: Full Tutorial for Beginners

Networking11 min

Every Networking Term a Beginner Needs in 12 Minutes

Docker6 min

How to Fix Docker 'Permission Denied' on docker.sock

Git7 min

How to Fix Git 'Updates Were Rejected' When You Push

Linux7 min

How to Fix nginx 502 Bad Gateway Errors on Linux

Linux8 min

How to Fix Linux apt 'Could Not Get Lock' Errors (Ubuntu)

Networking9 min

How Email Works on the Internet (SMTP) in 10 Minutes

Python8 min

The Python Roadmap for Beginners

Go (Golang)21 min

Golang REST API with Gin: Full Tutorial for Beginners

Networking10 min

How a WireGuard VPN Network Works

Linux9 min

Linux Makefiles Will Finally Make Sense After This

Auth (OAuth, JWT)9 min

SAML vs OAuth vs OpenID Connect: What's the Difference?

Python7 min

How to Fix Python cron Jobs That Never Run

Linux22 min

Linux Bash Scripting: Full Tutorial for Beginners

Networking10 min

How PXE Network Boot Works

Active Directory9 min

How Active Directory Works

Linux10 min

How to Fix a Linux systemd Service That Won't Start

Linux9 min

Linux Logs: syslog vs journald

Auth (OAuth, JWT)9 min

JWT vs Session Cookies: Which One Should You Use?

Docker10 min

Docker vs Docker Compose: Which One Should You Use?

Docker9 min

How to Fix Docker Compose Containers That Can't Talk to Each Other

Django (Python web framework)22 min

Django Full Tutorial for Beginners

Linux9 min

How Linux systemd Works

Networking8 min

How to Fix 'Windows Cannot Access' Network Share Errors (SMB)

APIs10 min

REST vs gRPC: Which One Should You Use?

Certificates & PKI (ADCS)9 min

How to Fix SSL Certificate Chain Errors (Missing Intermediate)

Python9 min

Every Python Concept for Beginners in 10 Minutes

Databases & SQL9 min

Every SQL Join Type in 10 Minutes

OpenRouter (one API for many AI models)9 min

Why OpenRouter Free Models Hit Their Limit So Fast

Gemini API & Google AI Studio9 min

Why Your Gemini API Free Tier Runs Out So Fast

OpenRouter (one API for many AI models)10 min

OpenRouter Will Finally Make Sense After This

Caching & Redis10 min

How Redis Caching Works

Gemini API & Google AI Studio10 min

Gemini API vs Vertex AI: Which One Should You Use?

Gemini API & Google AI Studio8 min

How to Fix a Leaked Gemini API Key

Go (Golang)9 min

Why Golang Uses Goroutines Instead of Threads

Gemini API & Google AI Studio9 min

How to Fix Gemini API Error 429: Resource Exhausted

Claude & the Claude Developer Platform10 min

Claude Token Pricing Will Finally Make Sense After This

Python11 min

Why Python Web Scraping Returns Nothing (and the Fix)

Python10 min

Python uv vs pip: Which One Should You Use?

Python22 min

Python Automation: Full Tutorial for Beginners

Auth (OAuth, JWT)9 min

How OAuth Login Works

Gemini API & Google AI Studio10 min

Google AI Studio Will Finally Make Sense After This

Docker10 min

What Happens When You Run a Docker Container

Claude & the Claude Developer Platform8 min

How to Fix Claude Code Billing Your API Key Instead of Your Plan

Auth (OAuth, JWT)9 min

Why Passkeys Can't Be Phished Like Passwords

PowerShell10 min

PowerShell vs Bash: Which One Should You Learn?

Linux10 min

The Linux Roadmap for Beginners

Django (Python web framework)9 min

Django vs FastAPI: Which One Should You Use?

Databases & SQL10 min

Why SQLite Is the Most Used Database in the World

Databases & SQL11 min

How a NoSQL Database Like MongoDB Works

Python11 min

How to Fix Python pip error: externally-managed-environment

Databases & SQL9 min

How to Fix MySQL Too Many Connections Database Errors

Go (Golang)9 min

Golang Concurrency Will Finally Make Sense After This

AWS10 min

How Amazon S3 Works

Kubernetes10 min

How Kubernetes Works

Git10 min

How Git Works

Docker10 min

How to Fix Docker Port Already Allocated Errors

PostgreSQL10 min

How PostgreSQL Works

Git8 min

How to Fix Git Merge Conflicts

Linux9 min

How to Fix No Space Left on Device in Linux

Networking10 min

How the Internet Works

Databases & SQL9 min

SQL vs NoSQL: When Each One Wins

Auth (OAuth, JWT)8 min

How to Fix JWT Token Expired Errors (401 Unauthorized)

Claude & the Claude Developer Platform9 min

Claude API vs Claude Pro: Why Your Subscription Doesn't Include It

AI agent skills9 min

Why AI Agent Skills Beat Giant Prompts

Linux10 min

Linux Cron Jobs Will Finally Make Sense After This

Cybersecurity10 min

Security Logs Will Finally Make Sense After This

Cybersecurity8 min

How to Fix a Security Leak: An API Key Pushed to GitHub

DNS9 min

DNS Will Finally Make Sense After This

Cybersecurity9 min

Never Ignore a Security Update

Auth (OAuth, JWT)9 min

Two-Factor Authentication Will Finally Make Sense

Networking8 min

Never Expose a Database to the Internet

Cybersecurity10 min

SSH Keys vs Passwords: Which Is Safer for Security?

Linux10 min

The 5 Levels of Linux Boot: From Power On to Login

Networking12 min

The 5 Levels of Network Firewalls

Cybersecurity10 min

Password Security: Why Hackers Crack Weak Passwords

Linux9 min

Why Your Linux Server Runs Out of Memory

Networking10 min

HTTP vs HTTPS: What Actually Changes on Your Network

Linux12 min

Every Linux File Permission You Need to Know

Linux10 min

Linux Processes vs Threads: When Each One Wins

Networking11 min

The OSI Model Will Finally Make Sense After This

Git11 min

The 7 Levels of Git

Networking10 min

Every Network Troubleshooting Command You Need

Cybersecurity10 min

Hashing vs Encryption in Cybersecurity: When Each One Wins

Networking11 min

Why the Internet Ran Out of IP Addresses

Linux11 min

Linux Package Managers: apt vs Snap vs Flatpak

Python9 min

Why Python Is Slow (and When It Doesn't Matter)

Networking11 min

TCP vs UDP: When Each One Wins

Linux8 min

Stop Running Linux as Root (Do This Instead)

Linux11 min

Linux Users and Groups Will Finally Make Sense

Cybersecurity9 min

Why Phishing Beats Good Security (and How to Spot It)

Docker12 min

The 7 Levels of Docker

AI agents & MCP12 min

AI Agents Will Finally Make Sense After This

Git8 min

Stop Using git push --force (Use This Instead)

AI agent skills10 min

Agent Skills vs MCP: When Each One Wins

Networking12 min

Networking Will Finally Make Sense After This

Linux12 min

Every Linux Command You Actually Need

Cybersecurity12 min

The 7 Levels of Cybersecurity

System design12 min

Every System Design Concept You Need, in One Diagram

PostgreSQL10 min

Why PostgreSQL Ignores Your Index