is there an IP address limitation on open api import?

[#1]

in my private cloud deployment i am starting to believe that the "create by open api" option might actually be getting limited by IP address. Whenever i try to import a doc from say:

http://10.184.42.188/files/some-api-swagger.json - one that passes json lint and renders okay in swagger editor - i get an immediate error:

"Error using OpenAPI: Bad request"

This is quite different from the swagger docs that take a while to time out because of lack of network access.

Is there some way to fix this? I would really like to use this feature.

[Former Community Member]

Have you tried the YAML version of the OAS document?

[#3]

thats not the problem. from cloud i am able to load this INSTANTLY:

http://petstore.swagger.io/v2/swagger.json if i take that file and load it on my own server and call it via the UI:

http://10.184.42.188/files/petstore-swagger.json

I get this error (see image)

[#4]

and just for giggles i put the petstore swagger up on a site that I was able to proxy to a public IP address via one of our gateway planets... i was able to load it from there w/o any problems! So it is a limitation of IP blacklisting...

[#5]

Update: More info here on how to fix this http://docs.apigee.com/private-cloud/latest/allowing-trace-tool-access-local-ip-addresses

[venkataraghavan]

@Benjamin Goldman

Did you try using chrome developer tools to track the api calls made when you hit Apply above ?

https://developer.chrome.com/devtools

specifically the Network group that lists the calls being made and the corresponding response.

May give an idea on the response that the management api is getting when you are using your own server IP.

[ncardace]

Yes you need to change an UI configuration section (and restart the edge-ui): see here https://docs.apigee.com/private-cloud/v4.18.05/allowing-trace-tool-access-local-ip-addresses