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?