You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

使用googleComputeEngineR调用gce_get_project()遇403权限错误求助

Troubleshooting 403 Error with googleComputeEngineR & GCE

Hey there, let's work through this 403 error together—since you're new to GCP, it's totally normal to hit these small hiccups! Let's break down targeted steps to fix this based on what you've already tried:

1. Confirm you're targeting the correct GCP project

It's easy to accidentally enable the API in a different project than the one R is using. Let's cross-verify:

  • In your terminal, run gcloud config get-value project to see gcloud's default project ID.
  • In R, run Sys.getenv("GCE_DEFAULT_PROJECT_ID") to check the project set in your .Renviron.
  • If they don't match, run gcloud config set project YOUR_CORRECT_PROJECT_ID in the terminal, then restart RStudio to apply the update.

2. Check your authentication credentials have proper permissions

Even if auto-auth succeeded, your credentials might lack access to Compute Engine resources:

  • Head to the GCP Console's IAM page for your project.
  • Locate the account you're using (this could be the default Compute Engine service account, or your personal GCP account if you used gcloud auth login).
  • Ensure the account has at least the Compute Viewer role (or Compute Engine Admin for full access). If not, add the role and wait 1-2 minutes for permissions to propagate.

3. Force refresh credentials and clear cached API state

The googleComputeEngineR package might be using outdated cached data from before you enabled the Compute Engine API. Try these commands in R:

# Re-authenticate to pull fresh credentials
gce_auth()

# Clear cached project data and retry the request
gce_get_project(clear_cache = TRUE)

Also, restart RStudio entirely to wipe any lingering old environment variables or cached data.

4. Wait for API enablement to fully propagate

GCP sometimes takes 5-10 minutes for API enablement to take full effect, especially on brand-new projects. If you just enabled the Compute Engine API recently, give it a little time before retrying.

5. Double-check your .Renviron configuration

Make sure your .Renviron file has the correct entries (open it with usethis::edit_r_environ()):

GCE_DEFAULT_PROJECT_ID=xxx
GCE_DEFAULT_ZONE=your-preferred-zone # e.g., us-central1-a

Save the file, then restart RStudio—environment variables won't update until you restart the session.

Since your gcloud compute instances list command works, we know your core GCP setup is functional. The issue is almost certainly a misalignment between R's project target, credentials, or cached API state.

内容的提问来源于stack exchange,提问作者jonnyf

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.05.07 06:42:35