• 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.

Wrong warn message: Another user with the same username (admin) is already logged in to Plesk.

Azurel

Silver Pleskian
User name: Azurel

TITLE

Wrong warn message: Another user with the same username (admin) is already logged in to Plesk.

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

CentOS 8.2, Plesk Obsidian

PROBLEM DESCRIPTION

Warning: Another user with the same username (admin) is already logged in to Plesk.

STEPS TO REPRODUCE

I don't know. I logged in with HTTP and after set SSL certificate for plesk with HTTPS. I tested login in private mode too.

ACTUAL RESULT

See description

EXPECTED RESULT

When I logged in with same Name, same Password, same IP. I think this message should not appear.

ANY ADDITIONAL INFORMATION



YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Same Name, same password, same IP can indeed lead to duplicate logins, because you might have received a new PHP session ID. This will most likely be true when cookies were deleted between sessions, when the procotol changed (like a switch between http and https), when your browser changed, when you are using a different device.
 
Back
Top