Unchecking "Allow unlisted file name extensions" results in 404.7 error

Importance of "Allow unlisted file name extensions" in IIS regarding the Orchestrator instance.

Issue Description:

Orchestrator requires the "Allow unlisted file name extensions" setting to be engaged due to its dynamic page generation process. This process often results in pages that either lack extensions or have unique extensions that resemble GUIDs (for example, 193031F0-D938-4108-B9CC-4ABD39C25FBC). Consequently, it's imperative to maintain the "Allow unlisted file name extensions" setting in an active or checked state at all times.

Resolution:
To avoid issues, "Allow unlisted file name extensions" must always remain checked in the IIS Request Filtering settings.

Steps to locate this setting in IIS:

  1. Open IIS Manager and select the UiPath Orchestrator website.
  2. Double-click Request Filtering under the IIS section.
  3. Go to the File Name Extensions tab.
  4. In the Actions panel on the right, click Edit Feature Settings.
  5. Ensure the option "Allow unlisted file name extensions" is checked.
  6. Click OK to apply the settings.

Impact of Unchecking:
Unchecking this setting will cause Orchestrator to fail in rendering its pages and communicating with other services. You may encounter errors like 404 (Not Found) or failures in the Orchestrator UI that will prevent normal operations, including job executions and accessing assets or logs.

1 Like

A post was split to a new topic: How to uncheck the setting “Allow unlisted file name extensions” in IIS?

Hi @UiPath_Community , @system

As part of our security compliance we have been told to uncheck the IIS setting " Allow unlisted file name extensions" .
But as per the article in 2021 , it was said that it must be always enabled as the pages are dynamically generated .

Please help me to understand if in 2024 , this setting must still be checked only Or any fix is provided to uncheck it and still continue to access orchestrator url …

Yes, even in 2024, the “Allow unlisted file name extensions” setting in IIS must still be checked for UiPath Orchestrator to function properly. This is because Orchestrator dynamically generates pages that may not have traditional extensions or use unique identifiers for each session.

If this setting is unchecked, Orchestrator won’t be able to load its pages, which will lead to access and functionality issues. Unfortunately, there is no workaround to safely disable this setting while still ensuring proper access to the Orchestrator interface.

1 Like