archimondain
I would like to be able to call functions from my Elixir code while the whole Cowboy/Phoenix machinery is running. For some reason when I’m not on production everything works fine with iex -S mix. But on production I get
[error] Failed to start Ranch listener SyntaxWeb.Endpoint.HTTP in :ranch_tcp:listen([{:cacerts, :...}, {:key, :...}, {:cert, :...}, :inet6, {:port, 80}]) for reason :eaddrinuse (address already in use)
I’m not sure of what the problem is. From the error message, it seems that iex -S mix tries to listen port 80, while Cowboy is already listening to it. On the other hand it seems odd for the iex -S mix command to try running a server, does’n it ?
My question is : what is really happening ? and how can I load my project modules and run some elixir code in command line while a server is running on the machine ?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Marked As Solved- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
yurko
Are you using releases? The
serveroption has to do with them, otherwise if you are running the production system with mix it’s just your mix config.If you are using releases and want to do something with the running system, check out the remote console: mix release — Mix v1.20.2
Also Liked
hauleth
If this is Phoenix application, and you have:
In your production configuration, then application will try to start application, and by extension - start listening -on application launch. And
iex -S mixis the same asiex -S mix run, andmix help runreturns:Which mean it starts application which will fail due to trying to reuse listening port.
archimondain
Good call. I am using releases
, so that must be it.
I will check the link you provide
Thanks