Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SF commands failing with "Destination URL not reset. The URL returned from login must be set #3026

Closed
alecdorner opened this issue Sep 18, 2024 · 2 comments

Comments

@alecdorner
Copy link

Summary

sf commands using the Use an Existing Access Token are failing with the "Destination URL not reset. The URL returned from login must be set" error.

Steps to Reproduce:

  1. Get the access token from any sandbox org you are logged in
  2. Run any SF command using the access token as the --target-org parameter

Expected Result

  1. The command is successful in using the access token

Actual Result

  1. The command fails noting an error "Destination URL not reset. the URL returned from login must be set"

System Information

@salesforce/cli 2.42.6 (core)
@oclif/plugin-autocomplete 3.0.18 (core)
@oclif/plugin-commands 3.3.4 (core)
@oclif/plugin-help 6.0.22 (core)
@oclif/plugin-not-found 3.1.9 (core)
@oclif/plugin-plugins 5.0.21 (core)
@oclif/plugin-search 1.0.24 (core)
@oclif/plugin-update 4.2.12 (core)
@oclif/plugin-version 2.1.2 (core)
@oclif/plugin-warn-if-update-available 3.0.19 (core)
@oclif/plugin-which 3.1.10 (core)
apex 3.1.11 (core)
auth 3.6.11 (core)
data 3.3.5 (core)
deploy-retrieve 3.6.14 (core)
info 3.2.8 (core)
limits 3.3.7 (core)
marketplace 1.2.5 (core)
org 4.1.10 (core)
packaging 2.4.4 (core)
schema 3.3.6 (core)
settings 2.2.6 (core)
sobject 1.4.2 (core)
source 3.3.12 (core)
telemetry 3.3.7 (core)
templates 56.2.7 (core)
trust 3.6.11 (core)
user 3.5.8 (core)

Uninstalled JIT Plugins:
community 3.2.10
custom-metadata 3.3.7
dev 2.3.1
devops-center 1.2.10
env 3.0.30
functions 1.23.0
signups 2.3.1
@salesforce/sfdx-plugin-lwc-test 1.2.0
@salesforce/sfdx-scanner 3.24.0

@WillieRuemmele
Copy link
Member

WillieRuemmele commented Sep 18, 2024

Hi @alecdorner -

did you set the org-instance-url config like required in step 3 of the posted link?

before I set that I was seeing the same error, once I set it, using the access token began to work as expected

@alecdorner
Copy link
Author

@WillieRuemmele oh goodness, I definitely missed that step and that cleared up the issue. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants