Fix: Failed to Check Session Lock
Resolve 'Failed to check session lock' errors caused by multiple instances or corruption.
The "Failed to check session lock" error occurs when the server can't acquire exclusive access to the world. This usually means another process is already using the world, or the lock file is corrupted.
Fixing the Error
Stop all server instances
Make sure no other server is running on the same world. Access the XGamingServer panel and confirm only one instance is active.
Delete the session lock file
Go to Files, navigate to your world folder (/world/), and delete the session.lock file.
Start your server
The server will create a new session lock when it starts.
⚠️ Warning: Never run two servers on the same world simultaneously. This will corrupt your world data.
📝 Note: If this error keeps recurring, your world may have deeper corruption. Try restoring from
Backups.
See also: Troubleshooting | Server Won't Start
If you need help, join our Discord.
How is this guide?
