cargo run configure for provider should prefer lo address
marmistrz opened this issue · comments
Currently my provider-server-cfg.json looks like:
{"connectMode":"Manual","hubAddrs":["192.168.0.123:61622"],"p2pPort":61621,"publishService":true}
even though the hub and the provider are running on the same machine. 127.0.0.1 should probably be used instead.
Use case: I have both wifi and ethernet at home. If I set up the hub configuration on ethernet, then gu-provider fails to connect to the hub on wifi, due to no route to host. (because the IP address is different)
Stale issue message
Stale issue message