Support
This page shows whom to contact with questions about COD and what to have ready for a request.
As of: November 2026, COD 3.8.6
Documentation
Contacts
| Matter | Route |
|---|---|
| Questions on rollout and operation | Your partner. Your partner is the first point of contact for support |
| Bugs | Your partner |
| Technical questions to extocode | Through the helpdesk form, if your partner cannot help |
| Feature requests | Feedback channel in COD or your partner |
| Vulnerabilities | Confidentially by e-mail to security@extocode.com. See Reporting vulnerabilities |
| You do not have a partner yet | Through the contact form, extocode puts you in touch with a suitable partner |
How working with partners looks is described on the Partner page.
Helpdesk form
- First clarify your request with your partner. Your partner knows your environment and can solve many things directly.
- If a technical question remains open, submit it through the helpdesk form. This applies to customers and partners.
- Have the details from the next section ready. A complete request saves follow-up questions.
We do not commit to response times through this form.
Feedback channel in COD
- The “Feedback” module takes bug reports and requests from within COD.
- COD sends the message to the vendor's issue tracker, otherwise by email.
- If COD is connected to the issue tracker, you see the status of your message in COD.
- A message leaves the installation only when a user deliberately sends it.
- This does not commit us to implementing a request.
What to have ready for a request
| Detail | Where to find it |
|---|---|
| COD version | apt policy cod-backend, see Checking your version |
| Operating model | Self Hosted, Shared Hosted or Private Hosted |
| Deployment shape | One server, or separate module servers and database servers, see Deployment shapes |
| Affected module and location | Name of the module and the location from the top bar |
| Time | Date and time with time zone when the error occurred |
| Symptom | What you did, what you expected, what happened. Error message word for word |
| Diagnostic output | Output of the commands below |
| Log | Entries from “Admin Area > Log” at that time. You pick service logs under “Service” |
Diagnostic commands
On the COD server, and with separate servers also on the affected module server:
systemctl list-units 'cod-*'
systemctl --failed
journalctl -u cod-backend --since today
curl -sk https://localhost/api/health
apt policy cod-backend
| Command | What it shows |
|---|---|
systemctl list-units 'cod-*' | State of all COD services |
systemctl --failed | Services that are not running |
journalctl -u cod-backend --since today | Log of one service since today. For another service, use its name from the systemctl list |
curl -sk https://localhost/api/health | Returns {"status":"ok"} when COD is running |
apt policy cod-backend | Installed and available release |
Note: Do not send passwords, keys, tokens or SNMP communities. Check output, logs and screenshots before sending and black out such details.
With Shared Hosted and Private Hosted, extocode operates the instance. The commands on the COD server then do not apply to you. Have the other details ready.
Help yourself
- Troubleshooting: common errors with cause and solution
- Support FAQ
Training and demonstration
| Offer | For whom | Route |
|---|---|---|
| Online product training | Partners, free of charge, with a certificate of completion | Partner |
| Demo | Everyone, no appointment needed. The real software with the data of a fictional company, reset every night | Open the demo |
| Personal demonstration | Prospects, free of charge and without obligation | Request a personal demonstration |