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
