This message was deleted.

Hello @few-lizard-48557 , could you run

pulumi about

for me and paste the results?

This looks similar to this issue: https://github.com/pulumi/pulumi/issues/3590 Your

pulumi about

output mentions that it can’t find

npm

. Does NodeJS start correctly when you run

node -v

separately?

Hi Ringo and thank you for your feedback. Nodejs runs at this machine proper with several Repos.

node -v

shows: V14.16.0

@few-lizard-48557 for

pulumi about

, any reason it can’t find

npm

on your system?

Hi Ringo, I just checked the link you forwarded but I'm not sure whether I do fully understand the information which is posted. I have an authentification proxy (px.exe) installed. The configuration of this proxy (px.ini) is the following:

The

noproxy

line is what I was after. Pulumi uses a network GRPC protocol to communicate between the language host, the engine and the provider binaries, all locally on your machine. If these network connections, albeit locally, are obstructed, then Pulumi doesn’t work correctly. In your case, the proxy is correctly configured as far as I can see, not to proxy for connections on your own machine

127.0.0.*

and internal private networks

10.*.*.*

,

192.68.*.*

.

I have now added "127.0.0.1" and "localhost" to the `noproxy`configuration, restarted the console and tried

pulumi up

again => unfortunately without success... (That was just a helpless attempt from my side)

Unfortunately not at the moment. This week, Pulumi is having a company wide refresh week. I can’t consult any of the core engineers this week unfortunately.

Hello Ringo, your tip with the proxy configuration was a hot tip for me and I would like to thank you expressly for it and I have also been able to find out in the meantime where exactly the dog is buried in the proxy configuration. So here is the resolution to the proxy configuration for my computer in the hope that it may still be useful for others... So the whole proxy configuration is apparently a 2-stage thing, i.e. on the one hand there are entries in the environment variables which are

HTTP_PROXY: <http://127.0.0.1:3128>

and `HTTPS_PROXY: http://127.0.0.1:3128`which on my computer forward to the authentication proxy (Px.exe) which listens on port 3128. In addition, there is an further proxy entry

NO_PROXY: localhost,.<http://bosch.com|bosch.com>,.<http://bosch-iot-cloud.com|bosch-iot-cloud.com>

in the environment variables. In NO_PROXY the entry 127.0.0.1 is missing on my system, which probably means that the requests for this ip are forwarded to the PX proxy. This is the case for the GRPC communication between the language host and the engine, but the PX proxy has configured an exclusion for 127.0.0.1 and somehow the instances involved cannot handle this in a proper way... I have now added the exclusion "127.0.0.1" to the environment variable

NO_PROXY: 127.0.0.1,localhost,.<http://bosch.com|bosch.com>,.<http://bosch-iot-cloud.com|bosch-iot-cloud.com>

, which probably means that a request to this address will not be forwarded to the PX.exe proxy and everything now works as expected, i.e. by calling the command

Pulumi up

I get a preview of all Azure resources that are created during the call. Many thanks again for the fast and good support!

Glad I could help you out! Have fun with Pulumi.

👍

This one was worth mentioning on our Troubleshooting page. https://github.com/pulumi/pulumi-hugo/pull/1797