[[["이해하기 쉬움","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 provides general troubleshooting information for Cloud Endpoints configurations, API backends, and response errors, along with links to more detailed guides for specific issues.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003egcloud endpoints services deploy\u003c/code\u003e command typically enables necessary Google services, but manual verification and enabling with \u003ccode\u003egcloud services list\u003c/code\u003e and \u003ccode\u003egcloud services enable\u003c/code\u003e is required if a third-party application or existing disabled services were used.\u003c/p\u003e\n"],["\u003cp\u003eExtensible Service Proxy (ESP) requires permissions to access Service Management and Service Control, and the specific permission setup varies based on the deployment platform such as Cloud Run, Compute Engine, or GKE.\u003c/p\u003e\n"],["\u003cp\u003eRunning the \u003ccode\u003egcloud\u003c/code\u003e command with debug verbosity via \u003ccode\u003egcloud --verbosity=debug COMMAND\u003c/code\u003e offers a way to get more comprehensive error logs for request and response information from the server, to aid debugging.\u003c/p\u003e\n"],["\u003cp\u003eFor gRPC API services, Ensure your configuration file includes an \u003ccode\u003eauthentication\u003c/code\u003e section with the necessary OAuth definitions, like the example provided in the Bookstore sample.\u003c/p\u003e\n"]]],[],null,["# Troubleshooting overview\n\n[OpenAPI](/endpoints/docs/openapi/troubleshoot \"View this page for the Cloud Endpoints OpenAPI docs\") \\| gRPC\n\n\u003cbr /\u003e\n\nThis page provides general troubleshooting information and provides links to\nother pages for additional information.\n\nErrors when deploying the Cloud Endpoints configuration\n-------------------------------------------------------\n\nIf you got an error message from the `gcloud endpoints services deploy`\ncommand, see\n[Troubleshooting Endpoints configuration deployment](/endpoints/docs/grpc/troubleshoot-config-deployment)\nfor information on troubleshooting the error.\n\nErrors when deploying your API backend\n--------------------------------------\n\nThe deployment of your API and the Extensible Service Proxy (ESP) to a\nGoogle Cloud backend is platform dependent. See the\nfollowing troubleshooting guides for more information:\n\n\n- [Troubleshooting proxy deployment on Compute Engine](/endpoints/docs/grpc/troubleshoot-gce-deployment)\n\n- [Troubleshooting proxy deployment on GKE](/endpoints/docs/grpc/troubleshoot-gke-deployment)\n\nResponse errors\n---------------\n\nWhen you send a request to your API and receive an error response, see\n[Troubleshooting response errors](/endpoints/docs/grpc/troubleshoot-response-errors)\nfor information on troubleshooting the error.\n\nChecking required services\n--------------------------\n\n### Checking required services\n\nAt a minimum, Endpoints and ESP require the following Google services to be enabled:\n\nIn most cases, the `gcloud endpoints services deploy` command enables these\nrequired services. However, the `gcloud` command completes successfully but\ndoesn't enable the required services in the following circumstances:\n\n- If you used a third-party application such as Terraform, and you don't\n include these services.\n\n- You deployed the Endpoints configuration to an existing\n Google Cloud project in which these services were explicitly disabled.\n\nUse the following command to confirm that the required services are enabled: \n\n```\ngcloud services list\n```\n\nIf you do not see the required services listed, enable them: \n\n gcloud services enable servicemanagement.googleapis.com\n gcloud services enable servicecontrol.googleapis.com\n\nAlso enable your Endpoints service: \n\n```\ngcloud services enable ENDPOINTS_SERVICE_NAME\n```\n\nTo determine the \u003cvar translate=\"no\"\u003eENDPOINTS_SERVICE_NAME\u003c/var\u003e you can either:\n\n- After deploying the Endpoints configuration, go to the **Endpoints** page in the Cloud console. The list of possible \u003cvar translate=\"no\"\u003eENDPOINTS_SERVICE_NAME\u003c/var\u003e are shown under the **Service name** column.\n\n- For OpenAPI, the \u003cvar translate=\"no\"\u003eENDPOINTS_SERVICE_NAME\u003c/var\u003e is what you specified in the `host` field of your OpenAPI spec. For gRPC, the \u003cvar translate=\"no\"\u003eENDPOINTS_SERVICE_NAME\u003c/var\u003e is what you specified in the `name` field of your gRPC Endpoints configuration.\n\nFor more information about the `gcloud` commands, see\n[`gcloud` services](/sdk/gcloud/reference/services).\n\nChecking required permissions\n-----------------------------\n\nThe instance running Extensible Service Proxy requires permissions to call [Service Management](/service-infrastructure/docs/service-management/getting-started) and [ServiceControl](/service-infrastructure/docs/service-control/getting-started).\n\n- For ESP deployed on Cloud Run, see [Building a new ESPv2 image in Cloud Run tutorial](/endpoints/docs/openapi/set-up-cloud-run-espv2#configure_esp) for details.\n\n- For ESP deployed on Compute Engine, see [Checking required permissions in Compute Engine tutorial](/endpoints/docs/openapi/get-started-compute-engine-docker#checking_required_permissions) for details.\n\n- For ESP deployed on GKE, see [Checking required permissions in GKE tutorial](/endpoints/docs/openapi/get-started-kubernetes-engine#checking_required_permissions) for details.\n\nChecking debug information\n--------------------------\n\nRunning the Google Cloud CLI with debug verbosity helps with\ndebugging. \n\n gcloud --verbosity=debug COMMAND\n\nThis command makes the Google Cloud CLI print a verbose log of the\nerror. Depending on the command being run, the output can include request and\nresponse information from the server.\n\nEnabling a service\n------------------\n\nYou can check whether a service is enabled using `gcloud`. \n\n gcloud services list\n\nTo display configuration for a particular service, use the following command: \n\n gcloud endpoints services describe SERVICE_NAME\n\nProxy OAuth fails yet requests pass\n-----------------------------------\n\nMake sure there is an `authentication` section that has your OAuth definition in\nyour gRPC API configuration file. An example configuration file is\navailable in the\n[Bookstore sample on GitHub](https://github.com/GoogleCloudPlatform/python-docs-samples/blob/master/endpoints/bookstore-grpc/api_config_auth.yaml).\n\nWhat's next\n-----------\n\n- [Monitoring your API](/endpoints/docs/grpc/monitoring-your-api)\n- [Tracing your API](/endpoints/docs/grpc/tracing)"]]
