Cli: Can't Update - Error: HTTP 403: Invalid channel stable

Created on 9 Jan 2021  Â·  19Comments  Â·  Source: forcedotcom/cli

Summary

Can't Update sfdx - HTTP 403: Invalid channel stable

image

Steps To Reproduce:

No idea. The update command never failed with this error message.

Expected result

sfdx update should update the cli or a least tell exactly what is the problem.

Actual result

sfdx update returns

Error: HTTP 403: Invalid channel stable

Additional information

SFDX CLI Version: 7.81.0 linux-arm64 node-v14.15.0
OS and version: Ubuntu 20

investigating

Most helpful comment

So it looks like wsl-x64 and linux-arm64 are platforms that are not available in the manifest.json file. Does this means these platforms are no longer supported? I've been using the CLI on WSL for quite a long time without any problems.

Here is another issue with the same underlying problem: #610

All 19 comments

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

@AllanOricil - Thanks for reporting. Can you please try again and close this issue if it works for you? I believe I just fixed it.

@shetzel the error is still happening

image

@AllanOricil can you run with --dev-debug? More specifically I want to know what URL it is failing on. Can you access https://developer.salesforce.com/media/salesforce-cli/manifest.json from your terminal?

Here is the output. Maybe your service is blocking because of the user agent?
image
image

And I can access that json from the url
image

I also noticed that I can't perform Web OAuth flow from that machine. It might be related. After entering the login credentials it stays loading forever a link. And when I refresh that link it says that an error happened.

I'm also having this exact problem but from WSL. I actually uninstalled WSL and started from scratch only to run into the issue again. Here is the error from the debug output.

image

So it looks like wsl-x64 and linux-arm64 are platforms that are not available in the manifest.json file. Does this means these platforms are no longer supported? I've been using the CLI on WSL for quite a long time without any problems.

Here is another issue with the same underlying problem: #610

So it looks like wsl-x64 and linux-arm64 are platforms that are not available in the manifest.json file. Does this means these platforms are no longer supported? I've been using the CLI on WSL for quite a long time without any problems.

I think they are just missing. Because sfdx is based on Oclif which is written for Node which supports these platforms.

@AllanOricil were you able to get Web OAuth flow to work at all? That is my main issue right now. Appears to overlap with #783. I'll try the workaround suggested there.

@AllanOricil were you able to get Web OAuth flow to work at all? That is my main issue right now. Appears to overlap with #783. I'll try the workaround suggested there.

No :/

So I moved over to the npm installation method, but the latest version of the CLI also fails to successfully web auth there as well. Downgrading to 7.76.0 seemed to do the trick.

So I moved over to the npm installation method, but the latest version of the CLI also fails to successfully web auth there as well. Downgrading to 7.76.0 seemed to do the trick.

@mrichmon12 How did you uninstalled the binary? Im not that familiar with linux commands yet haha

@amphro @mrichmon12 I solved my problem uninstalling sfdx-cli completly and installing it again with npm.
I followed this tutorial

image

But

I can't run the update command. It still outputs the same error message

image

I can't run the update command. It still outputs the same error message

@AllanOricil As per the Salesforce CLI Setup Guide, when installed via npm you should use npm install --global sfdx-cli to update.

If you are looking for a specific version you can specify the version number as well (e.g.: npm install --global [email protected])

When I downgraded to 7.76.0 my OAuth issues were resolved.

The sfdx update doesn't work for npm installs and will output why. The fact that you are still getting that error @AllanOricil implies that it is still running the installer version. What is the output of which sfdx?

The sfdx update doesn't work for npm installs and will output why. The fact that you are still getting that error @AllanOricil implies that it is still running the installer version. What is the output of which sfdx?

@amphro I made sure to have everything uninstalled before installing again with npm. It is running the npm "version".

image

It looks like it must be checking the manifest before indicating it should be updated using npm?

~ sfdx update                                                                                                                                                                                                                 
sfdx-cli: Updating CLI... !
    Error: HTTP 403: Invalid channel stable
~ which sfdx                                                                                                                                                                                                                
/home/mrichmond/.nvm/versions/node/v14.15.4/bin/sfdx

That is odd. The right way to update an npm installed version is to use npm.

I see it is checking the channel then outputting the message:

➜ sfdx update
https://developer.salesforce.com/media/salesforce-cli/sfdx-cli/channels/stable/darwin-x64
{
  version: '7.84.2-a2868a68d5',
  channel: 'stable',
  sha256gz: 'f4b3b318f04b3abdb03f2e13419a0d093ccb94d33b15d174fdf0f0683f629069',
  sha256xz: '67e8eda6613350f39b5d700d84ab3e6ef0c3b95f758197de5bf99d3a4d08b3af',
  node: { compatible: '>=8.10.0', recommended: '12.18.3' }
}
 ›   Warning: Use "npm update --global sfdx-cli" to update npm-based installations.
sfdx-cli: Updating CLI... not updatable
sfdx-cli: Updating plugins... done

Can you run with --dev-debug?

Was this page helpful?
0 / 5 - 0 ratings