Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Elastic-Agent] Could not reach Kibana Fleet API over cloud #17841

Closed
ph opened this issue Apr 20, 2020 · 3 comments · Fixed by #17843
Closed

[Elastic-Agent] Could not reach Kibana Fleet API over cloud #17841

ph opened this issue Apr 20, 2020 · 3 comments · Fixed by #17843
Assignees
@ph
Labels
blocker Ingest Management:alpha1 Group issues for ingest management alpha1

Comments

@ph
Copy link
Contributor

ph commented Apr 20, 2020 

2020-04-20T13:23:37-04:00 INFO	application.go:48	Detecting execution mode
2020-04-20T13:23:37-04:00 INFO	application.go:68	Agent is managed by Fleet
2020-04-20T13:23:37-04:00 INFO	managed_mode.go:190	Agent is starting
2020-04-20T13:23:38-04:00 DEBUG	fleet_gateway.go:126	FleetGateway calling Checkin API
2020-04-20T13:23:38-04:00 DEBUG	client.go:170	Request method: POST, path: /api/ingest_manager/fleet/agents/a584fd10-832b-11ea-9f16-b96d6775ae6d/checkin
2020-04-20T13:23:38-04:00 ERROR	fleet_gateway.go:162	Could not communicate with Checking API will retry, error: could not decode the response, raw response: Client sent an HTTP request to an HTTPS server.

	could not decode the response, raw response: Client sent an HTTP request to an HTTPS server.

2020-04-20T13:23:39-04:00 DEBUG	client.go:170	Request method: POST, path: /api/ingest_manager/fleet/agents/a584fd10-832b-11ea-9f16-b96d6775ae6d/checkin
2020-04-20T13:23:39-04:00 ERROR	fleet_gateway.go:162	Could not communicate with Checking API will retry, error: could not decode the response, raw response: Client sent an HTTP request to an HTTPS server.

	could not decode the response, raw response: Client sent an HTTP request to an HTTPS server.
@ph ph added blocker Team:Ingest Management Ingest Management:alpha1 Group issues for ingest management alpha1 labels Apr 20, 2020
@ph ph self-assigned this Apr 20, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ingest-management (Team:Ingest Management)

@ph
Copy link
Contributor Author

ph commented Apr 20, 2020

cc @ruflin I believe you ran into the same issue, I have a good idea of what the problem is, I believe we are not correctly generating the configuration to connect to kibana.

@ph
Copy link
Contributor Author

ph commented Apr 20, 2020

🤦

ph added a commit to ph/beats that referenced this issue Apr 20, 2020
@ph
Correctly unmarshal Protocol
834beb1 
The Protocol (https/http) was not correctly unmarshaly and assigned to
the value of the struct. Because of this the checking was trying to use
a plain text connection or a TLS enabled endpoint.

Fixes: elastic#17841
@ph ph mentioned this issue Apr 20, 2020
Merged
6 tasks
ruflin pushed a commit that referenced this issue Apr 21, 2020
@ph
Correctly unmarshal Protocol (#17843)
0765f94 
The Protocol (https/http) was not correctly unmarshaly and assigned to
the value of the struct. Because of this the checking was trying to use
a plain text connection or a TLS enabled endpoint.

Fixes: #17841
ph added a commit to ph/beats that referenced this issue Apr 21, 2020
@ph
Correctly unmarshal Protocol (elastic#17843)
a1a015d 
The Protocol (https/http) was not correctly unmarshaly and assigned to
the value of the struct. Because of this the checking was trying to use
a plain text connection or a TLS enabled endpoint.

Fixes: elastic#17841
(cherry picked from commit 0765f94)
@ph ph mentioned this issue Apr 21, 2020
Merged
6 tasks
ph added a commit that referenced this issue Apr 21, 2020
@ph
Correctly unmarshal Protocol (#17843) (#17866)
9a21b66 
The Protocol (https/http) was not correctly unmarshaly and assigned to
the value of the struct. Because of this the checking was trying to use
a plain text connection or a TLS enabled endpoint.

Fixes: #17841
(cherry picked from commit 0765f94)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ph ph

Labels
blocker Ingest Management:alpha1 Group issues for ingest management alpha1
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Elastic-Agent] Correctly unmarshal Protocol ph/beats
2 participants
@ph @elasticmachine