Skip to main content
Sometimes things go wrong, or you need a hand.
The self-hosted version of TryPost is supported by the community in their free time, on a best-effort basis. Post your question and be patient.

Discord

Flexible chat with screenshots and screen sharing — usually the fastest way to get help.

GitHub Discussions

Backup option if you can’t use Discord, or prefer an async thread.

​
TryPost Cloud — billing

For questions specific to a paid TryPost Cloud subscription (refunds, invoice changes, plan changes, account closure):
  • Use the in-app chat inside TryPost Cloud — open the chat widget while you’re signed in. That’s the right place for billing and account issues.
  • GitHub Issues are for bugs in the open-source app, not for billing.
  • Don’t share API keys, OAuth secrets, or payment details in Discord or other public channels.
Before opening a billing conversation, check Plans & billing — many billing questions are answered there.

​
How to ask for support effectively

Follow this order when you ask for help: Goal → Environment → Changes → Results.

​
Goal

Explain what you were trying to do:
  • I want to schedule a LinkedIn carousel for Friday at 6pm
  • I want to run TryPost in Docker on a VPS
  • I want to connect Instagram via Facebook Business

​
Environment

Share the relevant parts of your environment. Web app issues — browser and OS:
  • I’m using Chrome on macOS
  • I’m using Firefox on Windows 11
Self-hosted / install issues — machine and how you installed:
  • I’m on Ubuntu 24.04 with PHP 8.3, PostgreSQL, and Redis
  • This is a fresh Docker install on a Hetzner CX22
  • I’m on TryPost Cloud

​
Changes

What changed before it broke?
  • I updated my browser and now…
  • I pulled the latest release and now…
  • This used to work, but now…

​
Results

What happened, and what did you expect?
  • I see a blank screen
  • I get a 402 Active subscription required response
  • The post stays stuck in publishing
  • I expected the Instagram account picker, but got an error
Include screenshots, logs, or the exact error message when you can. That usually cuts the back-and-forth in half.