# Fleet-server: http: server gave HTTP response to HTTPS client **URL:** \ **Category:** Kibana\ **Tags:** elastic-stack-security\ **Created:** [March 31, 2022, 1:45pm UTC](https://discuss.elastic.co/t/fleet-server-http-server-gave-http-response-to-https-client/301203 "2022-03-31T13:45:00Z")\ **Posts on this page:** 7\ **Page:** 2
**Author:** ![ckim](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ckim/32/78869_2.png) [@ckim](https://discuss.elastic.co/u/ckim)\ **Post date:** [April 1, 2022, 3:13pm UTC](https://discuss.elastic.co/t/fleet-server-http-server-gave-http-response-to-https-client/301203/21 "2022-04-01T15:13:01Z")
> [@secopsgeek](#): > > ```auto > + ./elastic-agent install -f --url=https://172.16.100.6:8220 --enrollme ... > + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > + CategoryInfo : NotSpecified: (2022-03-31T12:2....16.100.6:8220/:String) [], RemoteException > + FullyQualifiedErrorId : NativeCommandError > > Error: fail to enroll: fail to execute request to fleet-server: x509: certificate signed by unknown authority > For help, please see our troubleshooting guide at https://www.elastic.co/guide/en/fleet/7.17/fleet-troubleshooting.html > Error: enroll command failed with exit code: 1 > > ``` 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. ---
**Author:** ![secopsgeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/secopsgeek/32/83957_2.png) [@secopsgeek](https://discuss.elastic.co/u/secopsgeek)\ **Post date:** [April 1, 2022, 3:28pm UTC](https://discuss.elastic.co/t/fleet-server-http-server-gave-http-response-to-https-client/301203/22 "2022-04-01T15:28:01Z")
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. ---
**Author:** ![secopsgeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/secopsgeek/32/83957_2.png) [@secopsgeek](https://discuss.elastic.co/u/secopsgeek)\ **Post date:** [April 1, 2022, 3:57pm UTC](https://discuss.elastic.co/t/fleet-server-http-server-gave-http-response-to-https-client/301203/23 "2022-04-01T15:57:43Z")
Only port 17480: ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/e/ceb22b70b96b66254438e4291729c44eec3f967a.png) ---
**Author:** ![secopsgeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/secopsgeek/32/83957_2.png) [@secopsgeek](https://discuss.elastic.co/u/secopsgeek)\ **Post date:** [April 8, 2022, 8:23pm UTC](https://discuss.elastic.co/t/fleet-server-http-server-gave-http-response-to-https-client/301203/24 "2022-04-08T20:23:01Z")
Any other advice for this issue? ---
**Author:** ![ckim](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ckim/32/78869_2.png) [@ckim](https://discuss.elastic.co/u/ckim)\ **Post date:** [April 11, 2022, 3:57pm UTC](https://discuss.elastic.co/t/fleet-server-http-server-gave-http-response-to-https-client/301203/25 "2022-04-11T15:57:23Z")
@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. ---
**Author:** ![secopsgeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/secopsgeek/32/83957_2.png) [@secopsgeek](https://discuss.elastic.co/u/secopsgeek)\ **Post date:** [April 11, 2022, 4:44pm UTC](https://discuss.elastic.co/t/fleet-server-http-server-gave-http-response-to-https-client/301203/26 "2022-04-11T16:44:48Z")
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. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 9, 2022, 4:45pm UTC](https://discuss.elastic.co/t/fleet-server-http-server-gave-http-response-to-https-client/301203/27 "2022-05-09T16:45:47Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed. [Previous page](https://discuss.elastic.co/t/fleet-server-http-server-gave-http-response-to-https-client/301203.md?page=1)