Twitter is currently blocking IPs from large hosting companies such as DigitalOcean and Hetzner from using their embed endpoints. Without being able to access Twitter there’s not much Ghost’s embed implementation can do.
There are threads on the Twitter dev community forum to follow for any response from Twitter but so far they’ve been largely ignored:
- https://twittercommunity.com/t/issue-with-twitter-oembed-api-when-accessed-from-digitalocean-droplets/194215/19
- WordPress Fails to Embed Tweets - #23 by udenizgenc - Twitter for Websites - Twitter Developers
Which purpose does the remaining Twitter Card now have if it can’t be used?
There’s no specific Twitter card, there’s just an embed card which is the same for all embeds (the card menu icons are named shortcuts to the generic embed card).
Until Twitter removes the IP block or provides an alternative embed method the only way to embed a tweet is via a HTML card and manually copy/pasting from the tweet’s embed UI, or creating an image of the tweet.