이 페이지에서는 App Engine의 일반적인 앱 초기화 및 서빙 오류와 이를 해결하는 방법을 설명합니다.
기본 서비스 계정으로 앱을 만들 때의 권한 오류
App Engine API를 처음 사용 설정한 후 앱을 만들면 다음과 같은 오류가 표시되면서 실패할 수 있습니다.
gcloud CLI
An internal error occurred while calling service consumer manager for service account.
Creating App Engine application in projectPROJECT and REGION....failed. DEBUG: (gcloud.app.create) Error Response: [13] an internal error has occurred
로그 요청
Service account creation is not allowed on this project.
이 문제를 해결하려면 App Engine 기본 서비스 계정을 만들고 배포할 수 있도록 조직 정책 제약조건 constraints/iam.disableServiceAccountCreation을 일시적으로 삭제해야 합니다. 기본 서비스 계정은 앱을 만들 때 필요하며 건너뛸 수 없습니다. 버전별 서비스 계정을 사용할 때도 마찬가지입니다.
App Engine 기본 서비스 계정을 삭제하거나 배포가 성공한 후에 만든 서비스 계정으로 바꿀 수 있습니다.
만든 서비스 계정을 사용하는 경우 역할 권장사항 개요를 검토하여 서비스 에이전트에 만드는 서비스 계정에 대한 토큰 생성자 역할 제공과 같이 권한을 제한하는 방법을 알아봅니다.
Python용 기존 번들 서비스를 사용할 때 발생하는 보안 오류
Python 3 앱이 시작될 때 레거시 번들 서비스 API를 사용하는 경우 다음과 같은 오류 메시지가 표시될 수 있습니다.
Attempted RPC call without active security ticket
이 오류는 앱이 데이터베이스 연결을 구성하거나 전역 변수를 설정하기 시작할 때 Memcache에서 특정 값을 읽는 등의 시나리오에서 발생할 수 있습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003eThis page details common errors encountered during App Engine app initialization and serving, along with their troubleshooting methods.\u003c/p\u003e\n"],["\u003cp\u003eA permission error can occur when creating an App Engine app due to the organization policy constraint \u003ccode\u003econstraints/iam.disableServiceAccountCreation\u003c/code\u003e, which prevents the creation of the default service account.\u003c/p\u003e\n"],["\u003cp\u003eTo resolve the default service account creation error, temporarily remove the \u003ccode\u003econstraints/iam.disableServiceAccountCreation\u003c/code\u003e policy to allow for its provisioning, as it is required during app creation.\u003c/p\u003e\n"],["\u003cp\u003eWhen using legacy bundled services with Python 3 apps, a security error ("Attempted RPC call without active security ticket") may arise, particularly when accessing services like Memcache during startup.\u003c/p\u003e\n"],["\u003cp\u003eTo fix the security errors when using legacy bundled services, move the logic that causes the error to a warmup request.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot serving issues in App Engine\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\nThis page describes common app initialization and serving errors in\nApp Engine and methods to troubleshoot them.\n\n### Permission error when creating an app with the default service account\n\nWhen you create an app after enabling the\nApp Engine API for the first time, it might fail with the following errors: \n\n### gcloud CLI\n\n An internal error occurred while calling service consumer manager for service account.\n Creating App Engine application in project\u003cvar translate=\"no\"\u003ePROJECT\u003c/var\u003e and \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e....failed. DEBUG: (gcloud.app.create) Error Response: [13] an internal error has occurred\n\n### Request logs\n\n Service account creation is not allowed on this project.\n\n### Console\n\n Error while initialising App Engine.\n\nThis error might occur due to the enforcement of the organization policy constraint [`constraints/iam.disableServiceAccountCreation`](/resource-manager/docs/organization-policy/restricting-service-accounts#disable_service_account_creation) when creating your\napp. This policy prevents the provisioning of the [App Engine default service account](/appengine/docs/standard/configure-service-accounts) `PROJECT_ID@appspot.gserviceaccount.com`.\n\nTo resolve this issue, you must temporarily remove the organization policy\nconstraint `constraints/iam.disableServiceAccountCreation` to allow for the\ncreation and deployment of the App Engine default service account. The default\nservice account is necessary for app creation and can't be skipped. This is also\napplicable when you use a per-version service account.\nThe App Engine default service account can be deleted or replaced\nwith a service account that you create after successful deployment.\n\nIf you are using a service account that you created, review the [Overview of role recommendations](/policy-intelligence/docs/role-recommendations-overview)\nto understand how to enforce restricting permissions, such as providing a\ntoken creator role on the service account you create for the service agent.\n\n### Security errors when using legacy bundled services for Python\n\nIf you use a legacy bundled services API when a Python 3 app is starting up,\nyou might see the following error message: \n\n Attempted RPC call without active security ticket\n\nThis error might occur in scenarios such as, reading certain values from\n[Memcache](/appengine/docs/standard/services/memcache) when your app is starting\nto configure a database connection or set a global variable.\n\nTo resolve this issue, you could try moving such logic into a\n[warmup request](/appengine/docs/standard/configuring-warmup-requests)."]]
