Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Instagram Shortcode broken getJSON failure #5659

Closed
tfolbrecht opened this issue Jan 31, 2019 · 5 comments
Closed

Instagram Shortcode broken getJSON failure #5659

tfolbrecht opened this issue Jan 31, 2019 · 5 comments

Comments

@tfolbrecht
Copy link

The Instagram Shortcode isn't working, getJSON error even though the addresses are valid and able to be fetched with my browser

Probably related to #5643 (comment)

I'll try looking into it and writing a build test. (I'm a noob)

screenshot from 2019-01-31 10-24-12
screenshot from 2019-01-31 10-24-59

@bep
Copy link
Member

bep commented Feb 1, 2019

I have merged #5643 -- and I cannot reproduce this particular issue -- the instagram examples on the docs site works fine (I have cleared the cache).

@pawelgrzybek
Copy link

I am having similar issue with tweet shortcode.

Building sites … ERROR 2019/02/01 10:12:24 "/Users/pgrzybek/Sites/pawelgrzybek.com/content/posts/2018-06-30-top-picks-2018-june.md:15:1": failed to render shortcode "tweet": failed to process shortcode: template: _internal/shortcodes/tweet.html:7:13: executing "_internal/shortcodes/tweet.html" at <getJSON $url>: error calling getJSON: failed to get getJSON resource "https://api.twitter.com/1/statuses/oembed.json?id=1003623284829638659&dnt=false": Get https://api.twitter.com/1/statuses/oembed.json?id=1003623284829638659&dnt=false: x509: certificate signed by unknown authority

screenshot 2019-02-01 at 10 11 12

It happened to me after update from v50 to v53.

@pawelgrzybek
Copy link

I can confirm that version. 0.54 fixed my issues.

@pawelgrzybek
Copy link

Thank you a lot for rapid action @bep

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants