Topic: Performance issue after upgrade to roundcube 1.6.4

- iRedMail version (check /etc/iredmail-release):
1.6.6 MariaDB Edition
- Deployed with iRedMail Easy or the downloadable installer?
Downloadable Installer
- Linux/BSD distribution name and version:
Debian 10 Buster
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.

Hi, since the Upgrade from roundcube 1.5 to 1.6.4 we expiriencing an performance issue in the roundcube webmail. Sometimes when we switch folders or subfolders the session gets stuck and in the right lower corner an error message appears "server connection failed". after like 20 seconds the session is restored. We also get this error when we move mails into subfolders etc. Sometimes we get an gateways error from the nginx and need to reload the site.

the only error log we can find is in the nginx/error.log:

upstream timed out (110: Connection timed out) while reading response header from upstream, client: 62.178.XXX.XXX, server: _, request: "POST /mail/?_task=mail&_action=refresh HTTP/2.0", upstream: "fastcgi://", host: "mail.example.com", referrer: "httpx://mail.example.com/mail/?_task=mail&_mbox=INBOX"

Roundcube Version 1.6.4 with PHP 8.0 cli and fpm


Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.


Re: Performance issue after upgrade to roundcube 1.6.4

Is this big mailbox with few GB messages in total?


Re: Performance issue after upgrade to roundcube 1.6.4

Hello, no it is reproduceable in our test mailbox as well, and there are just 20 messages in it. All users are experiencing this problem in the new roundcube version. We are planning an upgrade to Debian 12 tomorrow and hope for a better experience then..


Re: Performance issue after upgrade to roundcube 1.6.4

Looks like the upgrade from debian 10 to debian 12 fixed the issue.