No service YOUR_PROJECT_ID.appspot.com found or permission denied.If this is a new Endpoints service, make sure you've deployed the service config using gcloud.
app.yaml ファイルで指定されたサービスのサービス構成を読み込めない場合に Endpoints Frameworks for Python がこのエラーをログに記録します。このエラーは、gcloud endpoints services
deploy を使用して API の OpenAPI ドキュメントをまだデプロイしていない場合、または Service Management API が有効になっていない場合に発生することがあります。API の OpenAPI ドキュメントをデプロイすると、gcloud コマンドによって自動的に以下が有効化されます。
Service Management API（servicemanagement.googleapis.com）
[[["わかりやすい","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\u003eCloud Logging helps troubleshoot unsuccessful responses from Cloud Endpoints Frameworks APIs, accessible via the Logs Explorer in the Google Cloud console.\u003c/p\u003e\n"],["\u003cp\u003eA \u003ccode\u003e503 Service Unavailable\u003c/code\u003e error may occur initially with App Engine; waiting a few minutes and retrying the request is recommended before checking logs.\u003c/p\u003e\n"],["\u003cp\u003eErrors like "No service found" or "permission denied" often indicate a missing service configuration or disabled APIs, which can be resolved by deploying the OpenAPI document and ensuring necessary APIs are enabled.\u003c/p\u003e\n"],["\u003cp\u003eA \u003ccode\u003e404 Not Found\u003c/code\u003e error after migrating to Endpoints Frameworks version 2 requires specific troubleshooting steps detailed in Java and Python migration guides.\u003c/p\u003e\n"],["\u003cp\u003eIf \u003ccode\u003eInvoke-WebRequest\u003c/code\u003e fails in Windows PowerShell, try using Cloud Shell, Postman, or \u003ccode\u003ecurl\u003c/code\u003e with specific formatting for nested quotation marks.\u003c/p\u003e\n"]]],[],null,["# Troubleshooting response errors\n\nIf you don't get a successful response from a request to your\nCloud Endpoints Frameworks API, you can use Cloud Logging in the\nGoogle Cloud console to help troubleshoot.\n\nViewing logs\n------------\n\n1. In the Google Cloud console, go to the **Logging** \\\u003e\n **Logs Explorer** page.\n\n\n [Go to the Logs Explorer page](https://console.cloud.google.com/logs/query)\n\n \u003cbr /\u003e\n\n2. From the project drop-down list at the top of the page, select the\n Google Cloud project in which you created your API.\n\n3. Select **GAE Application** and **All logs**.\n\n4. Adjust the time range until you see a row that shows an error.\n\n5. Click **Expand All** to see the entire log for the error.\n\nThe following section provides troubleshooting information for specific error\nmessages. If you are unable to fix the issue, copy one of the log entries that\nshows the error and paste it in a text file. Include the log in any\ncommunication that you have with Google.\n\n### `503 Service Unavailable`\n\nApp Engine might take a few minutes to respond successfully to requests. If you\nsend a request and get a `503` error, wait a few minutes and try the\nrequest again. If you still don't get a successful response, check the\nCloud Logging logs. The following are some error messages that you might\nsee in the Cloud Logging logs.\n\n### `404 Not Found`\n\nIf you recently migrated to Endpoints Frameworks version 2, and you\nget the `404 Not Found` error message, see the following sections to\ntroubleshoot the issue:\n\n- [Java: Troubleshooting](/endpoints/docs/frameworks/java/migrating#api_returns_404_errors_but_api_explorer_still_lists_apis_correctly)\n- [Python: Troubleshooting](/endpoints/docs/frameworks/python/migrating#api_returns_404_errors_but_api_explorer_still_lists_apis_correctly)\n\nIssues with the example `Invoke-WebRequest`\n-------------------------------------------\n\nIn some versions of Windows PowerShell, the example `Invoke-WebRequest` in the\n[tutorials](/endpoints/docs/frameworks/tutorials) fails. We have also received a\nreport that the response contained a list of unsigned bytes that had to be\nconverted to characters. If the example `Invoke-WebRequest` didn't return the\nexpected result, try sending the request using another application. Following\nare a few suggestions:\n\n- [Start Cloud Shell](/shell/docs/starting-cloud-shell), and follow the Linux steps in the tutorial that you were using to send the request.\n- Use a third-party application such as the Chrome browser extension Postman\n (offered by `www.getpostman.com`). When creating the request in Postman:\n\n - Select `POST` as the HTTP verb.\n - For the header, select the key `content-type` and the value `application/json`.\n - For the body, enter: `{\"message\":\"hello world\"}`\n - Enter the URL for the sample application. For example:\n\n https://example-project-12345.appspot.com/_ah/api/echo/v1/echo\n\n- Download and install [`curl`](https://curl.haxx.se/download.html), which you\n run in the Command prompt. Because Windows doesn't handle double quotation\n marks nested inside single quotation marks, you have to change the `--data`\n option in the example, as follows: `--data \"{\\\"message\\\":\\\"hello world\\\"}\"`\n\nWhat's next\n\n- Get started using the [Logs Explorer](/logging/docs/view/logs-explorer-interface).\n\n- Learn how to [route logs](/logging/docs/export/configure_export_v2).\n\n- Use [filters](/logging/docs/view/advanced_filters)\n for advanced filtering, such as getting all requests with a latency greater\n than 300 milliseconds."]]
