Meta OAuth blocks Facebook and Instagram channel connections
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- authentication
Research direction
Start by reviewing the Meta OAuth app configuration and the Instagram Standalone callback involved in the reported flows. Reproduce Facebook Page, Instagram Business, and Instagram Standalone connections in the EveryFeed web app; done means each supported account returns with Connected status and appears in MCP listConnectedChannels.
Written by the indexing model from the issue text.
Description
Summary
EveryFeed cannot connect Facebook Pages or Instagram accounts through the supported Meta OAuth flows.
What happened
On 2026-09-07, from EveryFeed → Connections → Connect a channel:
- Facebook Page: Facebook returned:
Facebook Login is currently unavailable for this app, since we are updating additional details for this app. Please try again later.
-
Instagram (Facebook Business): the flow redirected to Facebook and returned the same error.
-
Instagram (Standalone): Instagram authorization completed, but EveryFeed redirected to a callback page showing:
Instagram (Standalone) rejected the post. Please check the content, settings, and media attachments.
After all attempts, EveryFeed MCP listConnectedChannels still returned only the existing X and YouTube connections. No Facebook or Instagram connection was created.
Expected behavior
The Facebook Page and Instagram account should return to EveryFeed with a Connected status and be available for publishing.
Environment
- EveryFeed web app
- Microsoft Edge
- Organization channel usage was 2 / 5, so this was not the channel limit
- Reproduced on 2026-09-07
Request
Please investigate the Meta OAuth app configuration and the Instagram Standalone callback. In particular, please confirm that the Facebook Login / Instagram permissions are live and approved for non-admin users, and advise whether there is a current workaround or ETA for resolution.
Because Facebook and Instagram are advertised supported channels, please also advise whether a billing credit or other remedy is available while these connections are unusable.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from VoltAgent/everyfeed-agent
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in VoltAgent/everyfeed-agent
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
[Bug]: 2026.10.10-beta.5 drops the #179205 shared-OAuth deleted-peer fix (regression of #178908)Openclawsweeper:needs-maintainer-review clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:auth-provider issue-rating: 🦞 diamond lobster P1
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
openclaw/openclaw#190705 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
esphome/home-assistant-addon#274 ·
-
backend Low Priority subtask
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Bearkat-Professionals/Software-Engineering-Project#87 ·
Maintainers usually reply within 1 day