While attempting to access the web UI via the Apache Web Server, receiving error code AHD4409. Error is specific to the Apache Web server (httpd daemon). Apache Tomcat does not present with any problems and is accessible.
cURL access to the same from a Linux command line also results in an AHD4409 (expecting a result denoting binary content was detected).
Release: All SDM Releases running Apache Web Server on Linux
The Apache Web Server was configured to operate using the PrivateTmp setting enabled. Normally, webengine expects to write content into the common /tmp directory location. The setting creates an isolated tmp location which can disrupt communications between webengine and Apache Web Server.
Later Linux and Apache installations will have this setting enabled by default, making this a scenario that is more common among newer installations. The PrivateTmp setting may have also been enabled for sandboxing purposes.
sudo systemctl show httpd | grep PrivateTmp
sudo mkdir -p /etc/systemd/system/httpd.service.d
sudo nano /etc/systemd/system/httpd.service.d/override.conf
[Service]
PrivateTmp=false
sudo systemctl daemon-reload
sudo systemctl restart httpd
The above changes apply specifically to Apache Web Server (httpd) and not Apache Tomcat. These are two distinct implementations of the web server technology developed by Apache, each with their own configuration requirements and settings. Apache Web Server is an optional web component that Service Desk supports on non-Windows implementations, most commonly Linux. Windows would use IIS in its place.
For additional Apache Web Server settings, please see also Apache Web Server access results in "You don't have permission to access this resource"