Gcloud Compute SSH连接实例与证书+PuTTY连接实例不一致问题

DevOps 小满

2026-5-25

Troubleshooting: Logging into the Wrong GCP Instance on Mac

Hey there! It sounds like you’re connecting to a totally different instance than the dev one you used on Windows—let’s sort this out step by step:

1. Confirm your active GCP project

First up, make sure you’re working in the same project where your dev instance lives. Run this command to check your current project:

gcloud config get-value project

Compare the output to the project ID you used on your Windows machine. If it’s not a match, switch to the correct project with:

gcloud config set project YOUR_DEV_PROJECT_ID

2. List all instances in your project

Next, verify your dev instance exists in the project and note its name and zone. Run this command to see all instances:

gcloud compute instances list

Look for the instance name you remember from your Windows setup—you’ll need its zone (like us-central1-a) for the next step.

3. SSH directly to your target instance

Instead of relying on default settings, explicitly specify your dev instance and zone when connecting. Use this command, replacing the placeholders with your actual details:

gcloud compute ssh YOUR_DEV_INSTANCE_NAME --zone YOUR_INSTANCE_ZONE

This ensures you’re connecting straight to the instance with all your installed packages and scripts.

4. Check your authenticated account

It’s possible you’re logged into a different GCP account on your Mac. Verify your current account with:

gcloud config get-value account

If this isn’t the same account you used on Windows, switch accounts by running:

gcloud auth login

Then follow the prompts to sign in with your correct GCP credentials.

5. Double-check SSH key setup (if needed)

If your Windows PuTTY setup used a specific certificate, you might need to sync your Mac’s SSH keys with GCP. Run this command to add your local public key to your instances’ metadata: