-
Notifications
You must be signed in to change notification settings - Fork 36
Subscription validation request timed out #9
Comments
Hi @alekkowalczyk . Since setting up my notification endpoint, I've only gotten that error when my service is offline (which also happens a lot). I just retested and I'm able to create a subscription. Any chance your response time has slowed down? I forwarded your question along to see if we can troubleshoot on this end. |
Hi @DianeD thanks for the quick response. |
Tracking this issue on StackOverflow: http://stackoverflow.com/questions/41621627/microsoft-graph-webhook-subscription-validation-request-timed-out |
Yes I'm in mail contact with Gary, I'll let here know how it was resolved.
Thanks for the support!
…On 13 January 2017 at 18:37, DianeD ***@***.***> wrote:
Tracking this issue on StackOverflow: http://stackoverflow.com/
questions/41621627/microsoft-graph-webhook-subscription-
validation-request-timed-out
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKbxKEGpQGk9waq1SNKvua5UYn3nFOxNks5rR7ZDgaJpZM4LiMsJ>
.
|
Issue was resolved on StackOverflow: "If anybody is interested: after our offline follow up it turned out that it's a connection issue, after my endpoint was deployed on a cloud service it worked. For endpoints pointing to dev machines ngrok is suggested." Thanks for reporting, @alekkowalczyk ! |
This is the ruby code I'm using to create a subscription in microsoft graph:
it worked great, but suddenly today I'm getting a
Subscription validation request timed out
response. Altough when I'm doing a POST tohttps://my_url/api/v1/outlook/o365notification
it's just working fine.Any ideas why it stopped working when nothing changed on my side?
Could it be that, because
my_url
points on my dev environment and is often offline, the domain got banned?The text was updated successfully, but these errors were encountered: