ktanev
I’m still learning Elixir, Phoenix and Mnesia, so probably it is a newbie question.
What I am trying to achieve is running 3 nodes on different IPs and connect them. I am executing on three terminals
PORT=4001 iex --name n1@127.0.0.1 --cookie secret_cookie -S mix phx.server
PORT=4002 iex --name n2@127.0.0.5 --cookie secret_cookie -S mix phx.server
PORT=4003 iex --name n3@127.0.0.8 --cookie secret_cookie -S mix phx.server.
The problem is that the second and third node do not connect to each other and giving me a warning
[warn] global: :"n2@127.0.0.5" failed to connect to :"n3@127.0.0.8". Running Node.ping returns :pang on both, the second and third one.
I have tried running it on the same IPs and it works, so I suppose there should be something more to do in order for them to connect to each other.
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Catch errors, track performance, monitor hosts and more.
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
- #ai
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming
Our Sponsors
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
**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)
hauleth
On macOS all other addresses in
127.0.0.0/8are unbound and you need to manually bound them to thelo0.Also Liked
benwilson512
I’m on OS X so perhaps it’s an OS X thing? Regardless, the OP should make sure that the IPs they’re using are addressable in the general sense. If they are not, that’s probably the issue. If they are, then we know to look elsewhere for a solution to their problem.
benwilson512
Unless regular
ping 127.0.0.5works and routes to your local computer, you probably want all of those nodes to be on127.0.0.1.