---
title: "Logs"
slug: "network-connector-logs"
updated: 2026-11-03T14:57:58Z
published: 2026-11-03T14:57:58Z
canonical: "docs.senhasegura.io/network-connector-logs"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.senhasegura.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Logs

This document provides information about the **Logs** report screen, where you can view the Network Connector operations that failed. Each record shows the error code that the Network Connector returned.

## Path to access

1. On Segura™, in the navigation bar, hover over the **Products menu** and select **Settings**.
2. In the side menu, select **Security policies and network > Network Connector > Logs**.

---

## Actions menu

| **Item** | **Type** | **Description** |
| --- | --- | --- |
| **Actions** | Dropdown menu | Displays the options *Print report, Export CSV* and *Schedule report.* |

## Search fields

| **Item** | **Type** | **Description** |
| --- | --- | --- |
| **ID** | Text field | Filter by your identification code within Segura™. |
| **Event** | Text field | Filters by type event. The options are: *Creation*, *List* and *Deletion*. |
| **Connector IP** | Text field | Filters by the IP address of the device registered as a Connector. |
| **Connector port** | Text field | Filters by the port that the IP is offering to the Connector service. |
| **Message** | Text field | Filters by log return message. |
| **Code** | Text field | Filters by the error code that the Network Connector returned for the failed operation. For the meaning of each code, see [Error codes](/docs/network-connector-logs#error-codes). |
| **Date/Time** | Date picker | Filters by the selected period. |

## Report fields

- **ID**.
- **Type**.
- **Connector IP.**
- **Connector Port.**
- **Message.**
- **Code.**
- **Date/Time.**
- **Actions**:
  - **Details**: opens the **Network connector log** screen.

Info

By default, the report displays 30 records per screen. To go to the next screen, click the forward buttons at the end of the report.

---

### Network connector log screen

| **Item** | **Description** |
| --- | --- |
| **ID** | Identification code within Segura™. |
| **Type** | Type of connector execution. |
| **Date/Time** | Date and time of the connector execution. |
| **Connector address** | IP address of the device registered as Connector. |
| **Connector port** | Port number that the IP is offering to the Connector service. |
| **Message** | Return message from the log. |
| **Details** | Full error text that the Network Connector returned. Use it with the code in [Error codes](/docs/network-connector-logs#error-codes) to identify the cause. |

## Error codes

The **Code** field shows the Network Connector's response to the request that Segura™ sent.

| **Code** | **Meaning** | **What to check** |
| --- | --- | --- |
| `0` | Segura™ did not receive a response from the Network Connector. The service is stopped, refused the connection, or did not respond in time. | Check that the Network Connector service is running. |
| `400` | The Network Connector rejected the request because of invalid data: an invalid destination address, a port outside the range 1–65535, a protocol other than TCP or UDP, or an agent port outside the allowed range. | Check the address and port configured on the resource that uses the connector, and the agent linked to it. |
| `404` or `405` | The Network Connector did not recognize the requested operation. This indicates that the Segura™ version and the Network Connector version are incompatible. | Contact Segura™ support. |
| `406` | The Network Connector could not reserve a port for the route. Either all available ports are in use, or the request uses UDP. Segura™ sends syslog messages through the Network Connector only over TCP, so every syslog message configured for UDP ends with this code. | If the records come from syslog, set the syslog **Message sending protocol** to **TCP**. For more information, see [How to configure the monitoring](/v4-2/docs/orbit-web-how-to-configure-the-monitoring). If all available ports are in use, contact Segura™ support. |
| `500` | Authentication between Segura™ and the Network Connector failed, the request was malformed, or an unexpected error occurred. | Contact Segura™ support and provide the date and time of the event. |