Re: Troubleshooting tips ...
Set CF_TRACE=true to see the exact request that results in the 404. Most
likely it is a request to api.cf.fxlab.net/v2/info. Double check that that
url does in fact return a 404.
From there, the problem will probably be in either the router or the api
instance. If you ssh onto the api instance, you can try to curl
localhost:9022/v2/info to see if it is working.
On Fri, Jul 31, 2015 at 5:55 AM, Vishwanath V <thelinuxguyis(a)yahoo.co.in>