Still Could not load StaticSitesClient metadata from remote after 2.0.4

[Beigmon]

Before filing this issue, please ensure you're using the latest CLI by running swa --version and comparing to the latest version on npm.

Are you accessing the CLI from the default port :4280 ?

• [ ] No, I am using a different port number (--port) and accessing the CLI from that port
• [x] Yes, I am accessing the CLI from port :4280

Describe the bug A clear and concise description of what the bug is. I'm on 2.0.4, latest at this date, trying to deploy an angular app on a SWA using CLI and still have "Could not load StaticSitesClient metadata from remote." error.

And I don't find how to fix it.

I'm using SWA CLI through an org proxy that I did setup in HTTP/S_PROXY variables and I can see it being used in the logs "Using proxy: <the one I want>".

To Reproduce I successfully followed the SWA documentation up to this point :
swa deploy --deployment-token

And then I have the error in the screen above.

Expected behavior Success message or more precise on how to fix this issue.

Desktop (please complete the following information):

• OS: Win11
• Version: 23H2

I already read the previous post of past weeks but still could not manage to make it work.

Thanks for your help.

[sameert89]

Facing the same issue here, it might be related to corporate proxies, but it used to work earlier. Its impacting our workflows.

Meanwhile we have downgraded to 2.0.0

[matiasturunen2]

This issue persists even on 2.0.5

[sovushka-utrom]

Same issue here on 2.0.6.

Tried downgrading to 2.0.2, still getting the same "Could not load StaticSitesClient metadata from remote". Downgrading to 2.0.0 seems to be unsecure according to doc