RANGES_EXHAUSTED indica que não foi possível satisfazer o intervalo de endereços IP que pediu inicialmente e que tem de pedir um novo intervalo. Inicialmente,
criou um pedido de intervalo no Passo 2: configure a rede.
Para pedir um novo intervalo a partir do qual o Apigee escolhe um endereço IP para as ligações de serviços privados, execute o seguinte comando gcloud:
gcloud compute addresses create $RANGE_NAME_2
--project=$PROJECT_ID --global --prefix-length=16
--description="additional peering range for Google services" --network=$NETWORK_NAME
--purpose=VPC_PEERING
Este comando cria um novo intervalo com o nome $RANGE_NAME_2.
Valide os detalhes do intervalo de endereços antigo e novo
gcloud compute addresses list --global --project=$PROJECT_ID
Valide os detalhes da interligação de VPC existente:
gcloud services vpc-peerings list \
--network=$NETWORK_NAME \
--service=servicenetworking.googleapis.com \
--project=$PROJECT_ID
Criar uma organização do Apigee
O exemplo seguinte mostra um erro comum que o Apigee pode apresentar quando tenta criar uma organização pela primeira vez:
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.
Isto significa que uma ou mais das APIs necessárias não estão ativadas. Reveja as APIs indicadas no
Passo 1: ative as APIs necessárias e certifique-se de que todas as APIs estão ativadas antes de continuar.
Além disso, pode receber um dos seguintes erros HTTP:
401 (UNAUTHENTICATED) indica que as suas credenciais podem ter expirado. Experimente renovar o token de autorização, como mostra o exemplo seguinte:
Normalmente, 409 (Conflict) indica que o nome da organização indicado já existe. Os nomes das organizações têm de ser globalmente exclusivos. Escolha outro nome para a organização e reemita o comando. (Especifica o nome na carga útil do pedido se estiver a criar uma organização na linha de comandos. Tenha em atenção que tem de
criar uma organização com o mesmo nome do seu projeto. Por isso, isto não deve
acontecer, a menos que tenha cometido um erro de digitação.)
Segue-se um possível erro que o Apigee pode devolver quando verifica o estado de um novo pedido de organização:
403 (Permission Denied) pode indicar que a organização ainda não foi criada. Aguarde mais um minuto e tente novamente. Se o Apigee devolver um 403 quando tentar criar a nova organização pela primeira vez, pode significar que uma ou mais das suas APIs não foram ativadas. Certifique-se de que ativou todas as APIs conforme descrito no Passo 1: ative as APIs necessárias
.
Implementação de amostras
O balanceador de carga não está em bom estado
Quando implementa um proxy de exemplo, o Apigee pode devolver um erro HTTP 502 (Bad Gateway).
Neste caso, experimente o seguinte:
Verifique o estado do balanceador de carga. O separador Equilibrador de carga mostra todos os equilibradores de carga do projeto e os respetivos estados. Um triângulo amarelo indica
que o serviço de back-end do balanceador de carga não está em bom estado.
Na Google Cloud consola, aceda à página Serviços de rede > Equilíbrio de carga.
Depois de confirmar um problema com o equilibrador de carga, verifique as VMs na instância de tempo de execução
para garantir que estão em funcionamento e em bom estado.
Consulte os ficheiros de registo para ver se consegue encontrar um erro ou outro tipo de problema que possa ter
originado um problema. Para mais informações sobre como ativar e ver registos, consulte o artigo
Ver registos.
Experimente fazer um reinício progressivo no grupo de instâncias na Cloud Console:
Na Google Cloud consola, aceda à página Compute Engine > Grupos de instâncias.
Na lista de grupos de instâncias, clique no que não está a responder na coluna Nome.
Clique em Reinício/substituição progressiva.
No ecrã seguinte, clique em Reiniciar.
Esta ação reinicia a instância do Envoy.
IP da instância incorreto
Se, em qualquer altura, eliminar e recriar a sua instância do Apigee, o IP da instância do Apigee é alterado e pode ficar dessincronizado com o IP do ponto final do modelo do grupo de instâncias gerido (MIG). Por exemplo, o modelo do MIG continua a ter o IP antigo da instância eliminada. O modelo de MIG foi criado durante o processo de aprovisionamento do Apigee. Nesta situação, experimente os seguintes passos para atualizar o modelo MIG com o IP do Apigee correto:
Na Google Cloud consola, aceda à página Apigee > Administração > Instâncias.
Abra o modelo de instância. Tem de abrir o modelo de instância usado pelo back-end mapeado para o equilibrador de carga.
Desloque a página para baixo para encontrar o ENDPOINT IP na secção Metadados personalizados.
Se o IP do ponto final for diferente do que anotou na IU do Apigee, tem de alterar o IP do modelo de instância para corresponder ao IP da instância do Apigee.
Consulte o artigo Alterar IPs de instâncias.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-09-03 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)"]]
