<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Homelab on Companionway</title>
		<link>https://www.companionway.net/categories/homelab/</link>
		<description>Recent content in Homelab on Companionway</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Mon, 19 Oct 2026 10:00:00 -0400</lastBuildDate>
		
			<atom:link href="https://www.companionway.net/categories/homelab/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Bypassing Port 80 and 443: How a Tunnel Agent Gets Around Port-Forwarding  Challenges</title>
				<link>https://www.companionway.net/post/bypassing-router-ports-with-cloudflare-tunnels/</link>
				<pubDate>Mon, 19 Oct 2026 10:00:00 -0400</pubDate>
				<guid>https://www.companionway.net/post/bypassing-router-ports-with-cloudflare-tunnels/</guid>
				<description>&lt;h1 id=&#34;-how-i-bypassed-my-routers-port-lockout-to-host-a-secure-home-server-for-free&#34;&gt;🌐 How I Bypassed My Router&amp;rsquo;s Port Lockout to Host a Secure Home Server for Free&lt;/h1&gt;&#xA;&lt;p&gt;If you have ever tried to host a web server or self-hosted app from your home network, you have probably hit a brick wall known as &amp;ldquo;port hijacking.&amp;rdquo; 🚧&lt;/p&gt;&#xA;&lt;p&gt;Many consumer ISP routers reserve standard HTTP (port 80) and HTTPS (port 443) ports for their own internal administrative interfaces or remote management systems. 🔒 Because the router locks these ports down at the hardware level, you cannot forward inbound web traffic on ports 80 or 443 to a local machine on your private network.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
