Loading Profile...
No ping response from apigee servers ...
I've done the CNAME setup route and everything had been working fine for the past few months, but today I've been getting support requests by my customers because they're not getting a response from our API. I've checked that *our* server is fine, so am starting to think there's something up with the Apogee proxy server.
Our API is at api.sandbox.mygengo.com - which points to sandbox.mygengo.apigee.com. Anyone over there know what's up? Has an EC2 instance changed or something?
Our API is at api.sandbox.mygengo.com - which points to sandbox.mygengo.apigee.com. Anyone over there know what's up? Has an EC2 instance changed or something?
I’m frustrated
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
-
Inappropriate?Matthew, sorry you're having trouble—we'll look into this right away.
Can you provide an API method we can use to test the endpoint? -
Inappropriate?Hi Marsh,
If you just ping it (api.sandbox.mygengo.com) and your endpoint too (sandbox.apigee.mygengo.com) you'll see there's no response ... -
Inappropriate?Aha! We don't currently accept pings to proxies. Do you get an error when you try a curl request against the endpoint?
Also, if you can send the http headers and any response you receive, that will help us troubleshoot.
Thanks! ~Marsh -
Inappropriate?I just tested both endpoints. The api.sandbox.mygengo.com URL was broken, and sandbox.mygengo.apigee.com is up (showing the "Translate API" page).
I tried a few minutes later and got neither one. I suspect that something is cycling in our EC2 environment.
I tried just now at 7:21 PM Pacific and got the original result. The page displayed when accessing http://sandbox.mygengo.apigee.com is http://mygengo.com/services/api/#bene... -
Inappropriate?Hi guys - for some reason the CNAME setting wasn't fully qualified, so I updated my CNAME setting on apigee and it works fine now. I never changed it before, so I'm guessing there was some update that changed it? Might want to review a recent deploy / update on your side and see if others are affected ...
I’m thankful it works now.
1 Comment
Add a comment
This solves the problem
-
by the way, here's the response I was getting that led me to believe something was up with Apigee:
<?xml version="1.0" encoding="UTF-8"?>
<Error>
<reason>Requested Domain api.sandbox.mygengo.com not registered</reason>
</Error> -
Inappropriate?Thanks, Matthew. We'll look into this further and see what might have caused the change.
EMPLOYEE
EMPLOYEE
