Skip to Content
  •  +49 (861) 88 00 32 00
COD powered by extocode GmbH
  • 0
  • Sign in
  • English (US) Français Deutsch Español Türkçe
  • Open the demo
  • Home
  • COD Overview
    Platform
    OverviewPlatform: tenants and brandFeaturesProblems & SolutionsArchitectureDocumentationIntegrationsPricing
    Operations & Network
    MonitoringNetworkNetwork Access Control (NAC)TACACS+Captive PortalFirewall
    Security & Resilience
    Governance, Risk & ComplianceBackupHypervisorOTPPasskeeprAutomation
    Solutions & More
    NIS2 & CompliancecodPassAI documentation (InfraScan add-on)Open the demoReferencesDownloadsFAQ
  • Pricing
  • News
    • Blog
    • Roadmap
  • FAQ
  • About us
    • About us
    • Careers
    • Partners
    • References
  • Academy
  • Contact
COD powered by extocode GmbH
  • 0
    • Home
    • COD Overview
    • Pricing
    • News
      • Blog
      • Roadmap
    • FAQ
    • About us
      • About us
      • Careers
      • Partners
      • References
    • Academy
    • Contact
  •  +49 (861) 88 00 32 00
  • English (US) Français Deutsch Español Türkçe
  • Sign in
  • Open the demo
  1. Home
  2. Documentation
  3. Troubleshooting

Troubleshooting

This page collects known issues with symptom, cause and solution. The commands for diagnosis are at the end.

As of: November 2026, COD 3.8.6

Documentation contents
  • Overview
  • Getting started
  • Requirements
  • Names and addresses
  • Network devices
  • Time and DNS
  • Installation
  • Deployment shapes
  • Initial setup
  • Updates
  • Modules
  • Troubleshooting
  • Security
  • Versions
  • Version history
  • Support

Documentation

  • Overview
  • Getting started
  • Requirements
  • Names and addresses
  • Network devices
  • Time and DNS
  • Installation
  • Deployment shapes
  • Initial setup
  • Updates
  • Modules
  • Troubleshooting
  • Security
  • Versions
  • Version history
  • Support

Overview

AreaIssue
NetworkNo link between two switches in layer 2
NetworkDevice missing from the topology
Network"port discovery failed"
NetworkQuery counts as failed although SSH worked
NetworkQuery error because of an unknown manufacturer
MikroTikNo routes and empty live views
Backup"All configured authentication methods failed"
Backup"Permission denied" during download
BackupHost shows ERROR because of the name check
NACNo NAC sessions on the port
Sign-inSign-in over HTTP fails
Sign-inTerminal or Passkeepr hang behind a reverse proxy
PasskeeprBrowser extension is rejected
ModulesModule not visible after enabling it
ModulesField for the TACACS+ address is missing
OperationsAudit status "degraded"
MonitoringZabbix link lost after renaming
FirewallFirewall does not appear in the module
InstallationAnsible rollout fails after an address change
InstallationErrors after a reinstallation

Network and topology

No link between two switches in layer 2

  • Symptom: Two switches are connected. The layer 2 map shows no link.
  • Cause: COD matches an LLDP neighbour to an asset by its system name. If the name differs from the asset name by even one character, no link is created. Or the switch does not send its system name via LLDP.
  • Solution: Align the asset name and the device's hostname. Send and receive LLDP on all switch and router ports, with system-name, system-description, system-capabilities, management-address and port-description. With some manufacturers you enable this per port.

See Preparing network devices and Names and addresses.

Device missing from the topology

  • Symptom: Cameras, storage systems, building services or other end devices do not appear in the layer 2 map.
  • Cause: COD draws links from the LLDP data of switches and routers. Devices without LLDP never appear automatically.
  • Solution: Draw these devices into the topology manually. Monitor their availability through the Zabbix connection.

"port discovery failed"

  • Symptom: A network object stays in the status "port discovery failed".
  • Cause: The device does not provide a port MIB (IF-MIB) via SNMP. This mainly affects small switches.
  • Solution: Check whether the device answers the IF-MIB via SNMP. If it does not, COD does not capture its ports. Draw the device into the topology manually if needed.

Query counts as failed although SSH worked

  • Symptom: The query of a network object counts as failed. Data via SSH, such as LLDP neighbours or clients, still arrives.
  • Cause: If the port discovery via SNMP fails, the whole query counts as failed, even if SSH worked.
  • Solution: Check SNMP on the device. COD queries SNMP v1 and v2c with a community. The community must be correct, the access list on the device must allow COD's source address, and the port MIB must answer.

Query error because of an unknown manufacturer

  • Symptom: The query of a network object ends with an error.
  • Cause: The manufacturer and model family on the asset decide which collector runs. An unknown manufacturer results in an error.
  • Solution: Choose the correct manufacturer and family from the catalogue on the asset. COD captures devices from Allied Telesis, Arista, Aruba, Cisco, Extreme, Juniper, MikroTik, Ruijie and Sophos. See Integrations.

MikroTik: no routes and empty live views

  • Symptom: The layer 3 map shows no routes for a MikroTik router. The live views stay empty.
  • Cause: COD reads routes, addresses, neighbours and interfaces through the RouterOS REST interface. If the interface is off on the router or blocked for COD, the data stays empty. Also note: if you edit a router in COD while it is unreachable, COD deletes its stored routes.
  • Solution: For the MikroTik sync, the router’s REST interface must be reachable for COD. You receive the details as part of the project. Restrict access to COD's source address and create a dedicated user with limited rights for COD. Edit routers only while they are reachable. You receive the minimum rights as part of the project.

See Network and MikroTik.

Backup

"All configured authentication methods failed"

  • Symptom: Backups fail with "All configured authentication methods failed" although the credentials are correct.
  • Cause: Too many simultaneous SSH sessions against the same target. RouterOS, for example, allows 20 SSH sessions.
  • Solution: Stagger the start times of the backups if many backups run over the same path.

"Permission denied" during download

  • Symptom: A backup of type Download fails with "Permission denied".
  • Cause: A subfolder is not readable for the backup user. A single such folder aborts the whole download. A regular expression in the template does not prevent this.
  • Solution: Give the user read access to all subfolders, or back up a folder without restricted subfolders. Files and folders with a leading dot are skipped by the download anyway.

Host shows ERROR because of the name check

  • Symptom: A backup host shows ERROR.
  • Cause: "Check Server Name" is enabled, and the hostname on the device differs from the "Server Name" in COD.
  • Solution: Align the hostname on the device and the "Server Name". See Names and addresses.

More about the module under Backup.

NAC

No NAC sessions on the port

  • Symptom: Devices authenticate via RADIUS. Still, no NAC sessions appear in the port dialog under "Port History".
  • Cause: The switch does not send RADIUS from its management address.
  • Solution: Set the RADIUS source address on the switch to the management address. Also send accounting so that COD shows statistics.

See NAC.

Sign-in and access

Sign-in over HTTP fails

  • Symptom: Sign-in through an address starting with http:// does not work.
  • Cause: COD sets its session cookies for secure connections only. HTTPS is mandatory, except locally on the COD server.
  • Solution: Set up HTTPS. The options are under Initial setup: HTTPS.

Terminal or Passkeepr hang behind a reverse proxy

  • Symptom: Behind a reverse proxy, the terminal does not open a session, or Passkeepr hangs.
  • Cause: The terminal needs WebSocket, Passkeepr needs server-sent events. The proxy does not pass one of them.
  • Solution: Let WebSocket and server-sent events pass on the proxy and enable "trust proxy" in COD. You receive a sample configuration as part of the project.

Passkeepr browser extension is rejected

  • Symptom: COD rejects the Passkeepr browser extension.
  • Cause: The extension version is too old. Since COD 3.8.6, at least version 3.3.6 is required.
  • Solution: Install the current extension from Passkeepr. It needs Chrome 137 or later or Firefox 140 or later.

See Passkeepr.

Modules

Module not visible after enabling it

  • Symptom: A module is enabled for the tenant but does not appear.
  • Cause: Enabling takes effect only after a new sign-in.
  • Solution: Sign out and sign in again. For Passkeepr, your role also needs the right for the module.

Field for the TACACS+ address is missing

  • Symptom: The field for TACACS+ is missing under "Location > Module URLs".
  • Cause: The field only appears if NAC, Backup or Passkeepr is also enabled for the tenant.
  • Solution: Clarify the enabled modules with your partner. The address you enter must end in /api/v1.

See TACACS+.

Operations, monitoring and firewall

Audit status "degraded"

  • Symptom: The audit status shows "degraded".
  • Cause: Time synchronisation is missing on the COD server, a database server or a module server.
  • Solution: Set up NTP on all servers involved. See Time and DNS.

Zabbix link lost after renaming

  • Symptom: On the next day an asset is no longer linked to its Zabbix host.
  • Cause: The host was renamed in Zabbix. The nightly sync compares full names and removes the link.
  • Solution: Keep the asset name and the Zabbix hostname identical. Then link the asset again through the list of unmonitored assets. COD never deletes hosts in Zabbix.

See Monitoring.

Firewall does not appear in the module

  • Symptom: A firewall does not appear in the Firewall module.
  • Cause: The module needs the built-in asset type "Firewall", an activated asset and a manufacturer. If the type was renamed, COD does not recognise the firewall.
  • Solution: Do not rename the built-in type "Firewall". Activate the asset and set the manufacturer.

See Firewall.

Installation

Ansible rollout fails after an address change

  • Symptom: After COD's public address has changed, Ansible rollouts fail.
  • Cause: The name under which COD is reachable matters for the browser's origin check, the certificate and the issuer of the sign-in tokens.
  • Solution: Roll out Ansible again for the affected locations. Decide on COD's name before the installation.

Errors after a reinstallation

  • Symptom: After removing and reinstalling COD on the same host, errors occur.
  • Cause: apt purge leaves configuration and data in place. The cache (Redis or Valkey) still holds entries of the old installation.
  • Solution: Clear the cache before the reinstallation. See Updates: removing COD.

Diagnosis

Run these commands on the affected host.

CommandWhat it shows
systemctl list-units 'cod-*'state of all COD services on the host
journalctl -u log of one service, for example journalctl -u cod-backend
curl -sk https://localhost/api/healthstate of COD. Expected is {"status":"ok"}
apt policy cod-backendinstalled and available version

In the interface, "Admin Area > Log" shows the logs of COD. Under "Service" you can also select services such as NAC, Backup, Passkeepr and TACACS+.

Contacting support

Your partner is the first point of contact. What to have ready for a request is described under Support. Technical questions to extocode go through the helpdesk form. See Support.

Further reading

  • Requirements
  • Check the installation
  • Modules
  • Support
  • FAQ: support and help
← Previous: Inventory and CMDB importNext: Security →
Folgen Sie uns
​
  • COD Overview
  • Features
  • Demo
  • Pricing
  • Integrations
  • NIS2
  • codPass
  • References

Help

  • FAQ
  • Documentation
  • Downloads
  • Contact

Kotzinger Straße 21 • 83278 Traunstein • Deutschland

  • ​+49 (861) 88 00 32 00
  • ​info@extocode.com
Datenschutz Impressum ​
Copyright © extocode GmbH
English (US) Français Deutsch Español Türkçe

We use cookies to provide you a better user experience on this website. Privacy Policy

Decline Accept