Ash FrameworkAF
Ash Framework•7mo ago•
9 replies
coderberry

Port conflict when running new app built using Ash installer

I used the Ash installer to generate a new app:

mix archive.install hex igniter_new --force
mix archive.install hex phx_new 1.8.0-rc.3 --force

mix igniter.new agentheon --with phx.new --install ash,ash_phoenix \
  --install ash_json_api,ash_postgres \
  --install ash_authentication,ash_authentication_phoenix \
  --install ash_admin,ash_oban --install oban_web,live_debugger \
  --install mishka_chelekom,tidewave --install ash_ai,beacon \
  --install beacon_live_admin --auth-strategy password \
  --auth-strategy magic_link --auth-strategy api_key --beacon.site cms \
  --beacon-live-admin.path /cms/admin --yes

cd agentheon && mix ash.setup


Once installed, I ran mix phx.server and got the following error (see attached error logs).

➜  agentheon mix phx.server
...
[info] Running AgentheonWeb.Endpoint with Bandit 1.7.0 at 127.0.0.1:4000 (http)
[info] Access AgentheonWeb.Endpoint at http://localhost:4000
[info] Running AgentheonWeb.CmsEndpoint with Bandit 1.7.0 at 127.0.0.1:4654 (http)
[info] Access AgentheonWeb.CmsEndpoint at http://localhost:4654
[watch] build finished, watching for changes...
[error] Running AgentheonWeb.ProxyEndpoint with Bandit 1.7.0 at http failed, port 4000 already in use
[notice] Application agentheon exited: Agentheon.Application.start(:normal, []) returned an error: shutdown: failed to start child: AgentheonWeb.ProxyEndpoint
    ** (EXIT) shutdown: failed to start child: {AgentheonWeb.ProxyEndpoint, :http}
        ** (EXIT) shutdown: failed to start child: :listener
            ** (EXIT) :eaddrinuse


I have verified that port 4000 is not in use and only is in use when the app starts. I expect there is a conflict with the proxy port and the server port but I'm not sure.
message.txt7.8KB
Was this page helpful?