• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Forwarded to devs PhpMyAdmin sudden timeout

Azurel

Silver Pleskian
Username: Azurel

TITLE

PhpMyAdmin sudden timeout

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

CentOS Linux 8.2.2004 (Core)
Plesk Obsidian Version 18.0.31 Update #1

PROBLEM DESCRIPTION

This is in all plesk versions. Login in plesk and pick a subscription and go to database -> phpmyadmin. Working in phpmyadmin for a longer time and you get a message box with error code 400 Bad Request (rejected). Its a time out. Because ajax call /phpMyAdmin/sql.php returns 400.

For security reasons there is a timeout. That's a good thing! But why do I get this timeout if I called a SQL query successful only one second before? Shouldn't the timeout for activity be extended accordingly?

Is this a setting from plesk or a phpmyadmin thing?

And why error 400? Shouldn't it rather say that you were automatically logged out?

STEPS TO REPRODUCE

see desciption

ACTUAL RESULT

see desciption

EXPECTED RESULT

see desciption

ANY ADDITIONAL INFORMATION



YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Help with sorting out
 
I have experienced something similar on Obsidian. The cause was that I was logged out from the panel. When you are not logged in to the panel, subsequent requests through phpMyAdmin fail, because phpMyAdmin is no longer authorized to access the database. So this might have something to do with the session expiration of your panel login.
 
It is related to the Plesk session timeout. The workaround is to increase it in Tools&Settings > Session Idle Time.
We should adopt the error message and show that it's an actual timeout. Bugreport PPPM-12565 was submitted.
 
Back
Top