PSU commands failing with SSL connection error

Hello @akapsch

Thank you for reporting this.

There is currently an active 2026.3.x issue involving PSU cmdlet behavior and Integrated mode that Development is investigating. However, I do not want to assume that the SSL error you are seeing is caused by the same issue, especially since in your case adding -Integrated appears to work around the problem for the cmdlets that support it.

Could you please confirm the following?
• Exact PSU version affected, for example 2026.3.0, 2026.3.1, or 2026.3.2
• Hosting method, such as Windows Service, IIS, Linux service, or Docker
• Where these commands are being executed, such as an App, Script, API Endpoint, or Admin Terminal
• The last PSU version where these same commands worked correctly
• The complete inner exception associated with "The SSL connection could not be established"

The inner exception will be particularly useful to determine whether this is related to certificate validation, TLS, the connection target, or the recent PSU cmdlet changes.

Because this is a public forum, please sanitize all evidence before posting. Remove credentials, tokens, license keys, cookies, private keys, full connection strings, email addresses, usernames, customer data, tenant or account identifiers, internal domains, hostnames, IP addresses, and private URLs. Please do not upload unredacted HAR files, memory dumps, database backups, or complete configuration files to this public thread.

References:
https://forum.devolutions.net/topics/56212/integrated-mode-intermittently-fails-with-you-must-be-running-this-com

Best regards,
Ruben Tapia

Hi Ruben,

• We have observed this on 2026.3.0 through 2026.3.2
• We run PSU as a Linux service
• These commands are in an app page
• We were previously on 2026.1.5
• The logs only say The SSL connection could not be established, see inner exception.. Where can I find the inner exception?

I believe I have more to add to this. I have observed that if I don't include the -Integrated parameter with some cmdlets, that they will run forever until the page runs out of memory. Since they never end, -ErrorAction Stop doesn't take effect and the code never drops into the catch block. Below is the code I am using to test. If -Integrated on both Get-PSUScript and Get-PSUSchedule, it runs fine. If I don't include -Integrated on either, the page runs out of memory with "Insufficient memory to continue the execution of the program.". When this happens, no errors appear in the logs. I'm assuming they are throwing the SSL error, but I can't confirm.

It also appears that Get-PSUSchedule has the -Integrated parameter implemented, but it is not in the current docs: Get-PSUSchedule | Devolutions PowerShell Universal | Product guides & reference

New-UDPage -Url '/pageurl' -Name 'Bug Demonstration' -Content {
  $ScriptName = 'GenerateReport.ps1'
  New-UDStack -Spacing 2 -Direction 'column' -Content {
    New-UDDynamic -Content {
      try {
        $Script = Get-PSUScript -Name $ScriptName -ErrorAction Stop #-Integrated
        $Schedule = Get-PSUSchedule -Script $Script #-Integrated

        New-UDElement -Tag 'div' -Content {
          'Next run: '
          New-UDDateTime -InputObject $Schedule.NextExecution
        }
      } catch {
        New-UDElement -Tag 'div' -Content {
          'Error: '
          $_
        }
      }
    } -LoadingComponent {
      New-UDProgress -Circular
    }
  }
}

Hello @akapsch

Thank you for the additional details and for sharing the test example.

This gives me a much clearer picture of the behavior, especially the difference between running the cmdlets with and without -Integrated, as well as the memory exhaustion you observed when the calls do not return.

I am going to adjust my lab testing based on this update so I can better match your environment and the behavior you are seeing across 2026.3.0 through 2026.3.2.

I will update the thread once I have completed the revised testing.

Best regards,
Ruben Tapia

Hello @akapsch

Thank you again for the detailed information.

We completed our internal testing across PSU 2026.3.0, 2026.3.1, and 2026.3.2. We were not able to reproduce the SSL error, hanging behavior, or memory growth you reported. Our isolated environment encountered authentication/context differences before reaching the same API and TLS path as your App, so additional internal reproduction would not provide a meaningful comparison.

Could you please perform one targeted test from your App?

For either Get-PSUScript or Get-PSUSchedule, please run the same call without -Integrated but explicitly provide -ComputerName using the HTTPS URL through which your PSU instance is normally accessed. Then compare that result with the current call where PSU determines the API URL automatically.

Please let me know whether the explicit -ComputerName call:

• Succeeds
• Returns the same SSL error
• Hangs
• Returns a different error

Also, please confirm whether API:URL is explicitly configured, which API SecurityModel is in use, whether a reverse proxy or TLS termination is present, and whether the endpoint certificate is trusted by the Linux host running PSU.

There is no need to post the actual private URL, hostname, certificate, token, or other sensitive values.

Because this is a public forum, please sanitize all evidence before posting. Remove credentials, tokens, license keys, cookies, private keys, full connection strings, email addresses, usernames, customer data, tenant or account identifiers, internal domains, hostnames, IP addresses, and private URLs. Please do not upload unredacted HAR files, memory dumps, database backups, or complete configuration files to this public thread.

References:
https://docs.devolutions.net/powershell-universal/config/module

Best regards,
Ruben Tapia