The admin password is set on your server, with one command. There is no password field in the admin and no reset by email.
In your project folder, as the user PHP runs as, with the data_dir of your front controller:
cd /var/www/your-site sudo -u www-data php vendor/bin/opensolr-chat-bot password /opt/opensolr-chat
- Type the new password. It is not shown as you type.
- Type it again.
- The command answers The admin password is saved in /opt/opensolr-chat/chat.sqlite. Every admin session was signed out.
The same command changes it later: the new password replaces the old one, and every admin session, in every browser, is signed out.
- At least 12 characters. A shorter one: The password must have at least 12 characters.
- The same twice. Otherwise: The two passwords are not the same. Nothing was saved.
- Stored as a hash (Argon2id, or bcrypt where PHP has no Argon2id), never as the password itself.
The first run creates the chat’s database in the data folder. Run as root, the database belongs to root and the web server cannot write it: the chat then fails with unable to open database file in your PHP error log. The fix is on Troubleshooting.
The user is www-data on Debian and Ubuntu, usually apache or nginx on Red Hat, Rocky or AlmaLinux, and often your own user on shared hosting.
Run composer install first. means the command was run outside the folder that holds vendor/.