Fix headless browser HTTPS resolution for internal network addresses

GitHub issue #79 Feature Proposed skybrian2via discord Jan 4, 2026 View Discord message View GitHub mirror

Discord Message

Author: skybrian2 Channel: #feedback Link: https://discord.com/channels/1405685085923049482/1405686161791516873/1457522545329701015

Ran into a weird network issue. Shelly reports: "The headless browser inside the VM resolves exe.xyz to an internal IP (10.42.0.84) which doesn't have TLS. The exe.dev proxy only provides HTTPS when accessed from outside the network."

I'd like to have Shelly test via HTTPS so CORS will work. Maybe I'll set up another proxy somewhere else, but it would be nice if I didn't have to.

discord-bugshelley

1 Comment

skybrianvia github Jan 5, 2026

Shelly and I figured out a fun workaround: I deployed a simple http proxy on val.town that fetches from exe.dev. It required setting the VM share to public, though.