HTTP Error 500

There are many different HTTP Error 500 types, each with their own solution(s). This topic contains the most commonly encountered.

---

500.19 - Internal Server Error

When trying to load the Devolutions Server web page, the following HTTP Error 500.19 - Internal Server Error is displayed in the browser:

This error is due to the absence of the IIS ASP.NET Core Module (ANCM) and/or the IIS Rewrite Module:

Solution

1. From the Devolutions Server Console, edit the instance.
2. Open the Support tab.
3. Click on the IIS diagnostic button.
4. Click on Install prerequisites.

   

If running the PowerShell script from the Devolutions Server Console is blocked due to restrictions on the system, the script is located in the Scripts folder of the Devolutions Server Console installation folder.

---

500.19 - Internal Server Error (ASP.NET)

The HTTP Error 500.19 - Internal Server Error is triggered by an ASP.NET issue at line 60. The solution is to edit the <handlers> in the web.config file located in the Devolutions Server Console installation folder.

Solution

1. To locate the installation folder, open Devolutions Server Console and click Explore.

1. Find and open the web.config file.
2. Replace the <handlers> with:

<handlers>

    <remove name="MvcHttpHandler" />

    <remove name="UrlRoutingHandler" />

    <remove name="aspNetCore" />

    <add name="aspNetCore"

         path="*"

         verb="*"

         modules="AspNetCoreModuleV2"

         resourceType="Unspecified" />

</handlers>

1. Save the file.
2. Restart the Devolutions Server Console.

---

500.30 – Enable the workspace TrustServerCertificate option

Most of the time, Devolutions Server returns this 500.30 error when an SQL server (Azure or local) is configured with a self-signed certificate not found in the certificate store.

Solution

In File – Workspaces, choose the workspace experiencing the 500.30 error. Then go to Edit workspace – Advanced and set the TrustServerCertificate to true.

---

500.30 - ASP.NET Core app failed to start

Following the upgrade process, when trying to open the Devolutions Server web page, the browser displays HTTP Error 500.30 - ASP.NET Core app failed to start.

Solution

Verify that Enable 32-bit applications is set to False in the Devolutions Server application pool's Advanced settings in IIS Manager.

If Enable 32-bit applications is already set to false, ensure that the service account designated as the Application pool identity in the Devolutions Server application pool has enough rights on the App_Data subfolder in the Devolutions Server web application folder.

Make sure that the APS.Net Core Hosting Bundle installed on the server where Devolutions Server is hosted is the latest version.

---

500.31 - Failed to load ASP.NET Core runtime

When updating Devolutions Server to the latest version, the web UI displays HTTP Error 500.31 - Failed to load ASP.NET Core runtime. The reason is that the ASP.Net Core version is not updated on the server where Devolutions Server is hosted.

Solution

1. Update the Devolutions Server Console to the latest version.
2. Download the latest ASP.Net Core Module hosting bundle.
3. Install it on the server where Devolutions Server is hosted.

Contact our customer support technicians at [e-mail] if these solutions do not solve your problem.

---

500.37 - ASP.NET Core app failed to start within startup time limit

The Devolutions Server instance is currently unable to establish a connection with the configured Identity provider, preventing the completion of the authentication process. To resolve this issue, please review your network environment and ensure that no firewall settings, proxy rules, or other network configurations are blocking or interfering with the communication between the Devolutions Server host and the Identity provider.

---

503 - The service is unavailable

The 503 error occurs when the web server of Devolutions Server is not reachable. This error can have many causes, it is therefore recommended to use Windows’ Event Viewer to troubleshoot the issue (under Windows Logs – System).