# Get help with oCMS

*Published: 2026-11-03*

Get help with installing, publishing or operating oCMS. Start with the guide for your task, then include a small, reproducible example when you need more help.

## 1. Find the right guide

- **Cannot start a new installation:** check [installation troubleshooting](/download#installation-help) and [configuration](/configuration).
- **Cannot sign in or complete MFA:** follow [account recovery](/account-security#recover-access).
- **Editing, images or translations:** use the [editor's guide](/editors-guide).
- **Form validation, captcha or saved submissions:** use the [contact form walkthrough](/forms-guide).
- **Theme layout or settings:** use [theme customization](/theme-customization) and the [theme gallery](/themes).
- **API authentication or failed requests:** check the [API error guidance](/api-cookbook#handle-errors).
- **A server or upgrade problem:** use [deployment](/deployment), [upgrading](/upgrading) and [backup and restore](/backup-and-restore).

## 2. Check the version and health

From the directory containing your extracted binary, record its version:

```
./ocms -version
```

For the default local quick start, check the application's response:

```
curl --fail --silent --show-error http://127.0.0.1:8080/health
```

Adjust the host and port for your installation. For a public site, also check its HTTPS health URL. An HTTP 200 response establishes that the health endpoint answers; still check the page, image, sign-in or API request involved in the problem.

## 3. Collect useful context

Record the operating system and architecture, installation method, active theme and relevant enabled modules. Describe whether the issue affects a local copy, production, or both. Include the browser and viewport for a layout problem, and the HTTP status for a failed request.

If you followed the deployment guide's systemd example, inspect recent application logs with:

```
sudo journalctl -u ocms-site -n 50 --no-pager
```

Use your actual service name if it differs. Include only the relevant error and nearby context, with private values removed. Keep passwords, API keys, session cookies, recovery codes and complete database backups out of reports. A full environment dump is not needed.

## 4. Prepare a reproducible bug report

Copy this template and replace the placeholders. A short sequence starting from a known state is more useful than a screenshot alone.

```
oCMS version:
Operating system and architecture:
Installation method:
Active theme and relevant modules:
Browser and viewport, if relevant:

What I expected:
What happened instead:

Steps to reproduce:
1.
2.
3.

Relevant HTTP status or redacted log excerpt:
Small example or public page URL, if available:
Does it also happen in a separate local copy?
```

## 5. Choose a contact option

For a reproducible software bug, search the [GitHub issues](https://github.com/olegiv/ocms-go/issues) for an existing report. Add useful reproduction details to a matching issue, or open a new one with the template above.

For a question, website feedback, an accessibility barrier or a matter that should not be public, email [webmaster@ocms.tech](mailto:webmaster@ocms.tech). Describe the issue without sending credentials or private records. For an accessibility report, include the affected URL and the browser or assistive technology; see the [accessibility feedback guidance](/accessibility-statement#accessibility-feedback).

## 6. Follow up with what you learn

Keep related details in the same issue or email conversation. If a suggested change helps, report the result and the version you tested. Rehearse upgrades or recovery steps against a separate copy before changing a live site; the [upgrade walkthrough](/upgrading) covers that process.

Reports and questions help identify improvements. Return to the [documentation overview](/docs) for the complete set of local guides.

---

[Source](https://ocms.tech/support)