Dokumen ini mencantumkan error umum dan menjelaskan kemungkinan penyelesaiannya saat Anda menginstal dan mengonfigurasi Apigee.
Membuat instance baru
Bagian ini menjelaskan error umum dan kemungkinan penyelesaiannya setelah mengirim permintaan ke Apigee untuk membuat instance baru:
401 (UNAUTHENTICATED) menunjukkan bahwa kredensial Anda mungkin telah
habis masa berlakunya. Coba perbarui token otorisasi Anda, seperti yang ditunjukkan dalam contoh berikut:
RANGES_EXHAUSTED menunjukkan bahwa rentang alamat IP yang awalnya Anda
minta tidak dapat dipenuhi dan Anda harus meminta rentang baru. Anda awalnya
membuat permintaan rentang di Langkah 2: Siapkan jaringan.
gcloud services vpc-peerings list \
--network=$NETWORK_NAME \
--service=servicenetworking.googleapis.com \
--project=$PROJECT_ID
Membuat organisasi Apigee
Contoh berikut menunjukkan error umum yang mungkin ditampilkan Apigee saat Anda pertama kali mencoba membuat organisasi:
Apigee API (staging) has not been used in project 59387731598 before or it is disabled.
Enable it by visiting https://console.developers.google.com/apis/api/staging-apigee.sandbox.googleapis.com/overview?project=59387731598 then retry.
If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.
Artinya, satu atau beberapa API yang diperlukan tidak diaktifkan. Tinjau API yang tercantum di
Langkah 1: Aktifkan API yang diperlukan dan pastikan semua API diaktifkan sebelum Anda melanjutkan.
Selain itu, Anda mungkin mendapatkan salah satu error HTTP berikut:
401 (UNAUTHENTICATED) menunjukkan bahwa kredensial Anda mungkin telah
habis masa berlakunya. Coba perbarui token otorisasi Anda, seperti yang ditunjukkan dalam contoh berikut:
409 (Conflict) biasanya menunjukkan bahwa nama organisasi yang diberikan sudah ada. Nama organisasi harus unik secara global. Pilih nama lain untuk
organisasi dan terbitkan kembali perintah. (Anda menentukan nama di payload
permintaan jika membuat organisasi di command line. Perlu diingat bahwa Anda harus
membuat organisasi yang memiliki nama yang sama dengan project Anda, jadi hal ini seharusnya tidak
terjadi kecuali ada kesalahan ketik.)
Berikut adalah kemungkinan error yang mungkin ditampilkan Apigee saat Anda memeriksa status permintaan organisasi baru:
403 (Permission Denied) dapat menunjukkan bahwa organisasi belum
dibuat. Tunggu satu menit lagi dan coba lagi. Jika Apigee menampilkan 403 saat Anda pertama kali
mencoba membuat organisasi baru, hal ini dapat berarti bahwa satu atau beberapa API Anda belum
diaktifkan. Pastikan Anda mengaktifkan semua API seperti yang dijelaskan di Langkah 1: Aktifkan API yang diperlukan
.
Men-deploy contoh
Load balancer tidak responsif
Saat men-deploy proxy contoh, Apigee mungkin menampilkan error HTTP 502 (Bad Gateway).
Dalam hal ini, coba langkah berikut:
Periksa kondisi Load Balancer. Tab Load balancer menampilkan semua load balancer untuk project dan statusnya. Segitiga kuning menunjukkan
bahwa layanan backend load balancer tidak responsif.
Di Google Cloud konsol, buka halaman Network services > Load balancing.
Setelah mengonfirmasi masalah pada load balancer, periksa VM di instance runtime Anda
untuk memastikan VM tersebut aktif dan responsif.
Lihat file log untuk melihat apakah Anda dapat menemukan error atau jenis masalah lain yang mungkin menyebabkan masalah. Untuk mengetahui informasi selengkapnya tentang cara mengaktifkan dan melihat log, lihat
Melihat log.
Coba lakukan rolling restart pada grup instance di konsol Cloud:
Di konsol Google Cloud , buka halaman Compute Engine > Instance groups.
Dari daftar grup instance, klik grup yang tidak merespons di kolom
Name.
Klik Rolling Restart/Replace.
Di layar berikutnya, klik Mulai ulang.
Tindakan ini akan memulai ulang instance Envoy.
IP instance salah
Jika Anda menghapus dan membuat ulang instance Apigee kapan saja,
IP instance Apigee akan berubah dan dapat menjadi tidak sinkron dengan IP endpoint template
grup instance terkelola (MIG). Misalnya, template MIG akan tetap memiliki IP lama dari
instance yang dihapus. Template MIG dibuat selama proses penyediaan Apigee. Dalam situasi ini, coba langkah-langkah berikut untuk memperbarui template MIG dengan
IP Apigee yang benar:
Di konsol Google Cloud , buka halaman Apigee > Admin > Instances.
Buka template instance. Anda perlu membuka template instance yang digunakan oleh
backend yang dipetakan ke load balancer Anda.
Scroll ke bawah untuk menemukan ENDPOINT IP di bagian Metadata kustom.
Jika IP endpoint berbeda dengan yang Anda catat di UI Apigee, Anda harus mengubah
IP template Instance agar cocok dengan IP instance Apigee.
Lihat Mengubah IP instance.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eThis document provides troubleshooting steps for common errors encountered during the installation and configuration of Apigee, excluding Apigee hybrid.\u003c/p\u003e\n"],["\u003cp\u003eA \u003ccode\u003e401 (UNAUTHENTICATED)\u003c/code\u003e error typically indicates expired credentials, requiring a renewal of the authorization token.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eRANGES_EXHAUSTED\u003c/code\u003e error when creating a new instance means a new IP address range must be requested by executing gcloud commands to update your connection request.\u003c/p\u003e\n"],["\u003cp\u003eWhen creating an Apigee organization, a \u003ccode\u003e409 (Conflict)\u003c/code\u003e error indicates the organization name already exists and a different, globally unique name must be used.\u003c/p\u003e\n"],["\u003cp\u003eA \u003ccode\u003e502 (Bad Gateway)\u003c/code\u003e error during sample proxy deployment suggests an issue with the load balancer, which can be resolved by checking the load balancer's health and potentially doing a rolling restart on the instance group.\u003c/p\u003e\n"]]],[],null,["# Troubleshooting the Apigee installation\n\n*This page\napplies to **Apigee** , but not to **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\nThis document lists common errors and describes possible resolutions for\nwhen you install and configure Apigee.\n\nCreating a new instance\n-----------------------\n\nThis section describes common errors and possible resolutions after sending a request to Apigee\nto create a new instance:\n\n- `401 (UNAUTHENTICATED)` indicates that your credentials may have timed out. Try renewing your authorization token, as the following example shows: \n\n ```\n AUTH=\"Authorization: Bearer $(gcloud auth print-access-token)\"\n ```\n- `RANGES_EXHAUSTED` indicates that the range of IP addresses that you initially requested could not be accommodated and that you must request a new range. You initially created a range request in [Step 2: Set up networking](/apigee/docs/api-platform/get-started/configure-service-networking).\n 1. Create these environment variables \n\n ```\n RANGE_NAME_1=YOUR_RANGE_NAME_1\n RANGE_NAME_2=YOUR_RANGE_NAME_2\n NETWORK_NAME=YOUR_NETWORK_NAME\n ```\n 2. Verify the details of the existing address ranges and ensure it will not overlap with the new range. \n\n ```\n gcloud compute addresses list --global --project=$PROJECT_ID\n ``` \n\n ```\n gcloud compute addresses describe $RANGE_NAME_1 --global --project=$PROJECT_ID \n ```\n 3. To request a new range from which Apigee chooses an IP address for the private service connections execute the following **gcloud** command: \n\n ```\n gcloud compute addresses create $RANGE_NAME_2\n --project=$PROJECT_ID --global --prefix-length=16\n --description=\"additional peering range for Google services\" --network=$NETWORK_NAME\n --purpose=VPC_PEERING \n ```\n 4. This command creates a new range named **$RANGE_NAME_2**.\n 5. Verify the details of both the old and new address range \n\n ```\n gcloud compute addresses list --global --project=$PROJECT_ID \n ``` \n\n ```\n gcloud compute addresses describe $RANGE_NAME_1 --global --project=$PROJECT_ID \n ``` \n\n ```\n gcloud compute addresses describe $RANGE_NAME_2 --global --project=$PROJECT_ID \n ```\n 6. Verify the existing VPC peering details: \n\n ```\n gcloud services vpc-peerings list \\\n --network=$NETWORK_NAME \\\n --service=servicenetworking.googleapis.com \\\n --project=$PROJECT_ID \n ```\n 7. Execute the following command to update your connection request: \n\n ```\n gcloud services vpc-peerings update\n --service=servicenetworking.googleapis.com --network=$NETWORK_NAME\n --ranges=$RANGE_NAME_1,$RANGE_NAME_2 --project=$PROJECT_ID \n ```\n | **Note:** You must specify the name of your first range (in this case, `RANGE_NAME_1`) and a name for your newly requested range (in this case, `RANGE_NAME_2`). For more information, see [gcloud services\n | vpc-peerings update](/sdk/gcloud/reference/services/vpc-peerings/update).\n 8. Verify the existing VPC peering details: \n\n ```\n gcloud services vpc-peerings list \\\n --network=$NETWORK_NAME \\\n --service=servicenetworking.googleapis.com \\\n --project=$PROJECT_ID \n ```\n\nCreating an Apigee organization\n-------------------------------\n\nThe following example shows a common error that Apigee might display when you first try to create\nan organization: \n\n```text\n Apigee API (staging) has not been used in project 59387731598 before or it is disabled. \n Enable it by visiting https://console.developers.google.com/apis/api/staging-apigee.sandbox.googleapis.com/overview?project=59387731598 then retry. \n If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.\n```\n\nThis means that one or more of the required APIs is not enabled. Review the APIs listed in\n[Step 1: Enable required APIs](/apigee/docs/api-platform/get-started/enable-apis) and be sure that all APIs are enabled before you continue.\n\nIn addition, you might get one of the following HTTP errors:\n\n- `401 (UNAUTHENTICATED)` indicates that your credentials may have timed out. Try renewing your authorization token, as the following example shows: \n\n ```\n AUTH=\"Authorization: Bearer $(gcloud auth print-access-token)\"\n ```\n- `404 (Not Found)` can be the result of the following:\n - You entered the wrong endpoint/request URL. Check that you specified `apigee.googleapis.com` for the API call's domain.\n - Your project might not yet be provisioned. Contact [Apigee Sales](https://pages.apigee.com/contact-sales-reg.html).\n- `409 (Conflict)` usually indicates that the given organization name already exists. Organization names must be globally unique. Choose another name for the organization and re-issue the command. (You specify the name in the payload of the request if you are creating an organization on the command line. Keep in mind that you must create an organization that has the same name as your project, so this really shouldn't happen unless there's a typo.)\n\nThe following is a possible error that Apigee might return when you check the status of a new\norganization request:\n\n- `403 (Permission Denied)` could indicate that the organization has not yet been created. Wait another minute and try again. If Apigee returns a `403` when you first try to create the new organization, it could mean that one or more of your APIs have not been enabled. Be sure that you enabled all the APIs as described in [Step 1: Enable required APIs](/apigee/docs/api-platform/get-started/enable-apis) .\n\nDeploying samples\n-----------------\n\n### Load balancer not healthy\n\nWhen deploying a sample proxy, Apigee might return a `502 (Bad Gateway)` HTTP error.\nIn this case, try the following:\n\n1.\n Check the health of the Load Balancer. The Load balancer tab shows all load\n balancers for the project and their statuses. A yellow triangle indicates\n that the load balancer backend service is not healthy.\n\n In the Google Cloud console, go to the **Network services \\\u003e Load balancing** page.\n\n [Go to Load balancing](https://console.cloud.google.com/net-services/loadbalancing)\n2. After confirming an issue with the load balancer, check the VMs in your runtime instance to ensure that they are up and healthy.\n3. Look at the log files to see if you can find an error or other type of issue that might have lead to a problem. For more information on enabling and viewing logs, see [Viewing logs](/load-balancing/docs/https/https-logging-monitoring#viewing_logs).\n4. Try doing a rolling restart on the instance group in Cloud console:\n 1. In the Google Cloud console, go to the **Compute Engine \\\u003e Instance groups** page.\n\n [Go to Instance groups](https://console.cloud.google.com/compute/instanceGroups)\n 2. From the list of instance groups, click the one that is not responding in the **Name** column.\n 3. Click **Rolling Restart/Replace**.\n 4. On the next screen, click **Restart** .\n\n This restarts the Envoy instance.\n\n### Incorrect instance IP\n\n\nIf at any time you delete and recreate your Apigee instance,\nthe Apigee instance IP changes and can become out of sync with the managed instance group (MIG)\ntemplate's endpoint IP. For example, the MIG template will still have the old IP from the\ndeleted instance. The MIG template was created during the Apigee [provisioning process](/apigee/docs/api-platform/get-started/install-cli#external). In this situation, try the following steps to update the MIG template with\nthe correct Apigee IP:\n\n1. In the Google Cloud console, go to the **Apigee \\\u003e Admin \\\u003e Instances** page.\n\n [Go to Instances](https://console.cloud.google.com/apigee/instances)\n2. Note the IP Address of the instance. You will need to know this IP in a later step. For example: `10.117.200.2`.\n3. In the Google Cloud console, go to the **Instance templates** page.\n\n [Go to Instance templates](https://console.cloud.google.com/compute/instances)\n4. Open the instance template. You need to open the instance template that is used by the backend that is mapped to your load balancer.\n5. Scroll down to find the `ENDPOINT` IP under the **Custom metadata** section.\n6. If the endpoint IP differs from the one you noted in the Apigee UI, you must change the Instance template IP to match the Apigee instance IP. See [Changing instance IPs.](/apigee/docs/api-platform/system-administration/change-instance-ips)"]]
