Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Issue in creating API Proxy as attached screenshot

Screenshot (4)_LI.jpg

As shown in the above picture it is not autopopulating the URL to work further 

it is showing :   "http://yourhost:port/mybasepath"

 

please let me know why it is not autogenerating the URL as shown by others .... in this case what should I input this yourhost and port ?

0 9 1,174
9 REPLIES 9

Not sure but lets check few things.

1.Is the proxy deployed?

2.If you navigate to Admin -> VirtualHost what do you see for Alias & Port. You can use the host & port for the url.

3.Also check what setting you have for HTTPProxyConnection & then  you can use values from VirtualHost like below.

 

<HTTPProxyConnection>
<BasePath>/v1/</BasePath>
<VirtualHost>secure</VirtualHost>
<VirtualHost>default</VirtualHost>
</HTTPProxyConnection>

https://<<virtualhost alias>>:<<vitualhosthost port>>/<<BasePath from HTTPProxyConnection>>/<<path suffix if any>>

If you look at the API Proxy's overview you will see the basepath of it under the proxy endpoints list.

 

For the host, you deploy your API Proxy to an environment (Looks like it's deployed to eval). Your environment (eval) belongs to an Environment group (such as eval-group) that is then mapped to a host. To find this, look under Admin > Environments > Groups, there will be a hostname that's associated with the Environment Group.

You should be able to combine this host with the proxy's basepath and populate it in the trace tool or manually send requests using curl, postman, or your favourite tool. 

Screenshot (5).png

Thanks for your reply...

As attached I have tried the same " https://buoyant-dynamo-321311-eval.apigee.net/myproxy1 " ..... here myproxy1 is the base path but still it is displaying me the below error

"Error Sending Request
Could not connect to https://buoyant-dynamo-321311-eval.apigee.net/myproxy1. Make sure the URL is correct. Original Error: Endpoint is not reachable: Get "https://buoyant-dynamo-321311-eval.apigee.net/myproxy1": harpoon error for ERROR_DNS. "

Please help me out with this.

Hi

What you are saying is how it used to work in apigee-edge where we used to have a default host mapped to each environment. Its different in apigee x. For external access, we need to map hostnames to environment-group, but in UI it will not show this mapping. It will work if you try curl or in postname replacing yourhost:port with your domain

Hi @CHIRUSOWMYA 

If we're doing the same thing on Apigee Edge, it would be as simple as using the existing eval account virtual host to hit API Proxies. But in APIGEE X we've to configure the Domain with your ingress IP so that it can redirect the traffic to your host with the port number you define in the firewall to use as per HTTP protocols.

And the Same Domain will be used to hit all the proxies created in the Environment of ORG.

Hope this may clear your picture of accessing the proxy using Virtual host Domain.

Hi Abhishek,

Thanks for the reply.... can you please let me know how to configure the domain with my ingress IP in APIGEE X as you said

Did you follow the steps in the Apigee X eval onboarding process? 

https://cloud.google.com/apigee/docs/api-platform/get-started/eval-orgs

screenshot-20210812-091320.png

You will get an IP address there, in that step.  And you can ask for a wildcard DNS (easy), or ... you can set up your own hostname.  You'll need a domain name service to do the latter.  

 

Hi @CHIRUSOWMYA 

As @dchiesa1, already replied the procedure to do it. You can easily follow the DOC steps and configure the IP or WILDCARD DNS. Please make a note of DNS/IP which will be used as a HOST/DOMAIN for your residing API Proxies in the APIGEE X Eval account.

Just want to add a simpler picture that whenever you make use of your runtime service for management UI to work Regional/Zonal, this ingress service is active for external Access with IP that IP you can see in Runtime Dashboard in Cloud. The same IP can be used to redirect the traffic for accessing your API Services/Proxies. Just you need to configure that IP and PORT with DNS of your choice from the market or you can use this wildcard service to get it.

I think this may help you to get a clear picture. Please let me know if this help you in finding your solution

@CHIRUSOWMYA : Am getting same error. Can you help me how did you resolved this issue.?

Top Solution Authors