Webmail Error 500 - Internal Server Error

markush · 2025-09-27T19:16:17+00:00

Hallo, ich heute meine Community Edition geupdatet, seitdem komme ich nicht mehr ins Webmail rein: Bereits mehrmals neu gestartet und auch einmal herunter...

LuckyStriker

WalterH In which file you changed this value?

I changed it in
/etc/grommunio-web/config.php

WalterH I guess you need to edit: /etc/php8/fpm/php.ini and in /etc/php8/fpm/php-fpm.conf set log_level = debug and restart php-fpm.service.

There's no php.ini in this folder. I changed the log_level in php-fpm.conf and restarted the php-fpm service.
But no changes in output. If I leave the "display_errors" to false in config.php, only the 500 error page is shown and also logged to access.log.
When changing it to true, only a blank page appears as webmail and no 500 error is recognized.
The access.log gets a 200 OK, but nothing is logged to the error_log.

Mister2

Have been a way for a few days and saw this post before I applied the outstanding updates yesterday. However, I have just applied todays' updates to Gromox v3..... etc on a clone of my production server and all appears to have gone well, with no issues with the webmail as mentioned above.

Hopefully, if you can do test update on your server (or at least get a snapshot/or backup of it) you should be able to update and fix your issues with webmail.

And a big thank you to those who reported the issue (saved me a few hours not having to dig for a solution or rolling back to a previous snapshot) and the Devs for getting it sorted so quickly.

EDIT: One anomaly that I have spotted is the the CUI console is showing that nginx is not running, even though in the admin GUI it shows as running and the admin and web interfaces seems to be working normally.. A reboot of the server seems to fix this.

Also note there are a lot of sqlite Schema Updates (from EV-18 to EV-23) that start running once the update is in place, these will make your server sluggish as it ploughs through each mailbox database making the changes - so just be aware it might take a while (especially on big servers) for performance to return to normal.

ChrisTucker

Hello Mister2,

Thanks for your post.

I updated my mail appliance:

Retrieving: grommunio-common-28.2-lp155.14.1.x86_64.rpm ..................................................................................................[done]
Retrieving: grommunio-cui-1.1.3.b0091e0-lp155.6.1.noarch (grommunio)                                                                       (3/13),  61.8 KiB
Retrieving: grommunio-cui-1.1.3.b0091e0-lp155.6.1.noarch.rpm .................................................................................[done (9.9 KiB/s)]
Retrieving: grommunio-dbconf-1.1.1.da20a46-lp155.13.1.x86_64 (grommunio)                                                                   (4/13),  27.4 KiB
Retrieving: grommunio-dbconf-1.1.1.da20a46-lp155.13.1.x86_64.rpm .............................................................................[done (8.5 KiB/s)]
Retrieving: grommunio-setup-1.1.14.768d394-lp155.71.1.noarch (grommunio)                                                                   (5/13),  32.8 KiB
Retrieving: grommunio-setup-1.1.14.768d394-lp155.71.1.noarch.rpm .........................................................................................[done]
Retrieving: gromox-3.0.0.g21b0cd4-lp155.1.1.x86_64 (grommunio)                                                                             (6/13),   2.2 MiB
Retrieving: gromox-3.0.0.g21b0cd4-lp155.1.1.x86_64.rpm .......................................................................................[done (1.6 MiB/s)]
Retrieving: gromox-debugsource-3.0.0.g21b0cd4-lp155.1.1.x86_64 (grommunio)                                                                 (7/13),   1.1 MiB
Retrieving: gromox-debugsource-3.0.0.g21b0cd4-lp155.1.1.x86_64.rpm .......................................................................................[done]
Retrieving: libexmdbpp0-1.11.3.a477f82-lp155.305.1.x86_64 (grommunio)                                                                      (8/13),  77.7 KiB
Retrieving: libexmdbpp0-1.11.3.a477f82-lp155.305.1.x86_64.rpm ............................................................................................[done]
Retrieving: mapi-header-php-1.7.0.be09cd6-lp155.13.1.noarch (grommunio)                                                                    (9/13),  96.7 KiB
Retrieving: mapi-header-php-1.7.0.be09cd6-lp155.13.1.noarch.rpm .............................................................................[done (74.2 KiB/s)]
Retrieving: gromox-debuginfo-3.0.0.g21b0cd4-lp155.1.1.x86_64 (grommunio)                                                                  (10/13),  22.7 MiB
Retrieving: gromox-debuginfo-3.0.0.g21b0cd4-lp155.1.1.x86_64.rpm ............................................................................[done (16.9 MiB/s)]
Retrieving: python3-pyexmdb-1.11.3.a477f82-lp155.305.1.x86_64 (grommunio)                                                                 (11/13), 119.6 KiB
Retrieving: python3-pyexmdb-1.11.3.a477f82-lp155.305.1.x86_64.rpm ...........................................................................[done (74.9 KiB/s)]
Retrieving: grommunio-index-1.3.0.g2bd8a8c-lp155.13.1.x86_64 (grommunio)                                                                  (12/13),  62.2 KiB
Retrieving: grommunio-index-1.3.0.g2bd8a8c-lp155.13.1.x86_64.rpm ............................................................................[done (62.2 KiB/s)]
Retrieving: grommunio-sync-2.3.1.a034e08-lp155.15.1.noarch (grommunio)                                                                    (13/13), 265.5 KiB
Retrieving: grommunio-sync-2.3.1.a034e08-lp155.15.1.noarch.rpm ..............................................................................[done (76.7 KiB/s)]

Checking for file conflicts: .............................................................................................................................[done]
( 1/13) Installing: grommunio-admin-common-42.e17ec55-lp155.36.1.noarch ..................................................................................[done]
( 2/13) Installing: grommunio-common-28.2-lp155.14.1.x86_64 ..............................................................................................[done]
Failed to try-restart grommunio-cui@.service: Unit name grommunio-cui@.service is missing the instance name.
See system logs and 'systemctl status grommunio-cui@.service' for details.
( 3/13) Installing: grommunio-cui-1.1.3.b0091e0-lp155.6.1.noarch .........................................................................................[done]
( 4/13) Installing: grommunio-dbconf-1.1.1.da20a46-lp155.13.1.x86_64 .....................................................................................[done]
( 5/13) Installing: grommunio-setup-1.1.14.768d394-lp155.71.1.noarch .....................................................................................[done]
( 6/13) Installing: gromox-3.0.0.g21b0cd4-lp155.1.1.x86_64 ...............................................................................................[done]
( 7/13) Installing: gromox-debugsource-3.0.0.g21b0cd4-lp155.1.1.x86_64 ...................................................................................[done]
( 8/13) Installing: libexmdbpp0-1.11.3.a477f82-lp155.305.1.x86_64 ........................................................................................[done]
( 9/13) Installing: mapi-header-php-1.7.0.be09cd6-lp155.13.1.noarch ......................................................................................[done]
(10/13) Installing: gromox-debuginfo-3.0.0.g21b0cd4-lp155.1.1.x86_64 .....................................................................................[done]
(11/13) Installing: python3-pyexmdb-1.11.3.a477f82-lp155.305.1.x86_64 ....................................................................................[done]
(12/13) Installing: grommunio-index-1.3.0.g2bd8a8c-lp155.13.1.x86_64 .....................................................................................[done]
(13/13) Installing: grommunio-sync-2.3.1.a034e08-lp155.15.1.noarch .......................................................................................[done]

mail:~> systemctl status grommunio-cui@.service
Failed to get properties: Unit name grommunio-cui@.service is neither a valid invocation ID nor unit name.

After a reboot, sudo systemctl status nginx shows:
nginx.service - The nginx HTTP and reverse proxy server
     Loaded: loaded (/usr/lib/systemd/system/nginx.service; enabled; vendor preset: disabled)
     Active: active (running) since Wed 2025-10-01 15:47:56 BST; 2s ago
    Process: 14786 ExecStartPre=/usr/sbin/nginx -t (code=exited, status=0/SUCCESS)
   Main PID: 14787 (nginx)
      Tasks: 2 (limit: 4915)
     CGroup: /system.slice/nginx.service
             ├─ 14787 "nginx: master process /usr/sbin/nginx -g daemon off;"
             └─ 14788 "nginx: worker process" "" "" "" "" "" "" "" "" ""

During a restart of nginx (sudo systemctl restart nginx), sudo journalctl -f shows:
Oct 01 15:48:30 mail systemd[1]: Stopping The nginx HTTP and reverse proxy server...
Oct 01 15:48:30 mail systemd[1]: nginx.service: Deactivated successfully.
Oct 01 15:48:30 mail systemd[1]: Stopped The nginx HTTP and reverse proxy server.
Oct 01 15:48:30 mail systemd[1]: Starting The nginx HTTP and reverse proxy server...
Oct 01 15:48:30 mail nginx[14935]: nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
Oct 01 15:48:30 mail nginx[14935]: nginx: configuration file /etc/nginx/nginx.conf test is successful
Oct 01 15:48:30 mail systemd[1]: Started The nginx HTTP and reverse proxy server.

which certainly looks better.

I can successfully connect to the admin web interface (https://mail.xxx.co.uk:8443/) and I can see no obvious problems.

However, I still receive a 500 error whenever I try to connect to the user web interface (https://mail.xxx.co.uk/web/).

Mister2

@ChrisTucker Your appliance is still running on OpenSuse 15.5, you should try and get this upgraded to the current appliance base of OpenSuse 15.6. Can't confirm anything but might help resolve your webmail issue. Others on the forum maybe able to advise better on this but current appliance is based on OpenSuse 15.6.

There are articles on the forum (written by @WalterH) that set out the process to do the OpenSuse 15.5 to 15.6 upgrade.

I personally prefer to install a clean VM from the latest Appliance ISO and migrate the data - and as I only have a few mailboxes it doesn't take that long to migrate my data across afterwards.

ChrisTucker

Hello Mister2,

Thank you for your advice and thanks to @WalterH for https://community.grommunio.com/d/1879-update-form-open-suse-155-to-156, which was very clear.

After upgrading from OpenSuse 15.5 to 15.6, the user and admin web interfaces are now working again.

LuckyStriker

Hello everybody,
I can confirm that updating to Suse 15.6 and updating grommunio seems to resolve the problems.
Despite the very good instructions from @WalterH, I found the update not as easy as expected.
For everyone who also runs in trouble at point 11

zypper dup -y

run
zypper purge-kernels
to get some more space on boot.
But the webmailer now works as expected, so the other services too.
A big thank to everyone who helped finding out what's wrong.

WalterH

LuckyStriker For everyone who also runs in trouble at point 11

Thank you, I extended the recipe.

Andrew

Still getting 500 on the latest community update for RHEL9. Was the fix SUSE-specific?

hugh

EL9, community, grommunio-web-3.15.12.g25f73772d-325.1.noarch

Same error here:
.../web/: Http status 500
Setting of log_errors = On and display_errors = On: Http status 200, but only empty white webpage

No errors in /var/log/*, except
nginx-access.log: x.x.x.x - - [02/Oct/2025:11:06:43 +0200] "GET /web/ HTTP/1.1" 500

markush

Many thanks to @WalterH und @Mister2 ! I can also confirm that a upgrade the OS SuSE to 15.6 make the Webmail working again

hugh

EL9:

/usr/share/php-mapi/class.baserecurrence.php
Delete ... in lines 1709, 1734, 1949, they are PHP syntax errors

Andrew

hugh Nice spot!

Deleting the dots allows webmail to open but I get a popup "An unexpected error has occurred".
It looks like this issue was caused by Commit bcda7c7 so I reverted the changes to the lines you flagged by replacing $this->sortExceptionStart(...) with [$this, "sortExceptionStart"] and $this->sortStarttime(...) with [$this, "sortStarttime"].
This time webmail loads with no error at all.

hugh

Andrew Many thanks for your quick help!

Andrew

This still seems to be a problem on EL9 systems. Installing the latest update broke it again.

Andrew

I've raised a GitHub issue for the commit that seems to have broken this on EL9.
https://github.com/grommunio/mapi-header-php/issues/6

segro

since 2 days there is a new php Error. It looks like they are porting functions to php8.2 or so but dont reflect EL9 default php is still 8.0.xxx
https://github.com/grommunio/mapi-header-php/issues/6

GeneralProbe

I filed an official ticket, but I have not heared anything from Grommunio yet.
Let's hope they find a solution soon ...

WalterH

Will nginx -treport any useful information?

Andrew

WalterH The EL9 problem isn't a configuration issue. EL9 uses PHP 8.0, but the developers have started converting mapi-header-php to PHP 8.2 and pushing the updates into the EL9 repo. The more they update, the more gets broken.
Unfortunately, although EL9 has an optional application stream for PHP 8.2, Grommunio also relies on packages from EPEL that are only built for the default PHP 8.0 app stream.

Possible solutions could be:

Revert the EL9 version to PHP 8.0. This means maintaining two versions, though.
Provide PHP 8.2 compatible packages to replace the ones from EPEL, and instruct EL9 users to switch to the official PHP 8.2 app stream. This means maintaining forks of additional packages, though.
Build the MAPI module to work with the PHP 8.2 build in the unofficial "Remi's" repo for EL9 (this contains all of the necessary packages) and instruct EL9 users to switch to that. Customers that pay Red Hat for support may not be happy if they can no longer get support because they're using an off-brand build of PHP, though.

There's some detail in https://github.com/grommunio/mapi-header-php/issues/6

GeneralProbe

I think there is no really good solution.
I would prefer "Remi", since it allows having multiple PHP Versions installed.

« Previous Page