Troubleshooting

Learn about troubleshooting steps that you might find helpful if you run into problems using App Engine.

Deployment errors

This section lists error messages that you may see when you deploy your app and provides suggestions for how to fix each error.

The caller does not have permission to access project

User EMAIL_ADDRESS does not have permission to access project PROJECT_ID (or it may not exist): The caller does not have permission
Description: This error occurs if the account that you used to deploy your app (EMAIL_ADDRESS) does not have permission to deploy apps for PROJECT_ID.
Solution: Grant the "App Engine Deployer" role to the account. To see which account you used to deploy:
  • If you used the gcloud command-line tool to deploy, run the gcloud auth list command.
  • If you deployed from an IDE, view the settings for the Cloud Tools plugin.

Failed to fetch metadata from GCR

Failed to fetch metadata from GCR, with reason: generic::permission_denied
Description: This error occurs if you use the gcloud app deploy command from a service account that does not have the "Storage Admin" role.
Solution: Grant the "Storage Admin" role to the service account. To see which account you used, run the gcloud auth list command. To learn why assigning only the "App Engine Deployer" role may not be sufficient in some cases, see App Engine roles.

Service accounts must have permissions on the image

The App Engine appspot and App Engine flexible environment service accounts must have permissions on the image IMAGE_NAME
Description: This error occurs when the default App Engine service account does not have the "Storage Object Viewer" role.
Solution: Grant the "Storage Object Viewer" role to the service account.

Failed to create cloud build

Failed to create cloud build: Permission denied
Description: This error occurs if you use the gcloud app deploycommand from an account that does not have the "Cloud Build Editor" role.
Solution: Grant the "Cloud Build Editor" role to the service account that you are using to deploy your app. To see which account you used, run the gcloud auth list command.

Permissions error fetching application

Permissions error fetching application apps/app_name. Please make sure you are using the correct project ID and that you have permission to view applications on the project
Description: This error occurs if the account you used to deploy your app doesn't have the "App Engine Deployer" role.
Solution: Verify that you have granted the "App Engine Deployer" role to the service account that you used to deploy your app; grant the role if the service account does not have it. To see which account you used to deploy:
  • If you used the gcloud command-line tool to deploy, run the gcloud auth list command.
  • If you deployed from an IDE, view the settings for the Cloud Tools plugin.

Timed out waiting for the app infrastructure to become healthy

Timed out waiting for the app infrastructure to become healthy
Description: This error occurs in the Flexible environment. Various factors can cause this error, such as missing permissions, code errors, insufficient CPU or memory, or failed health checks.
Solution: To rule out potential causes:
  1. Verify that you have granted the "Editor" role to your default App Engine Service Account; grant the role if the service account does not have it.
  2. Check whether the organization policy for your project restricts access to external IPs. For more information, see App Engine Flexible known issues.
  3. Verify that you have granted the following roles to the service account that you use to run your flex application (usually the default service account, app-id@appspot.gserviceaccount.com): Grant the roles if the service account does not have them.