Hello russellreid1
Thank you for reporting this and for including the comparison with your remote 2026.3.0 instance.
The HTTP/1.x versus HTTP/2 message gives us a useful starting point. Since automatic discovery finds the local instance but operations against it fail, while the remote 2026.3.0 instance works, I would like to compare the local connection and hosting configuration before assuming this is an extension issue.
Could you please confirm the following?
• Exact version of the Devolutions PowerShell Universal VS Code extension currently installed.
• Operating system of the local development machine.
• How the local PSU instance is running, for example Windows service, executable, IIS, Docker, or another method.
• The URL and protocol you normally use to access the local PSU Admin Console, specifically whether it is HTTP or HTTPS.
• Whether you have any custom Kestrel, proxy, TLS, or HTTP protocol configuration on the local instance.
If possible, please also provide the relevant VS Code Output entries from the PowerShell Universal extension and the PSU log entries covering the same failed connection attempt.
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/56197/devolutions-powershell-universal-version-2026300-september-15-2026
Best regards,
Ruben Tapia
rubentapia
This was a PU upgrade of version 2026.1.3.0 which worked with the previous version of the PU VS code extension but did not work with the current 2026.3.0 version of the extension. Which is why i upgraded PU.
VS Code version: 1.137.0 user setup
Devolutions Powerhsell Universal extension: 2026.3.0
Operating system of dev machine: Windows 11 Enterprise 25H2
Local Powershell Universal is running as a windows service
URL: http://localhost:5006 This was the url auto discovered.
I have a xampp portable installation but it is not running. When i do have it running it is using port 80, 443.
I do have Cisco Umbrella and crowdstrike installed per company policy.
Extension error on connect: Failed to connect to http://localhost:5006. PSU request failed (400 Bad Request): An HTTP/1.x request was sent to an HTTP/2 only endpoint.
I found this set of lines in the system log for PU:
2026-09-17 07:00:39.101 -05:00 [INF] Loading configuration files...
2026-09-17 07:00:39.118 -05:00 [INF] Reading configuration for Vault
2026-09-17 07:00:39.235 -05:00 [WRN] HTTP/2 is not enabled for [::]:5000. The endpoint is configured to use HTTP/1.1 and HTTP/2, but TLS is not enabled. HTTP/2 requires TLS application protocol negotiation. Connections to this endpoint will use HTTP/1.1.
2026-09-17 07:00:39.263 -05:00 [INF] Reading configuration for LoggingTarget
2026-09-17 07:00:39.283 -05:00 [INF][UniversalAutomation.Services.UniversalConfigurationService] Reading configuration for Tag
2026-09-17 07:00:39.317 -05:00 [INF][UniversalAutomation.Services.UniversalConfigurationService] Reading configuration for Variable
2026-09-17 07:00:39.541 -05:00 [INF][Microsoft.Hosting.Lifetime] Now listening on: http://[::]:60458
2026-09-17 07:00:39.542 -05:00 [INF][Microsoft.Hosting.Lifetime] Now listening on: http://[::]:5006
2026-09-17 07:00:39.542 -05:00 [INF][Microsoft.Hosting.Lifetime] Now listening on: http://[::]:5000
2026-09-17 07:00:39.542 -05:00 [INF][Microsoft.Hosting.Lifetime] Now listening on: https://[::]:5001
russellreid1
Thank you for the detailed information and the PSU log extract. This helps narrow the issue down considerably.
One important detail is that PSU is actually listening on port 5006, while the HTTP/2 warning in the log specifically references port 5000. The extension is failing against the automatically discovered http://localhost:5006 endpoint, so I do not want to change any HTTP, TLS, Kestrel, Cisco Umbrella, or CrowdStrike settings at this point.
Could you please confirm two additional details?
• What exact URL do you normally use in a browser to successfully access the local PSU Admin Console?
• If available, what was the exact version of the previous VS Code extension that worked with PSU 2026.1.3.0?
The Admin Console URL is particularly useful. If it differs from the automatically discovered http://localhost:5006 endpoint, that will give us a good comparison point and help determine whether the behavior is related to endpoint discovery rather than the PSU service itself.
Once we have that information, I can determine whether the next step should be a controlled local connection test or an internal reproduction against PSU 2026.3.0 and the 2026.3.0 extension.
Because this is a public forum, please continue to sanitize any additional logs or configuration before posting them.
References:
https://forum.devolutions.net/topics/56197/devolutions-powershell-universal-version-2026300-september-15-2026
Best regards,
Ruben Tapia
rubentapia
I use the following url to access the admin console on the local dev instance: https://localhost:5001/admin
The VS Code PU extension that worked with the previous version was Powershell Universal 2026.2.3 not Devolutions Powershell Universal.
