-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discovery not working #259
Comments
I tried almost all options but didn't get success and finally i switch to redis mode to get all process working... |
Try updating these variables in your
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I'm using cote on my native nodejs project which is working without any docker or kubernetes (just running it with pm2 on Ubuntu 18)
It's working as normal in AWS EC2 servers but when I tried to start same process with some version node_modules version on Vultr cloud servers, the services is not connecting to each other (Requested and Responders aren't matched.)
this is result of
ifconfig
command on Vultr machine:enp1s0
is public interfaceenp6s0
is private (internal) interfaceI tried to use cote like this:
But with this case only 2 process is connecting each other (whereas my project has 5 different process which each of them connecting to another one with different Requester-Responsed relationship) and it's only working if I start responded first and requester after.
What kind of problem is this?
Also I will appreciate if someone can explain me what I need to write for broadcast or multicast properties if I want to use them (internal ip, subnet or broadcast (where I think that it will be router ip))
Thanks
The text was updated successfully, but these errors were encountered: