Anyone successfully migrate to fly from Gigalixir using Master Proxy?

Questions / Help
1

I’ve had no trouble deploying Gigalixir apps to fly until recently when I decided to migrate our mono repo that is using Master Proxy/Main Proxy (which allows you to run multiple routers/apps with different ports under a single elixir phx app)

The current blocker is that when I deploy with several “services” in my toml (under a single http service) I get a message like you see below. Has anyone migrated with a more complex networking stack like this? Any pro-tips to get me moving?

Here is my fly.toml file for reference

Here is the endpoint configs I have in runtime.exs

config :master_proxy,
url: [host: host, port: 443, scheme: “https”],
http: [ip: {0, 0, 0, 0, 0, 0, 0, 0}, port: port]

config :app, AppOneEndpoint,
url: [scheme: “https”, port: 443],
http: [ip: {0, 0, 0, 0, 0, 0, 0, 0}, port: 4001],
secret_key_base: secret_key_base

config :app, AppTwoEndpoint,
url: [scheme: “https”, port: 443],
http: [ip: {0, 0, 0, 0, 0, 0, 0, 0}, port: 4002],
secret_key_base: secret_key_base

WARNING The app is not listening on the expected address and will not be reachable by fly-proxy.
You can fix this by configuring your app to listen on the following addresses:

  • 0.0.0.0:4002 for job
  • 0.0.0.0:4004
  • 0.0.0.0:8080
  • 0.0.0.0:4001
  • 0.0.0.0:4003
    Found these processes inside the machine with open listening sockets:
    PROCESS
2

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