SSL 핸드셰이크 오류와 같은 TLS/SSL 오류가 표시되면 DNS 제공업체에 문의하여 호스트 이름의 DNS A 레코드가 올바르게 구성되어 있는지 확인하세요. 레코드에 Apigee 프로비저닝 중에 생성된 부하 분산기의 IP가 있는지 확인합니다.
IP가 무엇인지 확실하지 않으면
호스트 이름에 Cloud 부하 분산기가 구성되어 있는지 확인을 참조하세요.
TLS/SSL 인증서 오류가 표시되면 부하 분산기와 연결된 SSL 인증서에 올바른 호스트 이름이 없을 수 있으므로 거부됩니다. 인증서는 프로비저닝 프로세스 중에 생성되었습니다.
호스트 이름에 Cloud 부하 분산기가 구성되어 있는지 확인의 문제 해결 단계는 인증서를 찾고 검사하는 방법을 보여줍니다.
문제를 해결할 수 없는 경우 Apigee를 프로비저닝한 사용자에게 추가 지원을 요청하세요.
[[["이해하기 쉬움","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-08-19(UTC)"],[[["\u003cp\u003eThis page provides instructions for testing an API proxy in Apigee or Apigee hybrid, offering guidance for both the new Apigee in Cloud console and the classic Apigee UI.\u003c/p\u003e\n"],["\u003cp\u003eAccessing the API proxy involves finding the environment group hostname, which is determined by either an external or internal network configuration, requiring specific \u003ccode\u003ecurl\u003c/code\u003e commands for each.\u003c/p\u003e\n"],["\u003cp\u003eSuccessful API proxy calls will return the output "Hello, Guest!", otherwise potential issues may be due to timeout errors, incorrect hostnames, misconfiguration of the environment group hostname, or TLS/SSL certificate problems.\u003c/p\u003e\n"],["\u003cp\u003eSteps for the classic Apigee UI are to go to Admin > Environments > Groups, then View in Google Cloud Console to access the environment groups to find the proper hostname.\u003c/p\u003e\n"],["\u003cp\u003eA successful call will return "Hello, Guest!".\u003c/p\u003e\n"]]],[],null,["# Step 3: Call an API proxy\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\nIn this step, you will test the API proxy you just created and deployed. \n\n### Apigee in Cloud console\n\n1. In the Google Cloud console, go to the **Apigee \\\u003e Management \\\u003e Environments** page.\n\n [Go to Environments](https://console.cloud.google.com//apigee/environments)\n2. Make sure the same Google Cloud project where you created the API proxy is selected from the dropdown at the top of the page.\n3. Select the **Environment Groups** tab.\n4. In the table, find the row for the environment group that contains the environment where **myproxy** is deployed. The hostname appears in the **Host Names** column of this row. For example: `mydomain.com`.\n5. Call the API proxy. The way you call the proxy depends on whether your Apigee instance is configured for external or internal network access. If you aren't sure how your Apigee instance is configured, contact your Apigee administrator.\n - **External access** : If your Apigee instance is configured for external access, call the proxy as follows: \n\n ```\n curl https://YOUR_ENV_GROUP_HOSTNAME/myproxy\n ```\n\n Where \u003cvar translate=\"no\"\u003eYOUR_ENV_GROUP_HOSTNAME\u003c/var\u003e is the hostname you obtained in the\n previous step.\n\n For example: \n\n ```\n curl https://mydomain.com/myproxy\n ```\n\n Here's another example, where the wildcard DNS service `nip.io` is used for the host: \n\n ```\n curl https://198.51.100.251.nip.io/myproxy\n ```\n - **Internal access** : If your Apigee instance is configured for internal network access, some extra steps are needed to obtain access to the internal load balancer and its IP address. For details, see [Calling a proxy with internal-only access](/apigee/docs/api-platform/get-started/accessing-internal-proxies).\n6. A successful call to the proxy returns the following output:\u003cbr /\u003e\n\n ```\n Hello, Guest!\n ```\n\n### Classic Apigee UI\n\n1. Open the [Apigee UI](https://apigee.google.com) in a browser.\n2. Make sure the same Google Cloud project where you created the API proxy is selected from the dropdown at the top of the page.\n3. In the Cloud console UI, select **Admin \\\u003e Environments \\\u003e Groups**.\n4. Click **View in Google Cloud console**.\n5. Select the **Environment Groups** tab.\n6. In the table, find the row for the environment group that contains the environment where **myproxy** is deployed. The hostname appears in the **Host Names** column of this row. For example: `mydomain.com`.\n7. Call the API proxy. The way you call the proxy depends on whether your Apigee instance is configured for external or internal network access. If you aren't sure how your Apigee instance is configured, contact your Apigee administrator.\n - **External access** : If your Apigee instance is configured for external access, call the proxy as follows: \n\n ```\n curl https://YOUR_ENV_GROUP_HOSTNAME/myproxy\n ```\n\n Where \u003cvar translate=\"no\"\u003eYOUR_ENV_GROUP_HOSTNAME\u003c/var\u003e is the hostname you obtained in the\n previous step.\n\n For example: \n\n ```\n curl https://mydomain.com/myproxy\n ```\n\n Here's another example, where the wildcard DNS service `nip.io` is used for the host: \n\n ```\n curl https://198.51.100.251.nip.io/myproxy\n ```\n - **Internal access** : If your Apigee instance is configured for internal network access, some extra steps are needed to obtain access to the internal load balancer and its IP address. For details, see [Calling a proxy with internal-only access](/apigee/docs/api-platform/get-started/accessing-internal-proxies).\n8. A successful call to the proxy returns the following output:\u003cbr /\u003e\n\n ```\n Hello, Guest!\n ```\n\nIf you get an error, check the following:\n\n- If you see a timeout error (unusual), try [undeploying and\n redeploying](/apigee/docs/api-platform/deploy/ui-deploy-new) the new API proxy.\n- If the host cannot be resolved, for example you receive a 404 error, double check that you are using the correct hostname and proxy name.\n- Make sure the environment group hostname is configured with the Cloud Load Balancer. See [Determining whether the Cloud Load Balancer is configured for a hostname](/apigee/docs/api-platform/fundamentals/environmentgroups-working-with#determining-whether-the-cloud-load-balancer-is-configured-for-a-hostname).\n- If you see a TLS/SSL error, such as an SSL handshake error, contact your DNS provider to make sure the DNS A record for the hostname is configured properly. Make sure the record has the IP of the load balancer that was created during Apigee provisioning. If you're not sure what the IP should be, see [Determining whether the Cloud Load Balancer is configured for a hostname](/apigee/docs/api-platform/fundamentals/environmentgroups-working-with#determining-whether-the-cloud-load-balancer-is-configured-for-a-hostname).\n- If you see a TLS/SSL certificate error, the SSL certificate associated with the load balancer might not have the correct hostname, and therefore is being rejected. The certificate was created during the provisioning process. The troubleshooting steps in [Determining whether the Cloud Load Balancer is configured for a hostname](/apigee/docs/api-platform/fundamentals/environmentgroups-working-with#determining-whether-the-cloud-load-balancer-is-configured-for-a-hostname) show you how to locate and inspect the certificate.\n- If you're unable to resolve the problem, contact the person who provisioned Apigee for further assistance.\n\n\nIn the next step, you will change the target endpoint of the API proxy.\n[1](/apigee/docs/api-platform/get-started/create-proxy) [2](/apigee/docs/api-platform/get-started/deploy-proxy) [3](/apigee/docs/api-platform/get-started/test-proxy) [(NEXT) Step 4: Change the target endpoint](/apigee/docs/api-platform/get-started/change-endpoint) [5](/apigee/docs/api-platform/get-started/add-policy)\n\n\u003cbr /\u003e"]]
