Most of us have this issue with Authorization command. Something may be broken in cli.
One workaround is with this command:
// authorize production org
// authorize sandbox
sfdx auth:device:login -r https://test.salesforce.com
// authorize devhub
sfdx auth:device:login -d -a <devhub alias>
Here is the link to related issue in ...
This was my solution, https://superuser.com/questions/1579346/many-excludedportranges-how-to-delete-hyper-v-is-disabled
I had to stop the winnat service with the following command via an elevated administrator command line:
net stop winnat
The reserved port range shows up via the netsh command but the specific 1717 port isn't seen as open by netstat
Administered Port Exclusions are the reason.
In the Salesforce CLI log, you also see:
error: listen EACCES: permission denied 127.0.0.1:1717
Run this in a Cmd Prompt:
> netsh interface ipv4 show excludedportrange protocol=tcp
Protocol tcp Port Exclusion Ranges
Start Port End Port
Logging into the DevHub won't activate the SOQL Builder. You will need to do an 'SFDX: Authorize an org' as well to make sure you are logged in and a default org is set for the SOQL Builder to work.
Check here for info on how to perform authorization to make sure your VSCode is connected to the Salesforce org.
You need to use a different URL from the Authentication Provider.
Go to your auth. provider
expand Experience Cloud Sites
scroll down and find the name of your site/community. There should be a different SSO URL for your community
As of today (12.09.2021) my observation is that Deploy option in context menu depends to what kind of org you are connected/authorized to (which one is set as a default one).
If it is a sandbox -> You will have a deploy option available. If it will be a scratch org it will be covered by a SFDX: Push sources to the scratch org. I believe that plugin ...