Need Help! - Agent Client Collector Framework - [Error] [agent] [handshake failed with status 401]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā11-06-2024 12:41 AM
I am getting the following error [Error] [agent] [handshake failed with status 401] - Authentication failed - API key is invalid in the acc.log file.
Notes to consider:
- This is on-premises environment.
- Instance and MID Server and Agent installed in the test machine is on Offline Network [No internet Access].
- MID Server is reachable from test machine.
- Agent is also being installed in the MID Server and same error appears.
Steps followed:
- MID Server is up and running.
- Checked API key - is valid and not expired.
- Web MID Server - state [started].
- Entered the end-point url in the browser https://<end point url> and it shows the same 401 Error.
- Tried curl command and it returns the same 401 error.
- Tested the port and Port is open.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā11-06-2024 11:38 PM
Hi @MurwanA This seems to be an issue with the authentication and u mentioned even the curl command is returning 401..
did u verify the API key in the log file? and is the test machine in DMZ zone?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā11-06-2024 11:44 PM
Yes, I have verified the API Key as I am getting API Key Authentication Failed - So I entered the API key manually in the config file of the agent. and still same error appears.
And both MID Server and Test machines can see each other.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā11-07-2024 12:12 AM
and regd CURL command, did u test the same mentioned in the docs link here:
Configure the websocket server on the MID Server
If this fails then it means its failing at network/OS level where the handshake is not happening.