OpenPostFix a connection
Fix configuration, callback, account access, and media errors.
Find the failed step below. If the account connects but a post fails, inspect its variant's error and use publishing troubleshooting.
The network is not configured
- Check Settings → Instance → Configuration → Provider apps as the instance administrator. Bot apps and Pinterest use
OPENPOST_PROVIDER_APPSin the deployment instead. - Confirm the provider and client ID match your developer app. Keep all environment entries in one valid JSON array. Environment values take precedence over database entries, including older provider variables.
- After editing
.env, rundocker compose up -d --force-recreate openpost. A plain restart keeps the old environment. After saving app credentials in Settings, restart OpenPost.
See saving provider credentials.
The callback URL is rejected
Compare the portal's redirect URI, OpenPost's redirect_uri, and OPENPOST_APP_URL with the exact path in the provider guide. Check scheme, host, port, path, and trailing slash. Use the callback path, not the app homepage.
After a domain change, update both configurations, restart OpenPost, and start a new connection. Do not reuse an old sign-in tab or authorization code.
The connection expired or the window closed
Start again from Social accounts. Keep the same OpenPost session and workspace open while finishing the provider's sign-in. Allow its popup if the browser blocks it.
A Page or account is missing
Sign in as someone who can manage the destination. Public visibility does not grant publishing access.
| Network | Check |
|---|---|
| Page access and Business Portfolio assignments | |
| Business or Creator account. Facebook Login also needs a linked Page you manage; direct Instagram login does not. | |
| Member profile versus Organization Page permissions | |
| YouTube | Google identity and channel selection |
Reconnect after correcting access. Include the intended destinations in the consent flow.
Only test users can connect
Check the developer app's mode, tester list, and approved permissions. Complete the provider's review before inviting other users. Reconnect accounts after approval of new scopes.
Pinterest, Telegram, and Discord bot mode also need OpenPost readiness records.
Media cannot be downloaded
- Open a harmless uploaded image's exact URL from outside your network, without an OpenPost session.
- Confirm it returns the file over HTTPS with the correct content type. A sign-in page, private hostname, expired link, or VPN-only address will fail.
- Compare its type and size with media requirements. For TikTok, check verified domain or URL-prefix settings too.
An account needs reconnecting
Reconnect from Social accounts after changes to passwords, roles, app permissions, or tokens. Confirm the same destination appears.
After rotating an app secret, update OpenPost, restart it, and check affected accounts. Replace a rotated Discord webhook connection. Follow Telegram's setup again after rotating a bot token.
Before retrying a failed post, check whether the provider already published it.
Report a setup problem
Open a GitHub issue with the provider, OpenPost version, failed step, visible error, and whether text and media behave differently. Replace your domain with post.example.com when sharing callback examples. Remove secrets, tokens, webhook URLs, cookies, and authorization codes from screenshots and logs.