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

Testing the URL after creating the api proxy , getting result as The site can't be reached.

Testing the URL after creating the new api proxy , getting result as Site can't be reached. This error is coming for all my old proxy also which i have already tested before. 

0 3 525
3 REPLIES 3

There is not enough detail in your question, for us to be able to make suggestions that might help you. 

Hi dchiesa1, Thanks for your reply.  I am creating API proxy in Apigee edge platform but for every API proxy i am getting same result as "This site can't be reached". For example: the URL which was given in Apigee docs tutorial , its also giving me the same result. Please find the URL and image attached  below. This problem is also occuring for the API which i have already created and tested before and that time they were working fine.

Akansha_0-1631780400549.png

 

https://ahamilton-eval-test.apigee.net/getstarted

 

Hi Akansha

Thanks for that screenshot, that helps me understand what's happening. 

I'm sorry you're having trouble, and I think I can shed some light on the matter .

I recognize that hostname in the URL you are trying.  I have seen it in various places in the Apigee documentation. I think you are following along in some documentation, maybe a tutorial.  The documentation tells you to invoke a URL at "ahamilton-eval-test.apigee.net".  But that is an example hostname.  That's not the actual hostname you should use.  You would need to use the appropriate hostname set up for your Apigee instance. It will be different for each Apigee instance.

  • If you are using the older Apigee Edge, then Apigee sets up a hostname for you.  It will follow the pattern like this: ORGNAME-ENVNAME.apigee.net, where ORGNAME is replaced with your organization name, and ENVNAME is replaced with your environment name.  So the example of ahamilton-eval-test corresponds to an orgname of ahamilton-eval and an environment name of test.  
  • But Apigee X does not provision a hostname for you.  If you are using Apigee X, You must do that yourself.  There is some documentation in the "setting up Apigee" pages that describes what you must do to get a hostname.  I know the product team is looking at making this simpler and easier for evaluation purposes. But for now you have to do that part yourself.  Consult the docs for more information on allowing "external access" to your APIs. 

Which Apigee are you using?  Edge or X?  Or maybe something else (There are a few other options)?