PowerShell Universal failed to start (Timed out waiting for security proxy to start) - Version 2026.3.0

PowerShell Universal failed to start (Timed out waiting for security proxy to start) - Version 2026.3.0

avatar
abang

OS: Linux
Docker Image: devolutions/powershell-universal:2026.3.0-ubuntu-24.04
Note: This container has updated through almost every 2026.* release without any problems causing failed starting
OBS: Image is baked into another image but other versions haven't been a problem

PowerShell Universal fails to start because the security proxy does not become available within the configured startup timeout.

After starting with new imagine

Startup sequence:
- PowerShell Universal begins starting.
- Startup reaches "Starting security service..."
- The security service does not successfully start within 30 seconds.
- PowerShell Universal then aborts startup.
- Reverting to 2026.2.5 successfully starts it again

Displayed error:

PowerShell Universal failed to start. Check the logs for more information.
Failed to load PowerShell Universal. Timed out waiting for security proxy to start. Waited 30 seconds. Consider increasing the SecurityProxyTimeout setting in appsettings.

Expected behavior:
PowerShell Universal should successfully start the security service and complete application startup.

All Comments (7)

avatar
Adam Driscoll

@abang Hello, can you please let me know what you have configured for the default or security environment in settings.ps1? In an unconfigured PSU instance, the security environment is Integrated, meaning it runs in the server process. If the default environment was changed to something else, like PowerShell 7, it requires an external process to start. If that fails for some reason, this issue can happen. One potential work around would be to set the Security environment to Integrated if default is set to something else.

Once we have this tidbit of information, we can investigate further.

Adam Driscoll
PowerShell Expert and Software Architect at Devolutions

avatar
abang

@adriscoll Thanks. Here’s what we had and what fixed it.
Before (failed 2026.3.0 start):

  • DefaultEnvironment = PowerShell 7
  • SecurityEnvironment = PowerShell 7
  • ApiEnvironment = PowerShell 7

Linux Docker (Ubuntu 24.04), SQL backend, Git two-way sync. 2026.2.5 was fine. 2026.3.0 failed at “Starting security service…” (30s security proxy timeout).
SecurityEnvironment = Integrated — container starts, Admin works.
App still did not start: “The app is not yet available on this server node.” No new app logs after upgrade.
All three = Integrated:

  • DefaultEnvironment = Integrated
  • SecurityEnvironment = Integrated
  • ApiEnvironment = Integrated

2026.3.0 then starts fully (Admin + app).
So on this host, PowerShell 7 for Default/Security/API is what breaks 2026.3.0. Security Integrated alone is not enough; Default/API on 7 left the app failed. Integrated for all three is the workaround.

avatar
abang

Issue still in version 2026.3.2

avatar
Adam Driscoll

@abang I've opened an issue for us to track this and see if we can determine why the external PowerShell 7 processes fail to start. I'll update this thread when we have a resolution or any other questions.

Adam Driscoll
PowerShell Expert and Software Architect at Devolutions

avatar
abang

Found another fix
We include this in our image

/etc/apt/conf.d/90curtin-proxy

and these labels in the compose file

       - http_proxy=http://subdomain.domain.local:8080
       - https_proxy=http://subdomain.domain.local:8080
       - HTTP_PROXY=http://subdomain.domain.local:8080
       - HTTPS_PROXY=http://subdomain.domain.local:8080
       - no_proxy=127.0.0.1,localhost,.domain.local,.domain.com


Removing them and setting proxy in

settings.ps1

as

 ProxyUri          = 'http://subdomain.domain.local:8080'

Fixes the problem

avatar
akapsch
@abang I've opened an issue for us to track this and see if we can determine why the external PowerShell 7 processes fail to start. I'll update this thread when we have a resolution or any other questions.


@Adam Driscoll
We also observed that environments other than the Integrated environment fail to start after upgrading. We had to set the execute flag on /opt/psuniversal/Hosts/7.5/PowerShellUniversal.Host. Granted we are on a Linux install and not using a container image, so this might not apply.

1
avatar
akapsch
@abang I've opened an issue for us to track this and see if we can determine why the external PowerShell 7 processes fail to start. I'll update this thread when we have a resolution or any other questions.

@Adam Driscoll
We also observed that environments other than the Integrated environment fail to start after upgrading. We had to set the execute flag on /opt/psuniversal/Hosts/7.5/PowerShellUniversal.Host. Granted we are on a Linux install and not using a container image, so this might not apply.


@Adam Driscoll I can confirm that the execution flag is not set with the built-in PowerShell 7.5 in 2026.3.3.