Skip to main content
If the user checks did not solve the problem, send enough detail for someone else to reproduce it. You do not need server logs when you use Presenton Cloud or do not manage the self-hosted server.

​
Include these details

  • Whether you use Presenton Cloud, the desktop app, or a self-hosted server
  • Your browser or desktop operating system and, if known, the Presenton version
  • What you were trying to do and the exact step that failed
  • Expected behavior, actual behavior, and whether the same test previously worked
  • The exact error text and a screenshot with private information removed
  • When it happened and whether it affects one presentation, one file, or everything
  • A small, safe example that reproduces the problem, when possible
  • For administrators or developers: sanitized logs, HTTP status, request identifier, task state, deployment method, and provider

​
Do not include

  • API tokens, passwords, cookies, private keys, signed URLs, or authentication headers
  • Provider secrets, database credentials, or complete environment files
  • Confidential source documents, presentation content, customer data, or internal screenshots
  • Personal information, access details, or production logs unrelated to the problem
For product support, email suraj@presenton.ai. For reproducible Open Source issues, use the Presenton GitHub repository after removing secrets and private data. Replace sensitive values with placeholders and create a small sanitized source file when reproduction requires an input.