# Central Management filebeat enrollment fail **URL:** \ **Category:** Beats\ **Created:** [December 11, 2018, 4:39pm UTC](https://discuss.elastic.co/t/central-management-filebeat-enrollment-fail/160412 "2018-12-11T16:39:45Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![GregoryB-T](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gregoryb-t/32/28564_2.png) [@GregoryB-T](https://discuss.elastic.co/u/GregoryB-T)\ **Post date:** [December 11, 2018, 4:39pm UTC](https://discuss.elastic.co/t/central-management-filebeat-enrollment-fail/160412/1 "2018-12-11T16:39:46Z")
Hi I'm trying to enroll filebeat to the Central Management but since I use a custom cert I have this error Error while enrolling: fail to execute the HTTP POST request: Post https://+++++++++/api/beats/agent/++++-++++++-+++++-+++++-++++++: x509: certificate signed by unknown authority there is a way of configure SSL cert and CA ? Thanks and regards ---
**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\ **Post date:** [December 11, 2018, 7:56pm UTC](https://discuss.elastic.co/t/central-management-filebeat-enrollment-fail/160412/2 "2018-12-11T19:56:23Z")
Hi Gregory, Unfortunately this is not supported yet. If you have a GitHub account, I suggest you subscribe to this issue: [https://github.com/elastic/beats/issues/9129](https://github.com/elastic/beats/issues/9129). That way you'll be notified of its progress. Shaunak ---
**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\ **Post date:** [December 11, 2018, 8:00pm UTC](https://discuss.elastic.co/t/central-management-filebeat-enrollment-fail/160412/3 "2018-12-11T20:00:10Z")
As mentioned in one of the issue's comments, the workaround for now is to "add the CA to the OS trust store and the enroll subcommand will pick it up." ---
**Author:** ![GregoryB-T](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gregoryb-t/32/28564_2.png) [@GregoryB-T](https://discuss.elastic.co/u/GregoryB-T)\ **Post date:** [December 12, 2018, 6:47pm UTC](https://discuss.elastic.co/t/central-management-filebeat-enrollment-fail/160412/4 "2018-12-12T18:47:39Z")
Hi @shaunak thanks for the workaround it works fine and the features are really nice Thanks and Regards ---
**Author:** ![Ryan\_Downey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ryan_downey/32/35987_2.png) [@Ryan\_Downey](https://discuss.elastic.co/u/Ryan_Downey)\ **Post date:** [January 4, 2019, 1:50pm UTC](https://discuss.elastic.co/t/central-management-filebeat-enrollment-fail/160412/5 "2019-01-04T13:50:41Z")
\*\*\*Update: I went through the steps here and it still didn't seem to work: [http://www.sqlservermart.com/HowTo/Windows\_Import\_Certificate.aspx](http://www.sqlservermart.com/HowTo/Windows_Import_Certificate.aspx) I'm running into the same issue. By "add the CA to the OS trust store" I assume that if I'm working on a Windows Server 2016 that it needs to be added somewhere in the MS truststore. Any info on how to do that? I've been reading documentation online but its not getting me anywhere. Any help would be appreciated. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 1, 2019, 3:50pm UTC](https://discuss.elastic.co/t/central-management-filebeat-enrollment-fail/160412/6 "2019-02-01T15:50:44Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.