This message was deleted.
# general
s
This message was deleted.
w
Is there a chance that you're running through a corporate proxy?
b
What happens when you go to https://api.pulumi.com in a browser?
p
I’m on my home network and turned the firewall off just for fun. I can hit the api. Thanks for the help.
Copy code
curl <https://api.pulumi.com/api/user>
{"code":401,"message":"Unauthorized: No credentials provided or are invalid."}
w
Are you saying that you've worked it out?
p
no, any time i use the pulumi cli it times out
but i can curl the same endpoint
w
Times out at the CLI handshake?
*TLS
p
it seems so from the error message
i can
az login
with out any issue
w
My only thought is an edge proxy, and they've bypassed the microsoft domains. Curl is also maybe bypassing and the CLI is using a system proxy.
p
im not running any vpn/proxy/etc. Pretty vanilla set-up and I turned my router and mac firewalls off to troubleshoot
Copy code
$ telnet <http://api.pulumi.com|api.pulumi.com> 443
Trying 35.160.203.13...
Connected to <http://api.pulumi.com|api.pulumi.com>.
Escape character is '^]'.
Copy code
$ pulumi login
Logging in using access token from PULUMI_ACCESS_TOKEN
error: problem logging in: getting user info from <https://api.pulumi.com>: performing HTTP request: Get "<https://api.pulumi.com/api/user>": net/http: TLS handshake timeout
anything else I can check?
w
I'm out I'm afraid... Possibly one of the pulumi folks.
p
thank you
b
@plain-spoon-93851 can you raise an issue in https://github.com/pulumi/pulumi for this please
p