Hello guys,
One of my cPanel/WHM servers is showing an error when opening Webmail on cPanel accounts that have the Jupiter theme. If you change the theme to paper_latern the webmail page opens normally.
Here are the errors and logs of my server:

This is the error that happens when I click on "Check Email" button on the "Email Accounts" menu.
The error below I caught in the log /usr/local/cpanel/logs/error_log:
[2022-06-21 14:34:50 -0300] info [webmaild] Internal Server Error: "POST /cpsess4668975073/login/ HTTP/1.1" 500 Error ID 26d316e2bb480
cpsrvd 26d316e2bb480: The theme “jupiter” was not usable and no fallback theme was found. at /usr/local/cpanel/Cpanel/Server.pm line 432.
[2022-06-21 14:34:58 -0300] info [webmaild] Internal Server Error: "POST /cpsess1617933814/login/ HTTP/1.1" 500 Error ID 26d316e2bb480
cpsrvd 26d316e2bb480: The theme “jupiter” was not usable and no fallback theme was found. at /usr/local/cpanel/Cpanel/Server.pm line 432.
The error started happening last week. The server was at version 102, but I updated to see if the error would be fixed.
One of my cPanel/WHM servers is showing an error when opening Webmail on cPanel accounts that have the Jupiter theme. If you change the theme to paper_latern the webmail page opens normally.
Here are the errors and logs of my server:

This is the error that happens when I click on "Check Email" button on the "Email Accounts" menu.
The error below I caught in the log /usr/local/cpanel/logs/error_log:
[2022-06-21 14:34:50 -0300] info [webmaild] Internal Server Error: "POST /cpsess4668975073/login/ HTTP/1.1" 500 Error ID 26d316e2bb480
cpsrvd 26d316e2bb480: The theme “jupiter” was not usable and no fallback theme was found. at /usr/local/cpanel/Cpanel/Server.pm line 432.
[2022-06-21 14:34:58 -0300] info [webmaild] Internal Server Error: "POST /cpsess1617933814/login/ HTTP/1.1" 500 Error ID 26d316e2bb480
cpsrvd 26d316e2bb480: The theme “jupiter” was not usable and no fallback theme was found. at /usr/local/cpanel/Cpanel/Server.pm line 432.
The error started happening last week. The server was at version 102, but I updated to see if the error would be fixed.
Last edited: