Skip to main content

Troubleshooting

Common Issues​

"Account locked" error​

The account has exceeded MaxPINAttempts (default 5). Wait PINLockoutSeconds (default 300s) or restart the server to clear lockout state.

Token authentication fails on reconnect​

  • Check that session.tok is being written to the correct directory
  • Verify the server's ServerHMACSecret hasn't changed since the token was issued
  • Check that TokenExpiryDays hasn't been reduced below the token's remaining lifetime

SQLite "database is locked" error​

Ensure only one server instance is writing to the same database file. SQLite uses WAL mode but isn't designed for multi-process writes.

"changeme_in_production" warning in logs​

Change ServerHMACSecret in Project Settings → Rogue Paradigm → ElysIdentity before shipping.

PIE multi-client issues​

ElysIdentity is PIE-safe. Client instances skip database loading (server-only). Token files are isolated per PIE instance.

FAQ​

Q: Can I use this without a dedicated server? A: Yes. Listen servers work fine — the host acts as both server and client.

Q: Is the PIN sent in plaintext? A: PINs are sent via UE RPCs. Enable UE's built-in encryption for wire security. PINs are never stored in plaintext — only salted SHA-256 hashes.

Q: Can I migrate from JSON to SQLite? A: Currently requires manual migration. Load from JSON, switch backend to SQLite, then save.