Support Center

How can we help you?

Select your deployment path below to route your inquiry or browse our edge-native developer knowledge base.

Self-Hosted / Open-Source

Independent Cloudflare Stack

Running Pouta on your own Cloudflare infrastructure? Report environment issues, code glitches, or suggest layout feature requests directly on our Github repository.

Report an Issue

SaaS Pro & Billing

Active Stripe Subscription

Need to cancel, update payment details, upgrade or review your active SaaS Pro subscription invoices? Manage your account immediately inside the secure customer billing portal.

Manage Subscription

Developer Knowledge Base Self-Service

Search or expand a topic to resolve edge-native sync issues.

1. How do I clear Cloudflare Edge Cache for instant content invalidation?

Pouta leverages Cloudflare’s global edge cache to render blog files instantly. If you submit a block edit but do not see it update immediately on your static site generator:

Ensure your deployment pipeline on Cloudflare Pages is configured to trigger a deployment webhook upon new GitHub push events.
If using a Custom Domain with caching rules, you can force invalidation inside the Cloudflare Dashboard under Caching > Configuration > Purge Cache > Purge Everything.
For programmatically driven custom headless setups, call the Cloudflare API Cache Purge endpoint using your specific Cache Tags or absolute routing paths.

Tip: Pouta SaaS Pro handles cache tagging automatically, ensuring instant local purging the second you click publish in the Block Editor canvas.

2. Why are my GitHub commits failing to synchronize with Pouta?

If Pouta displays database synch errors or fails to make commits to your configured markdown repository:

Check Installation Scope: Verify that the Pouta GitHub App is authorized to access the specific repository. Visit your GitHub Account Settings under Applications > Installed GitHub Apps > Pouta CMS > Configure.
Branch Protection Gates: Verify if your target branch (e.g. main) has strict Branch Protection Rules requiring signed commits or pull reviews. You may need to grant the Pouta collaborator access exceptions.
Expired Session Token: In rare cases, your developer OAuth session might expire. Log out of the Pouta Dashboard and log back in to refresh your short-lived access credentials.

3. How do I resolve Cloudflare D1 SQLite database migration locks?

When running schema migrations on your self-hosted Cloudflare D1 SQLite databases, you might occasionally face database execution locks or SQLite transaction conflicts:

Disable Concurrent Wrangler Commands: Ensure you don't have multiple parallel terminal migrations running via wrangler simultaneously.
Local Syncing: If developing locally, ensure your wrangler environment state resides in the correct .wrangler/state/v3/d1 path. Copy production states down carefully.
Wait Limits: SQLite allows multiple read transactions but only a single write lock. Ensure complex backup scripts do not hold long-running locks during active writer sessions.

4. How do I configure Cloudflare R2 CORS policies for image uploading?

If your self-hosted Pouta dashboard triggers a Preflight CORS Error when dragging images onto the editor canvas, your Cloudflare R2 bucket lacks standard cross-origin allowances.

To fix this, go to your Cloudflare dashboard, select R2, open your target media bucket, click the Settings tab, scroll down to CORS Policy, click Add CORS Policy, and paste:

[
  {
    "AllowedOrigins": ["https://your-pouta-domain.com"],
    "AllowedMethods": ["GET", "PUT", "POST", "DELETE"],
    "AllowedHeaders": ["*"],
    "ExposeHeaders": []
  }
]

Replace https://your-pouta-domain.com with your CMS URL, click save, and the editor image pipeline will execute smoothly.