Post: #1

I don't know Why, some player got their MAXping reached. They dont connect to game..

19:55:WARNING:Connection from 142.116.209.56 rejected (MAXPINGS reached 44/35)

Is there a way to reset this counter for let them play? Or the only method is reboot the shard?

Thx

Post: #2

This is handled by NetTTL (network time to live) setting on sphere.ini, if you set this value too high it will remember the connection for too long, making client reach MaxPings (max connections) faster because every time the client login or open a webpage will count as a new connection and it will remember this connection for too long

Unfortunately there's no way to reset this counter, so you must lower NetTTL value or raise MaxPings value

If you're getting these connections from sphere webpage, you can also do some HTTP caching (eg: set "Cache-Control: max-age=60" on page header) to make the client browser cache the page for X minutes, making it reload the page from cache while the cache is valid, and only do a new HTTP request to server after the cache expire

Post: #3

As always, A superb respond! THX!

Post: #4

it corrects this when you write it to the console as Maxpings (IP), "Maxpings 127.0.0.1"
or, as @Coruja says, you can keep the sphere.ini "MaxPing" setting high.