Why Did My phpMyAdmin Session Expire?
If you were working in phpMyAdmin and suddenly got a "session expired," "token mismatch," or login screen, your session timed out. Here's why it happens and what to do.
DBEverywhere Session Timeouts
DBEverywhere enforces session timeouts based on your plan:
| Plan | Session Timeout |
|---|---|
| Free | 15 minutes |
| Paid | 8 hours |
When your DBEverywhere session expires, the connection to your database is closed. You'll need to start a new session from the dashboard.
phpMyAdmin's Own Timeout
phpMyAdmin also has its own internal session timeout, which defaults to 1440 seconds (24 minutes). If phpMyAdmin's PHP session expires before the DBEverywhere session, you may see a "token mismatch" error or be sent back to the phpMyAdmin login screen.
On the free tier, this never matters because the 15-minute DBEverywhere timeout hits first. On the paid tier, phpMyAdmin's internal timeout may occasionally trigger before the 8-hour limit.
What to Do When a Session Expires
- Go back to your DBEverywhere dashboard.
- If the session is still listed as active, click End Session to clean it up.
- Start a new connection.
Your database itself is not affected by a session timeout — only the browser session ends.
How to Avoid Timeouts
- Upgrade to the paid plan for 8-hour sessions instead of 15 minutes.
- Watch the timer in the session bar. It turns yellow near the end, and a banner appears 3 minutes before a free session expires. Timeouts are based on elapsed time, not idle time.
- Save your work frequently — if you're writing a long query, copy it to a text editor as a backup before running it.