Skip to main content
Alan_
Staff
Alan_
Staff
March 6, 2026

Troubleshooting Tip: '500 Internal Server Error' when accessing FortiClient EMS Linux on GUI

  • March 6, 2026
  • 0 replies
  • 415 views
Description This article describes a possible cause of the '500 Internal Server Error' that may appear when accessing FortiClient EMS on Linux, and explains how to identify and resolve the issue.
Scope FortiClient EMS Linux.
Solution

When accessing FortiClient EMS through the GUI, the following error may appear:

 

Internal Server ErrorInternal Server Error

 

One possible cause of this error is a mismatch between the system timezone configuration files /etc/localtime and /etc/timezone.

 

Check Apache logs on the Linux server hosting FortiClient EMS.

 

Logs can be collected using one of the following methods:


/var/log/apache2

 

If /etc/timezone and /etc/localtime contain conflicting values, the following errors may appear in the Apache logs:

 

[Mon Mar 02 00:00:30.626489 2026] [wsgi:error] [pid 983877:tid 984027] [remote 172.23.166.213:1944] mod_wsgi (pid=983877): Failed to exec Python script file '/opt/forticlientems/fcm/fcm/wsgi.py'.
[Mon Mar 02 00:00:30.626526 2026] [wsgi:error] [pid 983877:tid 984027] [remote 172.23.166.213:1944] mod_wsgi (pid=983877): Exception occurred processing WSGI script '/opt/forticlientems/fcm/fcm/wsgi.py'.
[Mon Mar 02 00:00:30.626610 2026] [wsgi:error] [pid 983877:tid 984027] [remote 172.23.166.213:1944] Traceback (most recent call last):
[Mon Mar 02 00:00:30.626632 2026] [wsgi:error] [pid 983877:tid 984027] [remote 172.23.166.213:1944] File "/opt/forticlientems/fcm/fcm/wsgi.py", line 15, in <module>
[Mon Mar 02 00:00:30.626637 2026] [wsgi:error] [pid 983877:tid 984027] [remote 172.23.166.213:1944] import fcm.settings
[Mon Mar 02 00:00:30.626641 2026] [wsgi:error] [pid 983877:tid 984027] [remote 172.23.166.213:1944] File "/opt/forticlientems/fcm/fcm/settings.py", line 342, in <module>
[Mon Mar 02 00:00:30.626643 2026] [wsgi:error] [pid 983877:tid 984027] [remote 172.23.166.213:1944] TIME_ZONE = tzlocal.get_localzone_name()
[Mon Mar 02 00:00:30.626646 2026] [wsgi:error] [pid 983877:tid 984027] [remote 172.23.166.213:1944] File "/opt/forticlientems/fcm/env24_amd64/lib/python3.10/site-packages/tzlocal/unix.py", line 193, in get_localzone_name
[Mon Mar 02 00:00:30.626650 2026] [wsgi:error] [pid 983877:tid 984027] [remote 172.23.166.213:1944] _cache_tz_name = _get_localzone_name()
[Mon Mar 02 00:00:30.626653 2026] [wsgi:error] [pid 983877:tid 984027] [remote 172.23.166.213:1944] File "/opt/forticlientems/fcm/env24_amd64/lib/python3.10/site-packages/tzlocal/unix.py", line 144, in _get_localzone_name
[Mon Mar 02 00:00:30.626655 2026] [wsgi:error] [pid 983877:tid 984027] [remote 172.23.166.213:1944] raise utils.ZoneInfoNotFoundError(message)
[Mon Mar 02 00:00:30.626665 2026] [wsgi:error] [pid 983877:tid 984027] [remote 172.23.166.213:1944] tzlocal.utils.ZoneInfoNotFoundError: 'Multiple conflicting time zone configurations found:\\n/etc/timezone: Etc/UTC\\n/etc/localtime is a symlink to: Europe/Rome\\nFix the configuration, or set the time zone in a TZ environment variable.\\n'

 

FortiClient EMS relies on the system timezone configuration. If /etc/timezone and /etc/localtime contain different values, the EMS service fails to start correctly because it cannot determine which of these values is correct, resulting in a 500 Internal Server Error when accessing the GUI. 

 

EMS cannot change these settings, even during installation.

Ensure that /etc/timezone and /etc/localtime are configured consistently on the Linux system. Once the mismatch is corrected, the EMS services should start normally, and GUI access should work again.

 

See this article, Technical Tip: How to solve the '500 Internal Server Error' in FortiClient EMS Linux, for another possible cause for a 500 Internal Server Error.
Terms & ConditionsAccessibility statement