יש לי כמה בעיות בהגדרת הטמעת טוויטר

תמיכה

סיכום מבוסס בינה מלאכותית

MystereEugene reported issues with Twitter onebox embeds on their self-hosted Discourse instance (installed via Docker on DigitalOcean), despite correctly configuring Twitter API keys as per the official guide. They encountered 404 errors when fetching Twitter posts, even after rebuilding HTML and testing settings. Disabling keys resulted in broken previews with tiny images and missing @ handles. They questioned whether regional factors (France/OVH DNS/RGPD) or misconfigured OAuth v1 settings were to blame, and noted direct links failed with “unable to generate a preview” messages. In a follow-up, MystereEugene resolved the issue by upgrading their Twitter Developer account from Essential to Elevated tier — a free step that enabled Twitter embeds to work correctly.

1

Hello all, have a self hosted server on DigitalOcean using the “30 minutes” install via docker.

Run well, but I’ve some problems with the onebox embed on twitter post.

I’ve used the config manual here

I set my dev keys (consumer and secret consumer) and relaunch the app.

But Onebox give me a 404 error retrieving the twitter post?

Screenshot 2022-07-17 at 15.02.55
Screenshot 2022-07-17 at 15.02.552636×1168 260 KB

Testing the wrench key and rebuild HTML thing, same problem.

If I unset the keys, the post is ok but the @ is empty and the size of picture very very small

So I’ve some questions and need hints…

  1. I’m in France, using OVH for DNS, may be a problem for twitter post recovery in Europe? (a RGPD thing…). Do I need a special config?
  2. I misuse the Twitter dev config? I’ve set OAuthV1 (seem to be used for login only thing but…)
  3. a direct link give me an unable to generate a preview for this web page, is it a “normal” thing?

I’m a little lost for now. Thanks you for any help!

2

I’ve found it !

You need to escalate your developer Twitter account from Essential to Elevated (free).

And then it’s work like a charm.