I have successfully installed apigee on GCP. While doing so mentioned VM instance internal IP as the MSIP, now in my virtual host I am getting the internal IP populated, as the result when ever i am deploying a proxy the testing it from postman I am getting the server reachable. I need to change the virtual host on my VM instance, for that I believe there is a management API that need to be executed…
amar_baner@cma-apigeetest-node2 /]$ curl -X GET --header “Authorization: Basic XXXXX” “http://10.128.0.8:9001/amarorg/environments/dev/virtualhosts"{“fault”:{“faultstring”:"Unable to identify proxy for host: 10.128.0.8:9001 and url: /amarorg/environments/dev/virtualhosts”,“detail”:{“errorcode”:“messaging.adaptors.http.flow.ApplicationNotFound”}}}[amar_baner@cma-apigeetest-node2 /]$
Thanks a lot Stephen.
Just wanted to give some more brief about the issue , I installed APIGEE on GCP,using the mentioned link [[Install the Edge apigee-setup utility | Edge for Private Cloud v4.53.00 | Apigee Docs].
In GCP you get two IP address [Internal as well External] , My installation was successful, and I was able to successfully login into my apigee portal, from my machine.
After that I created a simple api proxy with mocktarget point, when I deployed that API, I could see the virtual address was the internal IP of the VM instance.Now when I access the API proxy from my desktop, I am getting a server not reachable , have attached some screenshots for reference.
Just a quick question, if I have to update the virtual host then should I be updating it with the public IP.
screenshot-60.pngscreenshot-61.pngscreenshot-62.pngscreenshot-63.png
Yes, you should use the external IP address for configuring virtual hosts.
Stephen
