Using a custom login on 2.17.0 (the user id is the smartfox username shown in Login failed:)
It seems to fail the login, in a way that I can't catch or figure out why it happens. Its very intermittent and happens <0.1% of the time but the users do love to shout at me when it happens.
I suspect theres an issue in the server side extension - one fast way I can fix this is via an option in my admin panel to clear the current cached data. Is there any way I can catch the inbuilt "WARN - Login failed:" message so I can try to figure out where the bug lays in this.
Code: Select all
26 Sep 2022 | 06:55:13,883 | INFO | SocketReader | bitswarm.sessions.DefaultSessionManager | | Session removed: { Id: 75531, Type: DEFAULT, Logged: No, IP: 104.205.158.199:49162 }
26 Sep 2022 | 06:55:14,525 | INFO | SocketReader | bitswarm.sessions.DefaultSessionManager | | Session created: { Id: 75532, Type: DEFAULT, Logged: No, IP: 104.205.158.199:49163 } on Server port: 9933 <---> 49163
26 Sep 2022 | 06:55:15,249 | WARN | SFSWorker:Ext:66 | v2.api.SFSApi | | Login failed: 1710030595 , session is already expired!
26 Sep 2022 | 06:55:20,040 | INFO | SFSWorker:Ext:87 | entities.managers.SFSRoomManager | | Room removed: { Zone: H3D }, [ Room: R136479, Id: 216433, Group: NR, isGame: true ], Duration: 29820
26 Sep 2022 | 06:55:23,917 | INFO | SocketReader | bitswarm.sessions.DefaultSessionManager | | Session removed: { Id: 75532, Type: DEFAULT, Logged: No, IP: 104.205.158.199:49163 }
26 Sep 2022 | 06:55:24,549 | INFO | SocketReader | bitswarm.sessions.DefaultSessionManager | | Session created: { Id: 75533, Type: DEFAULT, Logged: No, IP: 104.205.158.199:49164 } on Server port: 9933 <---> 49164
26 Sep 2022 | 06:55:25,263 | WARN | SFSWorker:Ext:66 | v2.api.SFSApi | | Login failed: 1710030595 , session is already expired!