Using custom domains without issuing certificates

I dont mind the warnings/no-HTTPS, but i would like to have custom domains pointed to my server without deploying a certificate for each one

Hi,

If a request arrives for your-app-name.fly.dev Fly knows which app to route that to. But … if a request arrives for your-custom-domain.com … how would Fly know which app to route that to? By default apps are given a shared IP. That IP might be shared with X other apps, Currently by adding the certificate, that associates the domain with the app. Then it does know.

I wonder (not tried this so it’s a total guess) whether if you were to allocate a dedicated IP to the app, whether that would be enough :thinking: Since that way the IP is linked to the app 1:1. You may need to bypass Fly’s proxy for that to work, with TCP passthrough. No idea. Would need someone from Fly to confirm. For more:

Thanks for the reply! That makes a ton of sense - I’ll try out dedicated IPs.

1 Like

I’ve been using a dedicated IP and it gets routed correctly. The documentation here has some information about it.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.