Fleet-server: http: server gave HTTP response to HTTPS client

Elastic Stack Kibana
21

From the error message posted yesterday, it seems like enrollment didn't go well, and that needs to be addressed first.

If the Agent is running on your machine and is connected to Fleet with a policy that has Endpoint Security integration, let's check if the Agent has bootstrapped elastic-endpoint.exe, and is ready to accept connection.

  • Please make sure Endpoint is extracted under the path Dan posted in step 3.
  • Check if elastic-agent.exe is listening on port 6788.
22

Yes they are from the windows Endpoint.
I am using elastic-agent-7.17.1-windows-x86_64.zip I can install the new version and try again.
I am not seeing the http.cpp error message in the logs.
I did remove the agent from elastic, do I need to reinstall the agent again to generate the error if so I can do that.

23

Only port 17480:

image
image1891×171 14.2 KB

24

Any other advice for this issue?

25

@secopsgeek , that doesn't seem like a port number that Agent would be listening on. Can you double check using a terminal command like netstat ? You will need to filter out the output by the PID agent.

26

Sorry, I am late responding butt I have this fixed now. I am running Elastic 8.1.2. The 7.17 version gave me problems ever since I upgraded from 7.16, so now I have all my Endpoints working.

I troubleshooted this problem Saturday morning and now I have everything working.

27

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.