Consideration
HTTP Status 404 messages occur when accessing the FME Flow web interfaces. This can happen for a few reasons: incorrect WAR file deployment, incorrect reverse proxy configuration, incorrect ports, or incorrect user permissions.
Incorrect deployment of WAR files
The .war files may have been installed in the wrong directory. Also, Antivirus, cybersecurity & Malware Protection software (e.g., McAfee, FireEye) can sometimes prevent successful WAR file installation.
Resolution 1
Check that no other processes use the FME Flow Web Application port on the system where FME Flow is installed. The default ports are typically either 80 or 443, but may vary depending on your FME Flow configuration.
To check which ports are in use on the system, run the following command from the command line:
netstat -aonThis lists all ports currently in use on the system. Check for the entry for the port your FME Flow is configured to run on. For example, if FME Flow uses port 80, look for an entry like this: 0.0.0.0:80. If an application other than FME Flow is using that port, you will need to stop that application, change it to use a different port, or change the port FME Flow uses.
Resolution 2
Check that you've used the correct install directory and that a folder exists for each WAR file.
Temporarily disable the Antivirus, cybersecurity, and malware protection software, then install FME Flow. Your IT department can help with this. Your IT department may be able to configure the Antivirus software to allow installation while still running (we can't provide this advice).
Resolution 3
Redeploying the WAR files in FME Flow's Tomcat directory can help clear this problem, especially if it started happening after installing or updating antivirus software on the system.
On the machine where the FME Flow Web Application Server is installed, go to Services and stop the service. Then open the following directory: <ServerInstallDirectory>\Utilities\tomcat\webapps\
Back up all the folders inside, then delete them from the webapps folder (leaving only the .war files). Finally, restart the FME Flow Web Application Service. It should automatically re-create the folders inside. Now check whether you can access the FME Flow homepage again.
Incorrect Reverse Proxy Configuration
If you use a separate web server and servlet container (e.g., IIS and Tomcat, or Apache and Tomcat), the connector filter may be misconfigured, causing the request to be forwarded to the servlet container even though the file is on the web server.
Resolution
Review the reverse proxy setup documentation and follow the steps described. For additional information, please see FME Flow Troubleshooting: Proxies.
Incorrect Port Specified
When you installed FME Flow, you chose a port that the web server runs on. If this has since changed, the links in the Start menu will point to the wrong port.
Resolution
Manually change the URL to match your web server: http://<host>:<port>/fmeflow
Incorrect User Permissions
After you have installed FME Flow, if you change the 'Log on As' account in Services and the new user does not have the correct permissions to access the FME Flow folder, you will not be able to access the FME Flow Web Interface.
Resolution
Find the FMEFlow folder in C:\Program Files, right-click and select 'Properties'. Under the Security tab, select 'Edit...' and add your new user, ensuring they have Full control permissions checked.