From 9be8245f31ae977a7f5036b5913f2f081833d6d6 Mon Sep 17 00:00:00 2001 From: hilram7 Date: Mon, 29 Dec 2025 16:53:38 -0500 Subject: [PATCH 1/3] Add Change Tracker KB folder and migrate initial articles - Initialize Change Tracker KB section with category configuration - Migrate 4 articles from general KB section to Change Tracker - Add _category_.json configuration for Change Tracker KB - Re-tag articles with appropriate product metadata Restored from archived repository with clean commit history. --- docs/kb/changetracker/_category_.json | 6 ++ .../corrupt-errorevent-in-event-reports.md | 67 +++++++++++++++++++ ...d_by_core._files_in_gen_7_agent_servers.md | 29 ++++++++ ...ificate_thumbprint_does_not_match_trust.md | 63 +++++++++++++++++ ...essage_ip_address_blocked_loginfailures.md | 58 ++++++++++++++++ 5 files changed, 223 insertions(+) create mode 100644 docs/kb/changetracker/_category_.json create mode 100644 docs/kb/changetracker/audit-and-logging/corrupt-errorevent-in-event-reports.md create mode 100644 docs/kb/changetracker/database-and-diagnostics/disk_space_occupied_by_core._files_in_gen_7_agent_servers.md create mode 100644 docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_error_nnt.hub.serviceclient.hubadapter_-_certificate_thumbprint_does_not_match_trust.md create mode 100644 docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_hub_connection_failed._403_server_message_ip_address_blocked_loginfailures.md diff --git a/docs/kb/changetracker/_category_.json b/docs/kb/changetracker/_category_.json new file mode 100644 index 0000000000..8163414625 --- /dev/null +++ b/docs/kb/changetracker/_category_.json @@ -0,0 +1,6 @@ +{ + "label": "Change Tracker Knowledge Base", + "position": 999, + "collapsed": true, + "collapsible": true +} diff --git a/docs/kb/changetracker/audit-and-logging/corrupt-errorevent-in-event-reports.md b/docs/kb/changetracker/audit-and-logging/corrupt-errorevent-in-event-reports.md new file mode 100644 index 0000000000..fb5ac3055a --- /dev/null +++ b/docs/kb/changetracker/audit-and-logging/corrupt-errorevent-in-event-reports.md @@ -0,0 +1,67 @@ +--- +description: >- + If Netwrix Change Tracker events reports contain ErrorEvent entries labeled + "Corrupt", multiple conflicting agent configuration files may be present on + affected devices. This article explains how to identify affected agents and + perform an agent reset to resolve the issue. +keywords: + - Netwrix Change Tracker + - ErrorEvent + - Corrupt + - agent reset + - gen7agent + - rolling-log + - Hubdetails.xml + - Config-*.xml + - AgentID +products: + - change-tracker +sidebar_label: Corrupt ErrorEvent in Event Reports +tags: + - audit-and-logging +title: "Corrupt ErrorEvent in Event Reports" +knowledge_article_id: kA0Qk0000000ahpKAA +--- + +# Corrupt ErrorEvent in Event Reports + +## Symptoms + +- The events report in Netwrix Change Tracker contains one or more `ErrorEvent` events. Their description states `Corrupt`. +- Agent logs located in `C:\ProgramData\NNT\gen7agent.service\rolling-log.txt` contain the following line: + +```text +[timestamp] ERROR AgentTaskRunner - task execution failed for task %#% - %task_name% [timestamp] +``` + +## Cause + +The agent directory on affected devices contains multiple conflicting `Config-*.xml` files. These files cause conflicts in device agent events. + +## Resolution + +> **NOTE:** You can establish the affected agents via the events report—review the **DeviceName** and **AgentID** column values. + +Perform an agent reset to reconfigure affected agents. Refer to the following steps: + +1. Stop the Netwrix Change Tracker Agent Service. Refer to the following Linux command: + +```bash +# service nntgen7agent stop +``` + +2. Navigate to the agent directory containing the Rolling-Log files. Refer to the following default path: + +```text +C:\ProgramData\NNT\gen7agent.service\ +``` + +3. Right-click the `Hubdetails.xml` file and select **Edit**. + +4. Replace the `` tag pair with the `` tag pair. Replace the contents with the current agent account password, as defined on your Netwrix Change Tracker Hub Server. Save the changes. + +5. Start the Agent Service. Refer to the following Linux command: + +```bash +# service nntgen7agent start +``` diff --git a/docs/kb/changetracker/database-and-diagnostics/disk_space_occupied_by_core._files_in_gen_7_agent_servers.md b/docs/kb/changetracker/database-and-diagnostics/disk_space_occupied_by_core._files_in_gen_7_agent_servers.md new file mode 100644 index 0000000000..8ad95745e9 --- /dev/null +++ b/docs/kb/changetracker/database-and-diagnostics/disk_space_occupied_by_core._files_in_gen_7_agent_servers.md @@ -0,0 +1,29 @@ +--- +description: >- + This article explains the purpose of `core.*` files in Gen 7 Agent servers and whether they can be safely deleted to free up disk space. +keywords: + - core files + - Gen 7 Agent + - disk space +sidebar_label: Disk Space and Core Files +tags: + - database-and-diagnostics +title: "Disk Space Occupied by Core.* Files in Gen 7 Agent Servers" +knowledge_article_id: kA0Qk0000000NuHKAU +products: + - change-tracker +--- + +# Disk Space Occupied by Core.* Files in Gen 7 Agent Servers + +## Questions + +The `opt/nnt/gen7agent/bin/` directory in Gen 7 Agent servers contains multiple `core.*` files. + +1. What are these files? +2. Is it safe to delete these files? + +## Answers + +1. The `core.*` files located in the `opt/nnt/gen7agent/bin/` directory are core dumps. These core dumps are generated upon a process crash or a fatal error—they contain a snapshot of the process memory at the time of the crash or error. +2. These core files can be safely deleted to free up disk space. \ No newline at end of file diff --git a/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_error_nnt.hub.serviceclient.hubadapter_-_certificate_thumbprint_does_not_match_trust.md b/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_error_nnt.hub.serviceclient.hubadapter_-_certificate_thumbprint_does_not_match_trust.md new file mode 100644 index 0000000000..d63a5690a2 --- /dev/null +++ b/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_error_nnt.hub.serviceclient.hubadapter_-_certificate_thumbprint_does_not_match_trust.md @@ -0,0 +1,63 @@ +--- +description: >- + This article addresses the error related to the certificate thumbprint mismatch in the Netwrix Agent and provides a resolution to ensure proper reporting to the Hub Server. +keywords: + - Netwrix Agent + - certificate thumbprint + - Hub Server +sidebar_label: Rolling-Log Fix +tags: [troubleshooting-and-errors] +title: 'Rolling-Log Fix: "ERROR NNT.Hub.ServiceClient.HubAdapter - Certificate Thumbprint Does Not Match Trusted"' +knowledge_article_id: kA04u0000000JaGCAU +products: + - change-tracker +--- + +# Rolling-Log Fix: "ERROR NNT.Hub.ServiceClient.HubAdapter - Certificate Thumbprint Does Not Match Trusted" + +## Symptoms + +The following may occur when the Agent password being sent to the Hub Server is incorrect: + +``` +# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # +# Example Message: # +# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # + +2017-10-08 11:17:36,935 [Threadpool worker] ERROR NNT.Hub.ServiceClient.HubAdapter - Certificate thumbprint does not match trusted (BAD1067FBAB59CCED21786657C672F6AB5BE824C/6F7F11707C0C93CD0F7E92D5BC0F1C9345D68A64). Consider setting Thumbprint in HubDetails.xml. Server certificate details +``` + +## Cause + +This means that you are using a custom or unrecognized IIS Certificate. You need to specify to the agent the certificate thumbprint so that it can use the new certificate. + +## Resolution + +If you are receiving this error, the Netwrix Agent is NOT reporting to your hub. This is a critical error, and for monitoring to continue, it must be resolved. To resolve this error: + +1. Stop the **Netwrix Agent Service**. +2. Navigate to your Netwrix Agent Directory, which contains the Rolling-Log Files, defined in this article [Netwrix Software Problem? What Info Should I Provide?](https://kb.netwrix.com/8048). +3. Right-click and edit the **HubDetails.xml** file. +4. Locate the **Thumbprint** entry in the XML file. +5. In between the **Thumbprint** tags, enter your custom certificate thumbprint (the correct thumbprint is shown in the error message). +6. Save the file, replacing the old one. Note that you may need to save this to the desktop and copy and paste it back into the directory, replacing the old file. +7. Restart the Agent service. + +### HubDetails.xml Example + +```xml + + + https://myserver.mydomain.local/api + agent + EncryptedPasswordWillAppearHere + + + + + false + + + BCD1067FBAB59CCED21786657C672F6AB5BE824C + +``` \ No newline at end of file diff --git a/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_hub_connection_failed._403_server_message_ip_address_blocked_loginfailures.md b/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_hub_connection_failed._403_server_message_ip_address_blocked_loginfailures.md new file mode 100644 index 0000000000..7e232d8401 --- /dev/null +++ b/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_hub_connection_failed._403_server_message_ip_address_blocked_loginfailures.md @@ -0,0 +1,58 @@ +--- +description: >- + This article provides a resolution for the "Hub connection failed" error due to an IP address being blocked after multiple login failures. +keywords: + - Hub connection failed + - IP address blocked + - Login failures +sidebar_label: Rolling-Log Fix +tags: [troubleshooting-and-errors] +title: "Rolling-Log Fix: Hub Connection Failed. 403 Server Message: IP Address Blocked: Login Failures" +knowledge_article_id: kA04u0000000JXgCAM +products: + - change-tracker +--- + +# Rolling-Log Fix: Hub Connection Failed. 403 Server Message: IP Address Blocked: Login Failures + +## Symptoms + +This problem can occur when the Agent password being sent to the Hub Server is incorrect. + +### Example Error Message + +``` +2017-09-06 14:22:43,230 [10] INFO Message - Hub connection failed (403 Server message: Ip Address Blocked: LoginFailures) +``` + +## Resolution + +1. Stop the **Netwrix Agent Service**. +2. Navigate to your Agent Directory which contains the Rolling-Log Files. +3. Right-click and edit the **Hubdetails.xml** file. +4. Remove the `` tags as they are the agent password which has been encrypted. +5. In place of ``, enter the `` tags. See an example of **HubDetails.xml** below. The default password is used as an example. +6. In between the password entries, enter your Agent Account password as defined on your Netwrix Hub Server. +7. Save the file, replacing the old one. +8. Restart the Agent service. + +> **NOTE:** When you start the service, the agent will automatically re-encrypt your password, and the **E1** tags will replace the password tags. Also, there is a ten-minute cool-off when this happens. Now that the username and password have been corrected, the agent should register after the ten minutes have elapsed. This cool-off period is counted at the Netwrix Hub Server and does not take effect at the agent level. If you have stopped the service, you do not have to wait 10 minutes after restarting it. + +### HubDetails.xml Example + +```xml + + + https://myserver.mydomain.local/api + agent + + + + + + false + + + + +``` \ No newline at end of file From ec4fb9605d75f9a409e35d984daf10f06c143d22 Mon Sep 17 00:00:00 2001 From: Hilary Ramirez Date: Mon, 5 Jan 2026 14:50:39 -0500 Subject: [PATCH 2/3] Add sidebar configuration and landing page for Change Tracker KB - Enable KB section in Change Tracker 8.0 and 8.1 sidebars - Create index.md landing page with welcome message and help section - Complete certificate article cleanup (remove unnecessary password references) - Update sidebar labels to distinguish between 403 and certificate articles --- docs/kb/changetracker/index.md | 18 ++++++++++++++++++ ...tificate_thumbprint_does_not_match_trust.md | 5 ++--- ...message_ip_address_blocked_loginfailures.md | 2 +- sidebars/changetracker/8.0.js | 8 ++++++++ sidebars/changetracker/8.1.js | 8 ++++++++ 5 files changed, 37 insertions(+), 4 deletions(-) create mode 100644 docs/kb/changetracker/index.md diff --git a/docs/kb/changetracker/index.md b/docs/kb/changetracker/index.md new file mode 100644 index 0000000000..ebd080a722 --- /dev/null +++ b/docs/kb/changetracker/index.md @@ -0,0 +1,18 @@ +--- +title: "Change Tracker Knowledge Base" +description: "Change Tracker knowledge base articles and troubleshooting guides" +slug: changetracker +--- + +# Change Tracker Knowledge Base + +Welcome to the Change Tracker knowledge base. Browse our collection of troubleshooting guides, configuration instructions, and best practices. + +Use the search function above to find specific articles or browse through all Change Tracker KB articles in this section. + +## Need Help? + +If you can't find what you're looking for: +1. Use the search function above +2. Check the main [Change Tracker documentation](https://docs.netwrix.com/docs/changetracker/) +3. Contact [Netwrix support](https://www.netwrix.com/support.html) diff --git a/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_error_nnt.hub.serviceclient.hubadapter_-_certificate_thumbprint_does_not_match_trust.md b/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_error_nnt.hub.serviceclient.hubadapter_-_certificate_thumbprint_does_not_match_trust.md index d63a5690a2..03cfe3cd74 100644 --- a/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_error_nnt.hub.serviceclient.hubadapter_-_certificate_thumbprint_does_not_match_trust.md +++ b/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_error_nnt.hub.serviceclient.hubadapter_-_certificate_thumbprint_does_not_match_trust.md @@ -5,7 +5,7 @@ keywords: - Netwrix Agent - certificate thumbprint - Hub Server -sidebar_label: Rolling-Log Fix +sidebar_label: Certificate Thumbprint Mismatch tags: [troubleshooting-and-errors] title: 'Rolling-Log Fix: "ERROR NNT.Hub.ServiceClient.HubAdapter - Certificate Thumbprint Does Not Match Trusted"' knowledge_article_id: kA04u0000000JaGCAU @@ -17,7 +17,7 @@ products: ## Symptoms -The following may occur when the Agent password being sent to the Hub Server is incorrect: +The following error occurs when using a custom or unrecognized IIS Certificate: ``` # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # @@ -50,7 +50,6 @@ If you are receiving this error, the Netwrix Agent is NOT reporting to your hub. https://myserver.mydomain.local/api agent - EncryptedPasswordWillAppearHere diff --git a/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_hub_connection_failed._403_server_message_ip_address_blocked_loginfailures.md b/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_hub_connection_failed._403_server_message_ip_address_blocked_loginfailures.md index 7e232d8401..9bf8041858 100644 --- a/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_hub_connection_failed._403_server_message_ip_address_blocked_loginfailures.md +++ b/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_hub_connection_failed._403_server_message_ip_address_blocked_loginfailures.md @@ -5,7 +5,7 @@ keywords: - Hub connection failed - IP address blocked - Login failures -sidebar_label: Rolling-Log Fix +sidebar_label: 403 IP Address Blocked tags: [troubleshooting-and-errors] title: "Rolling-Log Fix: Hub Connection Failed. 403 Server Message: IP Address Blocked: Login Failures" knowledge_article_id: kA04u0000000JXgCAM diff --git a/sidebars/changetracker/8.0.js b/sidebars/changetracker/8.0.js index 5ab4af3199..f0e24e2db2 100644 --- a/sidebars/changetracker/8.0.js +++ b/sidebars/changetracker/8.0.js @@ -1,8 +1,16 @@ +const generateKBSidebar = require('../../src/utils/generateKBSidebar'); + module.exports = { sidebar: [ { type: 'autogenerated', dirName: '.', }, + { + type: 'category', + label: 'Knowledge Base', + collapsed: true, + items: generateKBSidebar('changetracker') + }, ], }; \ No newline at end of file diff --git a/sidebars/changetracker/8.1.js b/sidebars/changetracker/8.1.js index 5ab4af3199..f0e24e2db2 100644 --- a/sidebars/changetracker/8.1.js +++ b/sidebars/changetracker/8.1.js @@ -1,8 +1,16 @@ +const generateKBSidebar = require('../../src/utils/generateKBSidebar'); + module.exports = { sidebar: [ { type: 'autogenerated', dirName: '.', }, + { + type: 'category', + label: 'Knowledge Base', + collapsed: true, + items: generateKBSidebar('changetracker') + }, ], }; \ No newline at end of file From bb585c2c88f449d1e426ed90099959ef3cd2d880 Mon Sep 17 00:00:00 2001 From: Hilary Ramirez Date: Mon, 5 Jan 2026 16:13:23 -0500 Subject: [PATCH 3/3] Address Claude Code review feedback for PR #9 - Add missing newline to disk space article - Fix XML formatting: use YourAgentPassword - Correct platform-specific paths for 8.0/8.1: - Windows: C:\ProgramData\NNT\gen7agent.app.netcore - Linux: /var/nnt/gen7agent.app.netcore/ - Linux binaries: /opt/nnt/gen7agentcore/bin/ - Replace broken kb.netwrix.com link with working docs links - Add references to official Change Tracker documentation - Separate Windows/Linux instructions in corrupt-errorevent article --- .../corrupt-errorevent-in-event-reports.md | 36 ++++++++++++------- ...d_by_core._files_in_gen_7_agent_servers.md | 6 ++-- ...ificate_thumbprint_does_not_match_trust.md | 6 ++-- ...essage_ip_address_blocked_loginfailures.md | 2 +- 4 files changed, 32 insertions(+), 18 deletions(-) diff --git a/docs/kb/changetracker/audit-and-logging/corrupt-errorevent-in-event-reports.md b/docs/kb/changetracker/audit-and-logging/corrupt-errorevent-in-event-reports.md index fb5ac3055a..db944d9ada 100644 --- a/docs/kb/changetracker/audit-and-logging/corrupt-errorevent-in-event-reports.md +++ b/docs/kb/changetracker/audit-and-logging/corrupt-errorevent-in-event-reports.md @@ -28,7 +28,9 @@ knowledge_article_id: kA0Qk0000000ahpKAA ## Symptoms - The events report in Netwrix Change Tracker contains one or more `ErrorEvent` events. Their description states `Corrupt`. -- Agent logs located in `C:\ProgramData\NNT\gen7agent.service\rolling-log.txt` contain the following line: +- Agent logs (see [Rolling-Log File Location](https://docs.netwrix.com/docs/changetracker/8_1/install/agent/rollinglogfile)) contain the following line: + - **Windows:** `C:\ProgramData\NNT\gen7agent.app.netcore\rolling-log.txt` + - **Linux:** `/var/nnt/gen7agent.app.netcore/rolling-log.txt` ```text [timestamp] ERROR AgentTaskRunner - task execution failed for task %#% - %task_name% [timestamp] @@ -42,26 +44,36 @@ The agent directory on affected devices contains multiple conflicting `Config-*. > **NOTE:** You can establish the affected agents via the events report—review the **DeviceName** and **AgentID** column values. -Perform an agent reset to reconfigure affected agents. Refer to the following steps: +Perform an agent reset to reconfigure affected agents: -1. Stop the Netwrix Change Tracker Agent Service. Refer to the following Linux command: +### Windows -```bash -# service nntgen7agent stop -``` +1. Stop the Netwrix Change Tracker Agent Service. -2. Navigate to the agent directory containing the Rolling-Log files. Refer to the following default path: +2. Navigate to the agent directory (see [Rolling-Log File Location](https://docs.netwrix.com/docs/changetracker/8_1/install/agent/rollinglogfile)): `C:\ProgramData\NNT\gen7agent.app.netcore\` -```text -C:\ProgramData\NNT\gen7agent.service\ +3. Right-click the `Hubdetails.xml` file and select **Edit**. + +4. Replace the `` tag pair with the `` tag pair. Replace the contents with the current agent account password, as defined on your Netwrix Change Tracker Hub Server. Save the changes. + +5. Start the Agent Service. + +### Linux + +1. Stop the Netwrix Change Tracker Agent Service: + +```bash +service nntgen7agent stop ``` -3. Right-click the `Hubdetails.xml` file and select **Edit**. +2. Navigate to the agent directory (see [Rolling-Log File Location](https://docs.netwrix.com/docs/changetracker/8_1/install/agent/rollinglogfile)): `/var/nnt/gen7agent.app.netcore/` + +3. Edit the `Hubdetails.xml` file. 4. Replace the `` tag pair with the `` tag pair. Replace the contents with the current agent account password, as defined on your Netwrix Change Tracker Hub Server. Save the changes. -5. Start the Agent Service. Refer to the following Linux command: +5. Start the Agent Service: ```bash -# service nntgen7agent start +service nntgen7agent start ``` diff --git a/docs/kb/changetracker/database-and-diagnostics/disk_space_occupied_by_core._files_in_gen_7_agent_servers.md b/docs/kb/changetracker/database-and-diagnostics/disk_space_occupied_by_core._files_in_gen_7_agent_servers.md index 8ad95745e9..9e989a2731 100644 --- a/docs/kb/changetracker/database-and-diagnostics/disk_space_occupied_by_core._files_in_gen_7_agent_servers.md +++ b/docs/kb/changetracker/database-and-diagnostics/disk_space_occupied_by_core._files_in_gen_7_agent_servers.md @@ -18,12 +18,12 @@ products: ## Questions -The `opt/nnt/gen7agent/bin/` directory in Gen 7 Agent servers contains multiple `core.*` files. +The `/opt/nnt/gen7agentcore/bin/` directory (see [Linux Agent Installation](https://docs.netwrix.com/docs/changetracker/8_1/install/agent/linuxos)) in Gen 7 Agent servers (Linux) contains multiple `core.*` files. 1. What are these files? 2. Is it safe to delete these files? ## Answers -1. The `core.*` files located in the `opt/nnt/gen7agent/bin/` directory are core dumps. These core dumps are generated upon a process crash or a fatal error—they contain a snapshot of the process memory at the time of the crash or error. -2. These core files can be safely deleted to free up disk space. \ No newline at end of file +1. The `core.*` files located in the `/opt/nnt/gen7agentcore/bin/` directory are core dumps. These core dumps are generated upon a process crash or a fatal error—they contain a snapshot of the process memory at the time of the crash or error. +2. These core files can be safely deleted to free up disk space. diff --git a/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_error_nnt.hub.serviceclient.hubadapter_-_certificate_thumbprint_does_not_match_trust.md b/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_error_nnt.hub.serviceclient.hubadapter_-_certificate_thumbprint_does_not_match_trust.md index 03cfe3cd74..4d94ddb2dc 100644 --- a/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_error_nnt.hub.serviceclient.hubadapter_-_certificate_thumbprint_does_not_match_trust.md +++ b/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_error_nnt.hub.serviceclient.hubadapter_-_certificate_thumbprint_does_not_match_trust.md @@ -36,8 +36,10 @@ This means that you are using a custom or unrecognized IIS Certificate. You need If you are receiving this error, the Netwrix Agent is NOT reporting to your hub. This is a critical error, and for monitoring to continue, it must be resolved. To resolve this error: 1. Stop the **Netwrix Agent Service**. -2. Navigate to your Netwrix Agent Directory, which contains the Rolling-Log Files, defined in this article [Netwrix Software Problem? What Info Should I Provide?](https://kb.netwrix.com/8048). -3. Right-click and edit the **HubDetails.xml** file. +2. Navigate to your Netwrix Agent Directory, which contains the Rolling-Log Files (see [Agent Rolling-Log File Location](https://docs.netwrix.com/docs/changetracker/8_1/install/agent/rollinglogfile) for more details): + - **Windows:** `C:\ProgramData\NNT\gen7agent.app.netcore\` + - **Linux:** `/var/nnt/gen7agent.app.netcore/` +3. Edit the **HubDetails.xml** file. 4. Locate the **Thumbprint** entry in the XML file. 5. In between the **Thumbprint** tags, enter your custom certificate thumbprint (the correct thumbprint is shown in the error message). 6. Save the file, replacing the old one. Note that you may need to save this to the desktop and copy and paste it back into the directory, replacing the old file. diff --git a/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_hub_connection_failed._403_server_message_ip_address_blocked_loginfailures.md b/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_hub_connection_failed._403_server_message_ip_address_blocked_loginfailures.md index 9bf8041858..b409d2fa41 100644 --- a/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_hub_connection_failed._403_server_message_ip_address_blocked_loginfailures.md +++ b/docs/kb/changetracker/troubleshooting-and-errors/rolling-log_fix_hub_connection_failed._403_server_message_ip_address_blocked_loginfailures.md @@ -45,7 +45,7 @@ This problem can occur when the Agent password being sent to the Hub Server is i https://myserver.mydomain.local/api agent - + YourAgentPassword