williamthewill
Hi guys, I have a question
I’m trying connect two distributed nodes with differents networks, but in always return false
these was my attempts:
pc1: iex --name one@william --cookie secret_token
pc2: iex --name two@uriel --cookie secret_token
pc1: iex --name one@william --cookie banana --erl ‘-kernel inet_dist_listen_min 9500’ --erl ‘-kernel inet_dist_listen_max 9500’
pc2: iex --name two@uriel --cookie banana --erl ‘-kernel inet_dist_listen_min 9500’ --erl ‘-kernel inet_dist_listen_max 9500’
pc1: iex --name one@161.22.57.2 --cookie secret_token
pc2: iex --name two@189.4.78.45 --cookie secret_token
Does anyone have any idea?
maybe it’s necessary open some network port
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
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
- #ai
- #umbrella
- #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
- #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.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 7- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
ityonemo
Open port 4369, that’s erlang port mapper daemon (epmd) https://erlang.org/doc/man/epmd.html
You may also have to activate other, higher port ranges in the firewall depending on your service
shanesveller
Note that the distributed Erlang protocol is really not designed for use over a WAN connection between the nodes, both in terms of its latency tolerances and mesh behavior and in terms of security considerations.
benwilson512
Right, to steal a joke from LYSE, distributed Erlang’s security protocol looks like this:
ityonemo
you can do erlang distribution over TLS, which is not horrible, if I understand correctly, but latency is still an issue.
2trc
@shanesveller base on your note, what would be the recommendation for building geo-redundant (resilient) solutions?
chasers
What are it’s latency tolerances?
ityonemo
Take your pick of rpc technologies, Jsonapi, openapi/swagger, grpc… I’m playing around with some of my own protocols (one which extends genserver over the WAN and one which extends Phoenix pubsub over the WAN) but I can’t recommend them for other people to use in prod, yet.