CyberPanel Community

ClosedSolution to "authentication failed" error in Rainloop

Ka
Kaushik71 #1

Hi all if you face errors with logging in to Rainloop and if your logs have something as “Invalid password in passdb: crypt() failed: Invalid argument” Then there is a simple fix for this. You need to update your Dovecot to 2.3.x as bcrypt is supported by 2.3.x. The steps are as follows:

  1. Add the reposity key of dovecot to the rpm key store:

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 18A348AEED409DA1

  1. Add the official dovecot Ubuntu Repo to sources.list

(this example is for Ubuntu 18)

sudo nano /etc/apt/sources.list.d/dovecot.list

insert into:

deb [arch=amd64] Index of /ce-2.3-latest/ubuntu/bionic/ bionic main

Save it and close editor

  1. Do a:

sudo apt update

  1. Do a:

sudo apt dist-upgrade

  1. Reboot your machine.

you rainloop should work nicely now.

Original post - Workaround for (some) Problems: Can´t login in Rainloop - General Discussion - CyberPanel Community

6 replies
as
asporkan #3

@Kaushik71 said:
Hi all if you face errors with logging in to Rainloop and if your logs have something as “Invalid password in passdb: crypt() failed: Invalid argument” Then there is a simple fix for this. You need to update your Dovecot to 2.3.x as bcrypt is supported by 2.3.x. The steps are as follows:

  1. Add the reposity key of dovecot to the rpm key store:

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 18A348AEED409DA1

  1. Add the official dovecot Ubuntu Repo to sources.list

(this example is for Ubuntu 18)

sudo nano /etc/apt/sources.list.d/dovecot.list

insert into:

deb [arch=amd64] Index of /ce-2.3-latest/ubuntu/bionic/ bionic main

Save it and close editor

  1. Do a:

sudo apt update

  1. Do a:

sudo apt dist-upgrade

  1. Reboot your machine.

you rainloop should work nicely now.

Original post - https://forums.cyberpanel.net/discussion/5385/workaround-for-some-problems-can-t-login-in-rainloop

Absolutely super solution. 10/10 points

Ma
Macho44 #6

Thanks. I’ve contacted support, waiting for feedback.

Sign in to reply