Sosyabot Docs

English

Türkçe

English

Türkçe

Appearance

Troubleshooting ​

Find the line that sounds like what you're seeing, then follow the fix. Deep commands for self-hosters are tucked into a fold at the bottom so this page stays simple.

Signing in and email ​

  • "I never got the verification email." — Check your spam or junk folder first. The code can take a minute or two. If it still hasn't arrived, ask whoever set up your workspace to re-send it, or reach out via Get Help.
  • "It keeps saying 'verify your email' even after I clicked the link." — Try signing out and back in once. If you're still stuck, an admin can mark your account as verified for you from Users.
  • "It says I'm trying too many times / I'm locked out." — For security, sign-in and code requests are limited for a short window. Wait about 15 minutes and try again. If you're sure your password is right and it still won't let you in, ask your admin.

Connecting accounts ​

  • "It says my account needs reconnecting." — This is normal and happens when the social platform expires Sosyabot's permission (for example after a password change or a security check on their side). Just go to Connections and reconnect that account in one click.
  • "My Telegram channel won't post." — The Sosyabot bot needs to be a member (and usually an admin) of that chat or channel. Open the chat in Telegram, add the bot, and try again.
  • "I clicked connect and landed on an error / blank page." — Close that tab and start the connect flow again from Connections. If it keeps failing on the same platform, note which one and contact support.

Publishing ​

  • "My post didn't go out." — First check whether the connected account is healthy on Connections (a "needs reconnecting" account can't post). If the account is fine, the scheduled time may not have arrived yet, or the post may still be processing — give it a few minutes.
  • "My post still says it's pending / scheduled long after the time." — Open the post and try sending it again. If a whole batch is stuck, it's usually a temporary backend hiccup — wait a few minutes or ask your admin to check the service.
  • "My image won't upload." — The file is probably too large. Shrink or compress the image and try again. Very large files are rejected to keep things fast.

AI ​

  • "I ran out of AI credits." — Each workspace gets a pool of AI credits that refills on the 1st of the month. You can wait for the reset, or upgrade your plan for a bigger allowance.
  • "AI text or image generation keeps erroring." — This usually means the AI model isn't responding right now. Wait a moment and retry. If it keeps failing for everyone in your workspace, let your admin know so they can check the AI setup.
  • "Where did the marketplace agent I installed go?" — Installed agent recipes arrive switched off on purpose. Open the agent, review its settings, and turn it on when you're ready. See Agents.
For self-hosters (CLI, services, and API)

These are the deeper fixes that need server access. Skip this section if you're a normal user.

Sign-in and email

  • OTP email never arrives — verify SMTP credentials and re-send the test email from the admin SMTP settings, then check spam.
  • Stuck on "verify your email" — flip isVerified: true for the user from the admin Users area.
  • Rate-limited — auth endpoints cap at 10 requests / 15 min, OTP at 20 / 15 min. Wait out the window or adjust limits.

Connections

  • Channel keeps showing needs_reconnect — the provider revoked Sosyabot's token (user revoked authorization, password change, security event). Re-run the connect flow.
  • OAuth callback 404 — the redirect URI registered with the provider doesn't match <BASE_URL>/api/v1/auth/<platform>/callback. Fix the registered redirect URI.

Publishing

  • Scheduled posts don't fire — verify the worker is running with ./service.sh status. Check ./service.sh logs worker for stack traces.
  • Post stuck in pending — the BullMQ queue lost the job. Re-trigger with PATCH /api/v1/posts/:id/status { status: 1 }.
  • Image upload fails with 413 — the image exceeds the configured storage cap (default 50 MB).

AI

  • Image generation returns 402 — workspace AI credits are exhausted. Upgrade or wait for the cycle reset on the 1st.
  • Inline AI returns generic errors — the configured Qevron model isn't available; the model resolver must filter category: "text". Test the model from the admin AI Models area.

Get Help

Connections

Glossary