Login Problems

Login Problems

First-run setup keeps appearing

Confirm /app/data is persistent and writable. The initial Administrator and setup state are stored in users.sqlite. If the container starts with a new or empty volume, PalCenter correctly enters setup again.

Username or password is rejected

• Usernames are case-sensitive.
• Re-enter the current password rather than the original temporary password.
• Ask an Administrator to confirm that the account is enabled.
• Wait before retrying after repeated failures; login attempts are throttled.

PalCenter does not provide a default Administrator password.

Password change is required

Accounts created by an Administrator receive a temporary password. On first sign-in, PalCenter directs the user to Profile to choose a new password before other protected actions are available.

Login works but does not persist

• Confirm the same /app/data volume is used after container recreation.
• Check browser cookie restrictions.
• When using HTTPS, set PALCENTER_SESSION_COOKIE_SECURE=true.
• Do not enable secure cookies when accessing PalCenter only through plain HTTP, because the browser will not send them.
• Ensure the reverse proxy preserves the original host and protocol correctly.

Account disabled or deleted

Disabled and deleted accounts cannot authenticate. Existing sessions are invalidated when account state or security-sensitive details change.

Restored backup

A restore replaces users, password hashes, and the session-signing secret with the backup contents. Use credentials from the restored backup. Existing browser sessions may require a new login.