I’ve downloaded and installed the MSI and the service is running and I can log in to the web portal.
I’ve then downloaded and added the VS code extension. My Admin account doesn’t have internet access.
I’ve generated an app token, kept it as localhost as VS code is on the same machine and port 5000.
But when I launch the extension, it says
“Failed to connect to PowerShell Universal. You can configure the connection information in settings.”
I can see the correct URL in the bottom left “connecting to PowerShell universal at http://localhost:5000…”
Are there any debug logs I could use to find out why its not connecting?
You will want to update your settings for the extension.
It looks like it’s trying to start the PSU server itself. Open the settings by pressing Ctrl+Shift+P and searching for the settings UI. There will be a section for PowerShell Universal.
You can set the extension to not start PSU and you can reset the app token as well.
It is running 443, with the port configured i get the same error.
When i run the dashboard on port 80, without the port configured in the settings, the extension can connect. Disadvantage is that Azure oidc authentication responds with an error 500. The port 80 redirect url is configured within my app registration. Is it possible it is having difficulty with the certificate? Powershell universal is running locally and i used dotnet to generate certificates.
For my problem i got the following workaround. By having the dashboard running at port 80 and 443 the extension is allowed to connect and i can access the website through 443.