I get stuck after postinstalling yunohost on a VPS using a fresh Debian 11 installation: my admin user credentials (first user created via postinstall) are not recognized.
I did the same installation on a raspberry pi 3 without any problem.
(using of course https://domain.name/yunohost/admin)
I first noticed that the admins group did not exist.
So I followed the recommended procedure on the 11.1.1 announcement to clean everything and then created the admins group:
MAINDOMAIN=$(yunohost domain list --output-as json | jq -r '.main')
yunohost user group add-mailalias admins root@$MAINDOMAIN admin@$MAINDOMAIN admins@$MAINDOMAIN webmaster@$MAINDOMAIN abuse@$MAINDOMAIN postmaster@$MAINDOMAIN
yunohost user group remove-mailalias admins root admin admins abuse webmaster postmaster
Now the admins group exist and my “admin” user (testuser) is a member:
yunohost user group list
Unfortunately the password is still not recognized and changing the password via “yunohost user update testuser -p” does not change anything.
The command gives a warning “Failed to fetch quota info … Command ‘doveadm -f flow quota get -u testuser’ returned non-zero exit status 75”, but I guess it’s kinda expected since the user’s mailbox quota is empty.
doveadm (1:2.3.13+dfsg1-2+deb11u1) and slapd (2.4.57+dfsg-3+deb11u1) are functional.
I’m confuse with this one.
The standard connexion to LDAP works and not the TLS one:
Is it something expected? Since .cert and .key are specified within the slapd conf but that we are using port 389 (instead of the default 363 for TLS).
But a connection test result in a “Can’t contact LDAP Server (-1)”
I’ve added slapd:ALL in /etc/hosts.allow.
Then I deleted the main user, did a regen-conf --force, and recreated the main user (= admin).
Slapd could not be contacted (due to the hosts.allow configuration).
As a result the creation of the main user was faulty (the associated system user and thus the /home/user folder could not be created). Even with the slapd connection allowedd, the user was then not recognized.
It was therefore necessary (in addition to authorizing slapd in hosts) to recreate the user.
If a dev or someone in the know could confirm if this is the right thing to do or if I’m just badly working around a problem that’s still there, I’d love to hear from you!