Victor Bjelkholm

Thanks, been unavailable lately but just now starting getting this to work again. Thanks for the ping! :)

So, things are back to normal (issue ended up being that old certificates were being used to connect to Let's Encrypt from Caddy, so the certification renewal didn't work [and...

We're one version behind latest stable version of go-ipfs (we're on 0.4.19, latest is 0.4.20). Worth trying to upgrade to see if it helps as it's supposed to have performance...

According to @raulk from libp2p (discussion in Freenode #ipfs), seems related to the following issues: - https://github.com/libp2p/go-libp2p-connmgr/issues/44 - https://github.com/libp2p/go-libp2p-connmgr/issues/42 - https://github.com/libp2p/go-libp2p/issues/634

@vyzo if you need any information trying to track down the issue (pprof dump or whatever), let me know!

@vyzo I'll give that a try and report back. Thanks

Log: Tried first to disable Circuit Relay-related experimental options: ``` ipfs config --json Swarm.EnableAutoNATService false ipfs config --json Swarm.EnableAutoRelay false ipfs config --json Swarm.EnableRelayHop false ``` Didn't do any change....

> As a way to short-circuit the process, could you try to change your public key to provoke a mismatch between the multiaddr and your actual identity, so that the...

@raulk > I'd like to figure if the sudden inflow of connection is triggered by your node acting as a relay. Most certainly. But I'm still bit lost on why...

Seems to start going into the same pattern again, currently connected to 20k peers and counting. Was working fine for a couple of hours, but then started getting more and...