Troubleshooting overview
Where to start when something is not working in Acrosite: read the logs, find the failing stage, and jump to the right fix.
When something is not working in Acrosite, a short, consistent approach finds the cause fast: read the logs, identify the stage that failed, then jump to the right fix. This page is your starting point.
Start with the logs
Most issues show up in the logs, which are read-only and sanitized:
- Publish Logs record each publishing job — validation, the GitHub commit, and the deployment trigger. See Understand Publish Logs.
- Deployment Logs record each deployment trigger request and its response. See Understand Deployment Logs.
- The workspace Activity log shows important events across people, content, publishing, integrations, billing, and security. See Read the workspace activity log.
The failing stage points you to the fix.
Common problems
- GitHub is not connected, or a commit failed — see Fix GitHub connection issues.
- The deployment trigger did not fire — see Fix deployment trigger failures.
- Content is Published but not on your site — see Content is not showing on my site.
- A publish failed — see Troubleshoot publishing failures.
- An action is blocked — see Permission errors and What to do at a plan limit.
What to avoid
Warning
Never share secrets, tokens, deployment hook URLs, or passwords when asking for help — Acrosite keeps these out of the interface and logs on purpose, and support never needs them.
Next steps
Frequently asked questions
Start with the logs. Publish Logs show which stage of a publish failed — validation, the GitHub commit, or the deployment trigger — and Deployment Logs show whether the trigger was accepted. The failing stage tells you which fix to use.
The logs are sanitized and do not show tokens, hook URLs, or raw payloads, so there is nothing secret to redact. Still, never paste secrets or tokens into a support request — they are not needed.
Usually not. "Published" means Acrosite committed your content and triggered your host to rebuild; it does not track the build to completion. Confirm the finished build in your provider's dashboard.