Closed offerm closed 6 years ago
I've seen this same thing recently I believe but haven't fully gotten to the bottom of it. It seems to happen only when you've configured a localhost listening address, and the result is a connection attempt to yourself. I couldn't see why exactly connections were even being attempted to oneself - debugging the connectNodes
sequence looked like we never attempted a connection to ourselves, but nevertheless I'd see an incoming connection with our own nodepubkey. #400 adds a check on incoming connections that they don't use our own nodepubkey which should fix this, but it doesn't explain why this came up in the first place.
Nothing to do with localhost. IMHO this has to do with the response we are getting from the bootstrap servers. I'm sure I'm listed there with a different pubkey
OK, might not be related to localhost, but I'd be interested to recheck this after #400 is merged either way.
This error doesn't seem to be happening with recent changes, can we close it? @offerm
Yep
On Fri, 5 Oct 2018 at 18:53 Daniel McNally notifications@github.com wrote:
This error doesn't seem to be happening with recent changes, can we close it? @offerm https://github.com/offerm
— You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ExchangeUnion/xud/issues/415#issuecomment-427413272, or mute the thread https://github.com/notifications/unsubscribe-auth/AJQ0cgWANbzH4hwPDAO-RFSdY8TaFv-wks5uh4CLgaJpZM4WQTvi .
Starting XUD (master). Letting XUD to create the database: