3 ms·
I'm struggling to deploy a basic docker application, that works fine on my machine, it handles https traffic by its self, so the Fly.io docs say to exclude serv
by Jamie9912 5y ago
I'm struggling to deploy a basic docker application, that works fine on my machine, it handles https traffic by its self, so the Fly.io docs say to exclude services.ports in fly.toml and TCP will be passed-on as-is, but unfortunately it seems to still be messing with my TCP traffic, maybe because it's on a non-standard port
- mrkurt 5y agoYou'll need [services] to accept public TCP traffic, just set `handlers = []` to turn off our TLS and HTTP layers. We do run a proxy so we definitely mess with your TCP traffic! You can enable PROXY protocol to get some of the original connection info (ip, port, etc): https://fly.io/docs/reference/services/#proxy-protocol https://fly.io/docs/reference/services/#proxy-protocol
- Jamie9912 5y agoYup i've tried that but sadly the curl command that works on my machine fails with `curl: (35) error:0A000126:SSL routines::unexpected eof while reading` on fly.io Locally I run with docker run -p 8888:8888, so I assume the correct thing to do when deploying on fly is to build the image with EXPOSE 8888 in the docker file, and set the service internal_port = 8888 in fly.toml. Have I assumed this correctly?
- mrkurt 5y agoYou do need the internal_port, you don't need `EXPOSE` though. Will you post your config file at https://community.fly.io https://community.fly.io so we can have a closer look?