selsta
selsta
I took a look through the last log and so far didn't see anything interesting. Can you disable public RPC access and see if you can still reproduce the issue?
Since which version do you have this issue? I run multiple nodes and so far did not notice this behavior.
Which OS do you have? 4 of my Linux nodes are okay, my macOS node can reproduce the issue.
When did this issue started showing up for you? Also are the out peers unaffected? Can you set them higher than default?
Can you run your daemon with log level 2 for a couple minutes and then upload logs? Just trying to confirm if you have the same error.
I'm more interested in log level 2, you don't have to change out peers. It is not really relevant.
I don't see anything interesting in your log, but I only skimmed over it. Let's see if we can also get a log from @computerfreak94
@AsBenDoge The issue is that 3 minutes uptime is likely not enough for this issue to show up, that's why I don't see anything in your log.
I still don't see anything interesting, will have to let someone else look. @AsBenDoge if you completely restart your computer, do you still not get more than 1 incoming connection?...
I only need 20 minutes of loglevel 2 for mainnet, log 0 does not show anything useful. Can you search for your IP in the log and redact it and...