Apps using Powershell 5.1 won’t start and give an http error 500 in the toast in the admin console (Dashboard 4; Request failed with status code 500). I cannot find error messages about it in the logs. When switching to the integrated environment the apps do start successfully. This was no problem o…

Apps not starting on PSU 4.2.x when using Windows Powershell 5.1, HTTP error 500

JQ1983 February 1, 2024, 3:35pm 8

192.229.221.95 appears to be the CRL of Digicert. So allowing CRL checking through the firewall fixes the problem. Maybe disabling CRL checking will work as well, but I haven’t tested that.

3 Likes

Non-integrated environments are not working

Topic		Replies	Views
Upgrade 2.0.0 -> 2.2.1 - "Error 500" when using PowerShell 7.0.3 PowerShell Universal	4	394	September 1, 2021
2.5.4 PSU service wont start PowerShell Universal	3	406	November 17, 2021
PSU on IIS Host not Loading correctly on the first load - Strange Behavior after Upgrading PowerShell Universal	2	299	March 15, 2023
Unable to start dashboard with Powershell 7 in Azure PowerShell Universal	2	343	April 19, 2021
Unable to Start Dahboards and Run Scripts After Update PowerShell Universal	6	956	March 11, 2021

Apps not starting on PSU 4.2.x when using Windows Powershell 5.1, HTTP error 500

Related Topics