Trouble Setting Up Subdomain-Based Proxy Forwarding with Code-Server on Fly.io #7373
Unanswered
dev-tarala
asked this question in
General
Replies: 1 comment
-
As far as code-server is concerned, I can say that I am not familiar with fly.io though, so I am not sure what is going on there. If it has trouble with the CNAME maybe an A record on the wildcard host will work better? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm running
code-server
on a Fly.io VM using a custom Docker image. The image includes all necessary setup to launchcode-server
, and it works as expected on a direct root route.To enable per-port preview for services (e.g.,
3000
,5173
), I initially tried using code-server’s built-in proxy forwarding via/proxy/:port
. While this works locally to some extent, it fails on remote environments (Fly.io), particularly with module resolution and static asset loading in some frameworks (like older CRA apps). I explored workarounds (such as rewriting paths in nginx or using absproxy), but these were unreliable or framework-specific.As an alternative, I attempted to follow the code-server documentation for subdomain-based proxying. Here's what I did:
*.myapp.domain.com
)--proxy-domain
flag tocode-server
inside the VMHowever, I’m encountering persistent SSL handshake failures (
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
) and DNS resolution errors (e.g.,CNAME not resolving
or TLS alerts duringcurl
). The certificate verification step on Fly’s end also seems stuck due to failed domain ownership validation.I'd appreciate any guidance or clarification on:
--proxy-domain
with Fly.io and code-serverThanks in advance for your support!
Beta Was this translation helpful? Give feedback.
All reactions