After installing tryton on the server, the first login was attempted via the browser. A window asked for the user name and suggested “admin”. If you select “admin” and click on the “Log-in” button, a new window opens and asks for “Password for admin”. If the password assigned with trytond-admin is entered and “OK” is pressed, the login does not take place, but the window opens again and asks for “Password for admin” again. This routine can be repeated endlessly. A login is not possible.
Try resetting the password of the administrator user with the trytond-admin --reset-password
command.
This reset the password by sending an email to the administrator if an email has been set and that the server can send email.
I think it is simpler to set again a password using trytond-admin -d <database> --password
.
Are you sure you type the same password?
First, the password was set to “abcd” with trytond-admin. Then the database query of the table res_user for “admin” returned the password_hash “$argon2id$v=19$m=65536,t=3,p=4$LGWMkRJijHEO4XzvnXMuJQ$KgH7IRbztZwfrsyvI/W2/mzNUpCpWlQ/laCU1KbuW8g”. Further the password “abcd” was encrypted with “PasswordHasher” and both hashes were identical. Now the login was attempted with the user “admin” and the password “abcd”, but every time “OK” was pressed, the prompt “Password for admin” appeared again and again in an endless loop. To avoid any queries: every care was taken to ensure that the password “abcd” was entered correctly and the Caps Lock button was not activated.
Then you must check that you are using the same series for the web client and the server.
Also check that you have not filled the table res_user_login_attempt
which may block temporary the account.
Then run the server in verbose mode to find the reason of refusing the password.
- same series
Webclient (SAO): “version”: “7.4.0”
Sever: trytond 7.4.0
- check that you have not filled the table
res_user_login_attempt
tryton=# select * from res_user_login_attempt;
id | create_date | create_uid | device_cookie | ip_address | ip_network | login | write_date | write_uid
----±------------±-----------±--------------±-----------±-----------±------±-----------±----------
(0 rows)
- Unfortunately still the same: each time “OK” is pressed, the prompt “Password for admin” appears, but no login.
Here is the connection protocol:
insert user “admin” and press button “Log-in”
REQUEST_METHOD:POST
QUERY_STRING:
REQUEST_URI:/tryton/
POST-DATA:
REQUEST_METHOD:POST
QUERY_STRING:
REQUEST_URI:/tryton/
POST-DATA:
RESPONSE:{“id”:0,“error”:[“LoginException”,[“password”,“Passwort f\u00fcr admin”,“password”]]}
insert password “1234” and press button “OK”
REQUEST_METHOD:POST
QUERY_STRING:
REQUEST_URI:/tryton/
POST-DATA:
RESPONSE:{“id”:0,“result”:[1,“01a65b20bf915b49a18249b5b3822561127d2bcf6c4e607f6c9bb648513be223”]}
REQUEST_METHOD:POST
QUERY_STRING:
REQUEST_URI:/tryton/
POST-DATA:
REQUEST_METHOD:POST
QUERY_STRING:
REQUEST_URI:/tryton/bus
POST-DATA:{“channels”:[“client:3df22402-6182-41e6-b8a3-e7ea2f7c7f75”]}
REQUEST_METHOD:POST
QUERY_STRING:
REQUEST_URI:/tryton/
POST-DATA:
REQUEST_METHOD:POST
QUERY_STRING:
REQUEST_URI:/tryton/
POST-DATA:
RESPONSE:{“id”:0,“error”:[“LoginException”,[“password”,“Passwort f\u00fcr admin”,“password”]]}
REQUEST_METHOD:POST
QUERY_STRING:
REQUEST_URI:/tryton/bus
POST-DATA:{“channels”:[“client:3df22402-6182-41e6-b8a3-e7ea2f7c7f75”]}
REQUEST_METHOD:POST
QUERY_STRING:
REQUEST_URI:/tryton/bus
POST-DATA:{“channels”:[“client:3df22402-6182-41e6-b8a3-e7ea2f7c7f75”]}
REQUEST_METHOD:POST
QUERY_STRING:
REQUEST_URI:/tryton/bus
POST-DATA:{“channels”:[“client:3df22402-6182-41e6-b8a3-e7ea2f7c7f75”]}
REQUEST_METHOD:POST
QUERY_STRING:
REQUEST_URI:/tryton/bus
POST-DATA:{“channels”:[“client:3df22402-6182-41e6-b8a3-e7ea2f7c7f75”]}
REQUEST_METHOD:POST
QUERY_STRING:
REQUEST_URI:/tryton/bus
POST-DATA:{“channels”:[“client:3df22402-6182-41e6-b8a3-e7ea2f7c7f75”]}
REQUEST_METHOD:POST
QUERY_STRING:
REQUEST_URI:/tryton/bus
POST-DATA:{“channels”:[“client:3df22402-6182-41e6-b8a3-e7ea2f7c7f75”]}
REQUEST_METHOD:POST
QUERY_STRING:
REQUEST_URI:/tryton/bus
POST-DATA:{“channels”:[“client:3df22402-6182-41e6-b8a3-e7ea2f7c7f75”]}
REQUEST_METHOD:POST
QUERY_STRING:
REQUEST_URI:/tryton/bus
POST-DATA:{“channels”:[“client:3df22402-6182-41e6-b8a3-e7ea2f7c7f75”]}
This seem to say that you received a session which seems to be directly invalid.
So maybe the session timeout is too short or there is different between the clock of the server and the database.
To find the error, the browser history of the current version of Firefox was analyzed. During the login phase, the error message appears when the Tryton server responds:
„A notification request can only be called from a short-running user-generated event handler.“
After that, the Tryton server only responds to each request with 401 unauthorized.
This is not a Tryton server response.