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
Today I came accross issue, when there were problem in postgres database:
Newly created user on roundcube should have same ID as allready created one (my own problem with wrongly configured sequence). Since no new user record can be created, error was logged, but I was unable to send email (failed authentication agains mail server). So far so good. But in Settings->Profiles (/?_task=settings&_action=identities) they`re were visible identities of other users, not only mine created.
DETAIL: Key (user_id)=(1476) already exists. (SQL Query: INSERT INTO "users" (" created", "last_login", "username", "mail_host", "language") VALUES (now(), now( ), '[email protected]', 'mailboy.xxx.cz', 'cs_CZ')) in /opt/roundcube /program/lib/Roundcube/rcube_db.php on line 543 (POST /?_task=login&_action=logi n)
Issue was resolved by manually altering sequence number. But Roundcube should not allow user to log-in if no user data can be correctly inserted into database.
The text was updated successfully, but these errors were encountered:
Today I came accross issue, when there were problem in postgres database:
Newly created user on roundcube should have same ID as allready created one (my own problem with wrongly configured sequence). Since no new user record can be created, error was logged, but I was unable to send email (failed authentication agains mail server). So far so good. But in Settings->Profiles (/?_task=settings&_action=identities) they`re were visible identities of other users, not only mine created.
DETAIL: Key (user_id)=(1476) already exists. (SQL Query: INSERT INTO "users" (" created", "last_login", "username", "mail_host", "language") VALUES (now(), now( ), '[email protected]', 'mailboy.xxx.cz', 'cs_CZ')) in /opt/roundcube /program/lib/Roundcube/rcube_db.php on line 543 (POST /?_task=login&_action=logi n)
Issue was resolved by manually altering sequence number. But Roundcube should not allow user to log-in if no user data can be correctly inserted into database.
The text was updated successfully, but these errors were encountered: