Clear ELK installation cant add Fleet server 8.12

Elastic Stack Elastic Agent
1

Hi there, I am install Elasticsearch and Kibana. All services using self-signed certificates generated with elasticsearch-certutil. :grinning:

In the Kibana Fleet GUI interface, I added a Fleet server and selected Advanced. I created a policy, chose production deployment mode, added the Fleet server with port 8220 and https protocol url. I created a token and issued the command:

sudo ./elastic-agent install --url=bttps://fleet.myserver.com:8220
--fleet-server-es=bttps://elk-01.myserver.com:9200/)
--fleet-server-service-token=token-here
--fleet-server-policy=fleet-server-policy
--certificate-authorities=/etc/elasticsearch/certs/ca/ca.crt \ --fleet-server-es-ca=/etc/elasticsearch/certs/ca/ca.crt
--fleet-server-cert=/home/adminimum/fleet/fleet.crt
--fleet-server-cert-key=/home/adminimum/fleet/fleet.key
--fleet-server-port=8220

After waiting for the message, recieved error "[====] Waiting For Enroll... [2m12s] Error: fleet-server failed: context canceled",

I also tried the command:

sudo ./elastic-agent install
--fleet-server-es=bttps://elk-01.myserver.com:9200
--fleet-server-service-token=token-here
--fleet-server-es-ca=/etc/elasticsearch/certs/ca/ca.crt
--fleet-server-policy=fleet-server-policy
--fleet-server-port=8220

The same problem occurred again. I also tried using --fleet-server-es-insecure.

ELK is accessible via curl -k -u {username}:{password} https://{ELASTICSEARCH_HOST}:9200

bttps://kibana.myserver.com:5601/api/fleet/package_policies/ad39463f-5cc0-4868-aba5-cb106318bb19
The result is here: pastebin .com/LvqK8NY3

Screenshot of settings attached.

snap3
snap31341×726 58.2 KB

I checked app/fleet/_debug I do not have preconfigured policies.

ELK Stack version 8.12.2

please help, why clear installation not working

2

This is no longer available.

To be clear, you are having issues deploying an agent that runs the fleet-server, correct?

Do you have any proxies deployed? Can you confirm that the instance you are attempting to install fleet-server on can reach the Elasticsearch URL?

Also, are the typos in the 1st command you added intended? for instance

--fleet-server-es=bttps://elk-01.myserver.com:9200/)

There is an extra parenthesis at the end, and the schema is incorrect

3

I used the https scheme. I wrote bttps in the message because the forum blocks links.

Do you still need the result of executing:

/api/fleet/package_policies/ad39463f-5cc0-4868-aba5-cb106318bb19

And yes, it's my first setup and fleet server running on agent

I able to get results from elasticsearch server where fleet server hosting, but I must specify CA certificate location.

No proxies used

4

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