You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue occurred following the upgrade from Teampass v2.1.26 to v3.0.10 (following the documentation and going through the intermediate versions);
Page on which it happened
On the password viewing page ("Items");
The passwords are displayed correctly, but some cannot be opened (error: "You are not allowed to do that!") without being able to identify why. This affects all users for the same password, regardless of permissions.
After checking the database, there doesn't seem to be anything conclusive between a working password and one that doesn't.
Note that if the item cannot be accessed, it is still possible to copy the login or password.
This issue occurred following the upgrade from Teampass v2.1.26 to v3.0.10 (following the documentation and going through the intermediate versions);
Page on which it happened
On the password viewing page ("Items");
The passwords are displayed correctly, but some cannot be opened (error: "You are not allowed to do that!") without being able to identify why. This affects all users for the same password, regardless of permissions.
After checking the database, there doesn't seem to be anything conclusive between a working password and one that doesn't.
Note that if the item cannot be accessed, it is still possible to copy the login or password.
Server configuration
Operating system: Linux teampass 6.1.0-23-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.99-1 (2024-07-15) x86_64
Web server: Apache
Database: 5.5.5-10.11.6-MariaDB-0+deb12u1
PHP version: 7.4.33
Teampass version: 3.0.10
Teampass configuration file:
Updated from an older Teampass or fresh install:
Client configuration
Browser: -
Operating system: - bits
Logs
Web server error log
Teampass 10 last system errors
Log from the web-browser developer console (CTRL + SHIFT + i)
The text was updated successfully, but these errors were encountered: