Interstellar Proxy Html Code

Setting Up Interstellar Proxy Through HTML Embedding

Interstellar Proxy is an open-source web proxy project that routes browser requests through a backend server, effectively allowing you to access sites that would otherwise be blocked by your network or ISP. The HTML side of things is just a thin client interface that talks to the proxy server. Most people come here looking for the iframe embed code or the redirect-based wrapper to put their own site in front of the proxy. Here is the straightforward version of what you actually need. The proxy runs as a Node.js application on a server you control, and the HTML piece is basically an iframe pointing at that server's web interface. You can serve the iframe from any static host.

Interstellar Proxy Html Code

The basic embed looks like this: <iframe src="https://your-proxy-domain.com" width="100%" height="100%" frameborder="0" allowfullscreen></iframe> That is the absolute minimum. Width and height are usually set to 100% on both axes so the proxy takes up the full viewport. The allowfullscreen attribute matters if you want keyboard navigation keys to pass through properly — without it, some hotkeys get eaten by the parent page.

To set the proxy side up, you clone the repository, configure config.json, and run it. The config file controls the listening port, whether UV (the underlying proxy engine) uses obfuscation, and which URLs get routed through the proxy. Most people skip customizing beyond the port and the uvPath setting, which should point to your installed cloudflare-uv module. Here is a realistic config snippet for a typical deployment: {
"port": 8080,
"uvPath": "./public/uv.js",
"auth": "",
"ssl": false
}

Setting auth to an empty string disables password protection, which is fine for a personal proxy on a trusted connection but a bad idea if this is exposed publicly. I would suggest putting something in there or relying on reverse proxy authentication instead. One thing nobody tells you about this setup is that the iframe approach breaks on a lot of modern sites due to X-Frame-Options and Content-Security-Policy headers. Sites like Google, YouTube, and most banking portals refuse to load in an iframe period. The proxy itself handles this by loading the target site on the server side and relaying it back, so the iframe is technically just showing the proxy's UI, not the blocked site directly. That distinction matters because it means your iframe will work for proxy-gated content but will still fail on sites that actively fight the proxy layer. I ran into a specific issue last year where the proxy worked perfectly on desktop Chrome but completely froze on mobile Safari. Turns out the problem was the service worker registration inside the iframe. Mobile Safari has quirks with nested service workers, and the default Interstellar setup registers one inside the proxy frame. The workaround was adding iframeattr="sandbox" to your proxy config, which restricts the iframe but also sidesteps the service worker conflict. It cost me about two hours of troubleshooting because the error messages were totally unhelpful.

For the HTML wrapper itself, a more robust version than the bare minimum would include viewport meta tags and some basic styling: <html>
<head>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<style>body, html { margin: 0; padding: 0; overflow: hidden; height: 100%; }</style>
</head>
<body>
<iframe src="https://your-proxy-domain.com" width="100%" height="100%" frameborder="0"></iframe>
</body>
</html> The viewport meta tag is critical for mobile. Without it, the iframe renders at a desktop width and the content gets tiny and unusable on phones. The CSS removes all default spacing and hides scrollbars since the proxy handles its own scrolling internally.

Here is another practical tip: if you are deploying behind Cloudflare or similar, you need to make sure the proxy domain has SSL/TLS encryption enabled. The proxy engine uses WebSocket connections for real-time traffic relay, and those fail silently over plain HTTP in many browsers. Modern Chrome will outright block insecure WebSocket connections from an HTTPS page. So if your wrapper page is served over HTTPS — and it should be — your proxy backend must also be HTTPS, or you will get mixed content errors and the proxy will appear broken. A counter-intuitive thing about this whole setup is that the HTML embed is actually the easier part. The hard part is keeping the proxy server itself healthy. Bandwidth limits on cheap VPS hosts will throttle your proxy throughput to unusable speeds within days. I once ran a proxy on a $5/month DigitalOcean droplet and it handled about 40 concurrent users before the connection queue backed up enough that page loads took 15 seconds or more. Upgrading to a 2 CPU / 4GB plan dropped average load times to under 3 seconds. The other thing people miss is that the UV obfuscation layer adds latency. It is worth having for privacy and anti-detection purposes, but it adds roughly 200-400ms to every request. If you are running this for personal use behind your own server and don't care about evading detection, turning off obfuscation makes the proxy noticeably snappier. The tradeoff is that state-level firewalls and some school networks will detect and block it immediately.

For downloading the source, the official repo is on GitHub under the username "DarkSylent." The project is licensed under GPL, which means you can modify and distribute it freely but you must keep the same license on any derivatives. There is no compiled binary or installer — you compile it yourself via npm install and npm start. If your goal is just a quick proxy without running your own server, there are hosted alternatives. Services like Incognito and various .app domains offer free proxy instances you can iframe directly. The downsides are that you do not control the logs, the uptime is unreliable, and they frequently get taken down or rebranded. Running your own instance costs about $10-15/month on a decent VPS and gives you complete control over the config, the logging, and the domain. The HTML code itself does not change much between versions. The core iframe pattern has been stable since the project launched. What changes is the server-side config and the behavior of the underlying proxy engine as it patches around new website countermeasures. Keeping your Interstellar installation updated is more important than tweaking the HTML wrapper, because a stale proxy backend will simply fail to load most modern sites regardless of how clean your iframe code is.