Which VPN Works for GitHub Codespaces Connection Error 504 on Hotel Wi-Fi?

You are sitting at a hotel desk late in the evening trying to push a quick patch before your morning sprint standup. You open VS Code, click into the GitHub Codespaces extension, and hit your active workspace.

The status bar at the bottom left begins its familiar rhythm: "Opening Remote...", "Starting the container...", "Setting up SSH tunnel...".

And then it just sits there.

Forty-five seconds later, the prompt gives up and dumps a toast notification in the corner: `504 Gateway Timeout` or `Failed to connect to the remote extension host server`. You switch over to the browser client on github.dev, and the web editor spins endlessly before timing out at the WebSocket handshake.

The immediate reaction is to curse the hotel Wi-Fi. But when you run a speed test, the needle jumps to 80 Mbps down. Documentation pages load instantly, your company Slack is updating without delay, and video calls run fine. Yet your dev environment refuses to establish a stable container bridge.

The failure is not caused by weak broadband. It is happening at the intersection of hotel traffic management rules and Microsoft's front-door edge security.

### Why Hotel Wi-Fi Triggers a 504 on Codespaces

A 504 Gateway Timeout is an HTTP status code indicating that an intermediary gateway or proxy did not receive a timely response from an upstream server.

When you connect local VS Code to GitHub Codespaces, you are not simply downloading static assets. The client establishes a continuous, bidirectional WebSocket over HTTPS/WSS (or a tunneled SSH pipe) back to GitHub’s regional container relays hosted on Azure infrastructure.

When you do this over a hospitality network, two specific network friction points break the handshake:

1. Aggressive State-Table Flushes on Hotel Middleboxes: Hotel routers and captive-portal gateways (such as Nomadix or Mikrotik appliances) are configured to support hundreds of transient guests. To keep memory tables clear, they aggressively prune long-lived, silent TCP connections. If the initial setup handshake encounters even a slight delay while container extensions spin up, the hotel firewall silently resets the port or drops the return packet, leaving the upstream gateway waiting until it returns a 504.

1. Noisy Neighbor IP Deprioritization on Microsoft Edge: All guests in a hotel share a single public IPv4 egress address. If someone in room 304 is running torrents or a malware-infected machine is spraying port scans, the entire hotel IP gets flagged in threat reputation feeds. When your client tries to open an authenticated, high-privilege WebSocket into Azure's container edge, Microsoft’s automated front doors impose connection throttling or slow-walk the handshake.

When developers encounter this, their first instinct is to turn on whatever commercial VPN they already have installed on their laptop.

Surprisingly, that often makes the 504 errors worse.

### The Pitfall of Shared VPN Pools for Developer Tooling

The majority of commercial VPNs operate on large, shared IP pools. When you click "Quick Connect," you are dumped onto a data center exit node alongside hundreds of random users.

That shared architecture creates the exact same problem you were trying to escape on hotel Wi-Fi:

- Shared-IP Abuse Flags: Commercial VPN subnets from hosting giants like M247 or Datacamp are constantly scraped and monitored. Microsoft and GitHub actively rate-limit suspicious API requests originating from dirty public data center ranges to stop bot activity.

- Intermediate Reverse-Proxy Stalls: If the VPN server’s upstream routing experiences high packet jitter, the WebSocket handshake between your local VS Code client and the Codespaces relay daemon times out before the handshake acknowledgment completes.

- Inconsistent Session Hops: Consumer VPNs frequently balance load by bouncing your connection between multiple egress nodes. If your IP address shifts while Codespaces is negotiating tunnel authorization, the session token is invalidated immediately.

If you are going to use a VPN to resolve remote development timeouts, the selection criteria must change completely.

### The Real Fix: Dedicated IP Architecture vs. Shared Pools

To get a persistent, uninterrupted link into GitHub Codespaces from a managed public network, your connection needs to solve two technical problems:

First, it must shield your packets from the hotel router’s aggressive TCP connection killing by encapsulating all traffic inside a clean, single-port tunnel (typically TLS over port 443). To the hotel gateway, your entire development session looks like standard web browsing, completely bypassing protocol-specific throttling.

Second, it must present a clean, consistent IP identity to Microsoft’s infrastructure. This is where choosing between a shared pool and a dedicated IP makes all the difference:

A dedicated IP address belongs solely to you. It does not carry the baggage of stranger traffic, web scraping bans, or compromised reputations. When your VS Code client makes continuous upstream API calls and opens persistent WebSockets to remote virtual machines, Azure’s edge proxies see an unflagged, stable business connection rather than a noisy public proxy. Handshakes complete on the first pass, eliminating the gateway delays that cause 504 timeouts.

### Where ONLYDOGSVPN Fits into Remote Development

ONLYDOGSVPN provides clean network routing designed for environments where standard tunnels get clamped or rate-limited:

- Dedicated Static IP Allocations: You can bind your connection to an exclusive static IP address. Because the IP is not recycled among high-volume consumer traffic, your connection profile remains trusted by developer platforms, avoiding the automated CAPTCHA challenges and connection drops common to shared commercial nodes.

- Unencumbered Transit to Cloud Hubs: Nodes are built on optimized transit links connected directly to major internet exchanges. Minimizing the intermediate hops between your hotel room and Azure/GitHub data centers lowers round-trip latency and prevents packet dropouts during extension synchronization.

- Low-Overhead Tunneling: The client utilizes modern, streamlined tunneling protocols that reduce packet header bloat. This keeps WebSocket connections alive even over patchy Wi-Fi with minor packet jitter, preventing unexpected extension host disconnects midway through your coding session.

### When a VPN Will Not Fix Your 504 Error

It is important to be realistic about what network routing can and cannot solve:

If the Codespace container itself has genuinely hung—such as an out-of-memory error caused by a run-away Node.js process, a corrupted Docker daemon inside the devcontainer, or a crashed remote extension host—changing your internet path will not bring it back. If the machine status on `[github.com/codespaces](https://github.com/codespaces)` shows a failure state, you need to rebuild the container or restart it from the web dashboard.

Similarly, if the hotel Wi-Fi is suffering from severe local radio interference (such as 30% packet loss between your laptop and the hallway access point), no VPN can synthesize missing radio packets. If local ping tests to your default gateway show wild spikes and drops, switching to a 5G phone tether is your necessary first step.

### Practical Steps to Restore Your Codespaces Connection

If you are stuck on a 504 timeout and need to get back into your code immediately:

1. Open your terminal and run a quick ping test to your local gateway to ensure your radio connection to the hotel access point is stable without local dropouts.

1. Open your browser, navigate to your GitHub Codespaces dashboard, and verify that your target workspace shows as "Active" or "Available" rather than "Rebuilding."

1. Launch your VPN using a dedicated IP node situated in the same geographic region as your Codespace container (typically US East, US West, or Europe West) to keep routing hops minimal.

1. Return to VS Code, run `Codespaces: Rebuild Container` or re-initiate the connection to your remote container.

Once your connection route stops tripping hotel packet filters and presents a clean, unthrottled endpoint to Microsoft’s edge, your remote environment connects cleanly on the first try, letting you finish your work without fighting the network.