You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for checking in. We are aware of the situation, and we are working hard to resolve this as quickly as we can. We do apologize for the inconvenience this has caused.
Best,
"
Can it still be a good idea to try to reach by https if http does not answer? Like in the case that was from last night until earlier today?
The text was updated successfully, but these errors were encountered:
Http requests give 522 timeout.
Change request url from "http://api.embed.ly/1/oembed" to "https://api.embed.ly/1/oembed"
Reference:
http://api.embed.ly/1/oembed?url=https%3a%2f%2fbcove.video%2f3FCggAA&key=INSERT-YOUR-KEY-HERE
https://api.embed.ly/1/oembed?url=https%3a%2f%2fbcove.video%2f3FCggAA&key=INSERT-YOUR-KEY-HERE
UPDATE:
Interessting, it now works.. Both http and https..
No incident notified for 25.05.
http://status.embed.ly/
got this from support:
"
Hi there,
Thanks for checking in. We are aware of the situation, and we are working hard to resolve this as quickly as we can. We do apologize for the inconvenience this has caused.
Best,
"
Can it still be a good idea to try to reach by https if http does not answer? Like in the case that was from last night until earlier today?
The text was updated successfully, but these errors were encountered: