You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
will sometimes pick the wrong local IP if you are connected to a VPN.
17:54:36.566 [main] INFO i.d.discovery.core.CuratorAdvertiser - Using '192.168.225.102' as listenAddress from found addresses: [/192.168.225.102, /10.0.1.101]
Easiest solution I can think of is do have a config param for dropwizard-discovery to match those addresses returned by ServiceInstanceBuilder.getAllLocalIPs(); against a regex pattern like "^10\.0\.1\.\d+" or something like that.
The text was updated successfully, but these errors were encountered:
@jplock it is a reasonable workaround for now, yes, but then the config can't be checked in and used by multiple developers who want to run integration tests. you'd have to manually modify the config each time you ran the tests on a different machine or on a different day (as IPs are dynamically allocated)
I'm not sure if this is the best way to solve this problem, but if you want to run a service locally and you use a VPN, the logic here:
dropwizard-discovery/src/main/java/io/dropwizard/discovery/core/CuratorAdvertiser.java
Line 85 in 2c3f45b
will sometimes pick the wrong local IP if you are connected to a VPN.
Easiest solution I can think of is do have a config param for dropwizard-discovery to match those addresses returned by
ServiceInstanceBuilder.getAllLocalIPs();
against a regex pattern like"^10\.0\.1\.\d+"
or something like that.The text was updated successfully, but these errors were encountered: