CyberPanel on AWS - cannot use RainLoop after snapshot restore - advice?

As the title says, I am hosting a number of critical sites on a CyberPanel install on an AWS ec2.

During the creation of this instance I intended to assign an elastic IP (stable IP) however in doing so it changed the initial IP assigned which broke a number of processes. I have since been able to change the IP in the machineIP file and have re-establish loopback so the REST-API works again.

However since doing this I have not been successful in logging into the RainLoop Admin, and therefore have never set it up.

I have confirmed I have the correct RainLoop admin password (/usr/local/CyberCP/public/rainloop.php)
however everytime I try to log in tells me authentication failed.

What are some things I should be looking at?

the logs show: (IPs x’d out)
Feb 1 22:36:24 localhost dovecot: pop3-login: Disconnected (no auth attempts in 0 secs): user=<>,,, TLS handshaking: SSL_accept() failed: error:14201044:SSL routines:tls_choose_sigalg:internal error, session=<RYn0h/zWSO6saBjd>

The rip changes in each log entry and the lip reflects the machine’s private ip I am not sure what the error code represents… any ideas?

OS: Ubuntu 20.04.3 LTS
CyberPanel: 2.1.1
Postfix: 3.4.13

Thank you all

Hello again, this is a bump of this issue
I just set up a whole new instance and I am still receiving the “Authentication failed” error while trying to log into the Rainloop admin account. The password is accurate as displayed in the application.ini.

Could this be a bug?

But AWS instances wont allow sending emails, why you need rainloop?

That’s simply untrue.
Unless, have you’ve disabled rainloop intentionally?

On AWS the ports are disabled by default, but can be enabled upon request.

If you have got your ports opened, thats ok then.

Did you install aws from marketplace or manually?

Ports are open and marketplace

it used to work early last year - since then, even on new instances I cannot enter the admin page.

You should use our installation guide and install the latest version of CyberPanel.

2.1.1 is way old.

Set up a vm and install CyberPanel on it.

Do the upgrade commands not function?
I’ve followed the instructions it appeared to complete correctly but is still at 2.1.1
Is there something not listed in the instructions I should be doing differently?

do yum or aptget update upgrade

sh <(curl || wget -O -

in one line then press enter to use current latest version

Thanks, I had already done this.

What I am seeing at the end after running the command is

Saving to: ‘’                                                                                                 
                                                                                                                         100%[===================>]  96.97K  --.-KB/s    in 0.02s                                            
2022-03-04 14:59:52 (5.73 MB/s) - ‘’ saved [99297/99297]  

Am I supposed to run something after this file saves to actually install it?
I do not see this in the instructions.

1 Like

that is part of the automate upgrading sequence
just wait… until back to # bash

That’s what I would expect but the terminal simply closes afterwards.

well that is something not normal…

cant help you about that…

1 Like

Updates Installed

CP version now 2.1.2
Rainloop still will not authorize the login. continuing to research

1 Like

Can you share logs when you try to login?


[14:50:46.536][c589d6cb] INFO[DATA]: [DATE:05.03.22][OFFSET:-00][RL:1.16.0][PHP:7.3.33-1+focal][IP:][PID:17884][LiteSpeed][litespeed]
[14:50:46.536][c589d6cb] INFO[DATA]: [APC:off][MB:on][PDO:mysql,sqlite][Streams:tcp,udp,unix,udg,ssl,tls,tlsv1.0,tlsv1.1,tlsv1.2]
[14:50:46.536][c589d6cb] REQUEST[NOTE]: [GET] https://sld.tld:8090/rainloop/?/Lang/0/Admin/en_US/1c6a6bc68ba5f92d85485ab98a7fc6d4/
[14:50:46.537][c589d6cb] INFO[MEMORY]: Memory peak usage: 2MB
[14:50:46.538][c589d6cb] INFO[TIME]: Time delta: 0.011991024017334

[14:51:41.002][24963d68] INFO[DATA]: [DATE:05.03.22][OFFSET:-00][RL:1.16.0][PHP:7.3.33-1+focal][IP:][PID:17884][LiteSpeed][litespeed]
[14:51:41.002][24963d68] INFO[DATA]: [APC:off][MB:on][PDO:mysql,sqlite][Streams:tcp,udp,unix,udg,ssl,tls,tlsv1.0,tlsv1.1,tlsv1.2]
[14:51:41.002][24963d68] REQUEST[NOTE]: [POST] https://sld.tld:8090/rainloop/?/Ajax/&q[]=/0/
[14:51:41.003][24963d68] AJAX[NOTE]: Action: DoAdminLogin
[14:51:41.008][24963d68] POST[DATA]: {"Login":"admin","Password":"*******","Action":"AdminLogin","XToken":"1ed3b1f08b7aefbb0a93d72bd1cf55b5"}
[14:51:41.013][24963d68] INFO[NOTICE]: RainLoop\Exceptions\ClientException: AuthError[102] in /usr/local/CyberCP/public/rainloop/rainloop/v/1.16.0/app/libraries/RainLoop/Actions.php:3915
Stack trace:
#0 /usr/local/CyberCP/public/rainloop/rainloop/v/1.16.0/app/libraries/RainLoop/ServiceActions.php(174): RainLoop\Actions->DoAdminLogin()
#1 /usr/local/CyberCP/public/rainloop/rainloop/v/1.16.0/app/libraries/RainLoop/Service.php(151): RainLoop\ServiceActions->ServiceAjax('')
#2 /usr/local/CyberCP/public/rainloop/rainloop/v/1.16.0/app/libraries/RainLoop/Service.php(62): RainLoop\Service->localHandle()
#3 /usr/local/CyberCP/public/rainloop/rainloop/v/1.16.0/app/libraries/RainLoop/Service.php(85): RainLoop\Service->__construct()
#4 /usr/local/CyberCP/public/rainloop/rainloop/v/1.16.0/app/handle.php(94): RainLoop\Service::Handle()
#5 /usr/local/CyberCP/public/rainloop/rainloop/v/1.16.0/include.php(243): include('/usr/local/Cybe...')
#6 /usr/local/CyberCP/public/rainloop/index.php(13): include('/usr/local/Cybe...')
#7 {main}
[14:51:41.014][24963d68] AJAX[DATA]: {"Action":"AdminLogin","Result":false,"ErrorCode":102,"ErrorMessage":"","ErrorMessageAdditional":"","Time":22}
[14:51:41.014][24963d68] INFO[MEMORY]: Memory peak usage: 2MB
[14:51:41.014][24963d68] INFO[TIME]: Time delta: 0.022711992263794

My research on the github for RainLoop shows an old solution to a similar issue was to toggle the “Use Short Login” setting however, that’s not an option in the 1.16.0 config.

I found this: Unfortunately this was not a solution.

deb [arch=amd64] bionic main
deb focal main
since I have ubuntu 20.04.

However, during this update of dovecot it was not clear if I should keep the original config, do a 3 way merge or save the maintainer’s version. Perhaps I performed this update incorrectly. Some clearer instructions would help.

Firstly, do your logs show the "Invalid password in passdb: crypt() failed: Invalid argument” …
If no, then this cannot be the problem to your solution. Btw, I kept the original configs.
I have linked to the original source for my solution try looking in the original post.
Workaround for (some) Problems: Can´t login in Rainloop - General Discussion - CyberPanel Community.

Please follow the solution shared above, also share the dovecot logs not rainloop.