This message was deleted.

I think more details will be needed to help out here. Certainly you will need to be able to reach both

<http://api.pulumi.com|api.pulumi.com>

as well as cloud provider provisioning endpoints. And also ability to write to the current user home directory.

That’s 3 possibilities all rolled into a single 401

3 possibilities

3 possibilities for what?

API.pulumi.com is 404 from my mobile?

There is nothing served from the root of https://api.pulumi.com/ - so that is expected. https://api.pulumi.com/api/user is a legal endpoint, but needs to be authenticated so you will receive a 401. What are you trying to do?

I thought api.pulumi.com was an endpoint that I should be checking as it was suggested? If it is not there why are you suggesting that is an endpoint to check? Or have I misunderstood?

I thought api.pulumi.com was an endpoint that I should be checking as it was suggested?

As what suggested?

If it is not there why are you suggesting that is an endpoint to check?

Who is suggesting that?

Thanks Luke but I have not been able to connect from corporate environment to try your gist and those are the error messages as pointed out. Pulumi up Logging in using access token from PULUMI_ACCESS_TOKEN Error: invalid access token Pulumi Logout Generated new token Pulumi Login Logging in using access token my from PULUMI_ACCESS_TOKEN Logged into pulumi.com as .... Mkdir testdir && cd testdir As per instructions, pull project created in portal pulumi new aws-typescript -s niceseb/aurora-lambda/dev Error: authorization failed And similarly pulumi up from a locally typescript generated folder Pulumi up Can’t find module grpc_node.node

Any chance you can share the exact output you are seeing in each step? It looks like you are sharing approximations of the output, which makes it a little hard to understand exactly what’s going on.

Result from pulumi up above after successful whoami

That looks like you had an

npm install

fail related to the gRPC package. You can try deleting

node_modules

and re-running

npm install

. If you get any failures again from that - please share here.

Npm install grpc separately?

I can’t tell from that screenshot what the original error was - but this appears to be an issue with installing gRPC on your Windows environment. I suspect the actual error is a few lines earlier.

After login now I followed project creation and then error: authorization the moment when pulling down project to local machine? Could this be company firewall?