# Sidecar cannot get the configuration for filebeat **URL:** \ **Category:** Graylog Central (peer support)\ **Tags:** sidecar, filebeat-linux, nosendlogfblx, failoadcongfigfblx, clfblx\ **Created:** [February 13, 2018, 9:27am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139 "2018-02-13T09:27:33Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![cdeng](https://avatars.discourse-cdn.com/v4/letter/c/e79b87/32.png) [@cdeng](https://community.graylog.org/u/cdeng)\ **Post date:** [February 13, 2018, 9:27am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/1 "2018-02-13T09:27:33Z")
Hello, I have failed to make filebeat work with SSL/TLS with a private self-signed CA in a graylog-2.4.3-1 . in my configuration, the key and certs are put under /etc/graylog/server for graylog server as: ```auto [root@gl1 ~]# ls -l /etc/graylog/server/*.pem -rw-rw----. 1 root graylog 2143 2月 8 12:18 /etc/graylog/server/ca-cert.pem -rw-rw----. 1 root graylog 2029 2月 10 04:05 /etc/graylog/server/rest-cert.pem -rw-rw----. 1 root graylog 3272 2月 10 04:04 /etc/graylog/server/rest-key.pem -rw-rw----. 1 root graylog 2029 2月 10 04:05 /etc/graylog/server/web-cert.pem -rw-rw----. 1 root graylog 3272 2月 10 04:05 /etc/graylog/server/web-key.pem ``` in the collector host i put the key and certs for filebeat under /etc/graylog/collect-sidecar/ and the ca certificate has been already added to the system trust ca list by update-ca-trust command: ```auto ls -l /etc/pki/ca-trust/source/anchors/ca-cert.pem -rw-r--r--. 1 root root 2143 2月 13 15:37 /etc/pki/ca-trust/source/anchors/ca-cert.pem ``` ```auto ls -l /etc/graylog/collector-sidecar/*.pem -rw-r--r--. 1 root root 2143 2月 13 15:46 /etc/graylog/collector-sidecar/ca-cert.pem -rw-r--r--. 1 root root 2049 2月 13 15:46 /etc/graylog/collector-sidecar/clr-node-cert.pem -rw-r--r--. 1 root root 3272 2月 13 15:46 /etc/graylog/collector-sidecar/clr-node-key.pem ``` and the output of sidecar: ```auto graylog-collector-sidecar -debug -c /etc/graylog/collector-sidecar/collector_sidecar.yml INFO[0000] Using collector-id: 8fb06d83-1cd9-4373-a12e-e1bad4a3f246 INFO[0000] Fetching configurations tagged by: [linux ntp chronyd] DEBU[0000] Creating rotated log writer for: /var/log/graylog/collector-sidecar/collector_sidecar.log.%Y%m%d%H%M DEBU[0000] Add collector backend: filebeat INFO[0000] Starting signal distributor DEBU[0000] [signal-processor] (seq=1) handling cmd: restart INFO[0000] [filebeat] Starting (exec driver) DEBU[0000] Creating rotated log writer for: /var/log/graylog/collector-sidecar/filebeat_stderr.log.%Y%m%d%H%M DEBU[0000] Creating rotated log writer for: /var/log/graylog/collector-sidecar/filebeat_stderr.log.%Y%m%d%H%M DEBU[0000] [signal-processor] (seq=1) cmd done: restart ERRO[0001] [filebeat] Backend finished unexpectedly, trying to restart 1/3. DEBU[0001] [signal-processor] (seq=2) handling cmd: restart INFO[0001] [filebeat] Stopping DEBU[0003] [filebeat] SIGHUP ignored, killing process DEBU[0003] [filebeat] Failed to kill process os: process already finished INFO[0003] [filebeat] Starting (exec driver) DEBU[0003] Creating rotated log writer for: /var/log/graylog/collector-sidecar/filebeat_stderr.log.%Y%m%d%H%M DEBU[0003] Creating rotated log writer for: /var/log/graylog/collector-sidecar/filebeat_stderr.log.%Y%m%d%H%M DEBU[0003] [signal-processor] (seq=2) cmd done: restart ERRO[0004] [filebeat] Backend finished unexpectedly, trying to restart 2/3. DEBU[0004] [signal-processor] (seq=3) handling cmd: restart INFO[0004] [filebeat] Stopping DEBU[0006] [filebeat] SIGHUP ignored, killing process DEBU[0006] [filebeat] Failed to kill process os: process already finished INFO[0006] [filebeat] Starting (exec driver) DEBU[0006] Creating rotated log writer for: /var/log/graylog/collector-sidecar/filebeat_stderr.log.%Y%m%d%H%M DEBU[0006] Creating rotated log writer for: /var/log/graylog/collector-sidecar/filebeat_stderr.log.%Y%m%d%H%M DEBU[0006] [signal-processor] (seq=3) cmd done: restart ERRO[0007] [filebeat] Backend finished unexpectedly, trying to restart 3/3. DEBU[0007] [signal-processor] (seq=4) handling cmd: restart INFO[0007] [filebeat] Stopping DEBU[0009] [filebeat] SIGHUP ignored, killing process DEBU[0009] [filebeat] Failed to kill process os: process already finished INFO[0009] [filebeat] Starting (exec driver) DEBU[0009] Creating rotated log writer for: /var/log/graylog/collector-sidecar/filebeat_stderr.log.%Y%m%d%H%M DEBU[0009] Creating rotated log writer for: /var/log/graylog/collector-sidecar/filebeat_stderr.log.%Y%m%d%H%M DEBU[0009] [signal-processor] (seq=4) cmd done: restart ERRO[0010] [filebeat] Unable to start collector after 3 tries, giving up! INFO[0010] [RequestConfiguration] No configuration found for configured tags! INFO[0020] [RequestConfiguration] No configuration found for configured tags! ``` and the status report failed for the collector on the graylog server, but log files have been listed there. | 2018-02-13 15:32:32 | 72 | /var/log/chrony | | --- | --- | --- | | 2018-02-13 17:20:23 | 15070 | /var/log/chrony/measurements.log | | 2018-02-13 17:20:23 | 11934 | /var/log/chrony/statistics.log | | 2018-02-13 17:20:23 | 10496 | /var/log/chrony/tracking.log | is there anything i missed ? thanks. –charles ---
**Author:** ![cdeng](https://avatars.discourse-cdn.com/v4/letter/c/e79b87/32.png) [@cdeng](https://community.graylog.org/u/cdeng)\ **Post date:** [February 13, 2018, 9:38am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/2 "2018-02-13T09:38:48Z")
the sidecar configuration: ```nohighlight cat /etc/graylog/collector-sidecar/collector_sidecar.yml server_url: https://gl1.mylogs.com:9000/api/ update_interval: 10 tls_skip_verify: true send_status: true list_log_files: /var/log/chrony node_id: clr.mylogs.com collector_id: file:/etc/graylog/collector-sidecar/collector-id cache_path: /var/cache/graylog/collector-sidecar log_path: /var/log/graylog/collector-sidecar log_rotation_time: 86400 log_max_age: 604800 tags: - linux - ntp - chronyd backends: - name: nxlog enabled: false binary_path: /usr/bin/nxlog configuration_path: /etc/graylog/collector-sidecar/generated/nxlog.conf - name: filebeat enabled: true binary_path: /usr/bin/filebeat configuration_path: /etc/graylog/collector-sidecar/generated/filebeat.yml ``` ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [February 13, 2018, 9:45am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/3 "2018-02-13T09:45:42Z")
what did your filebeat logfile in `/var/log/graylog/collector-sidecar` gives you back? What is the configuration in `/etc/graylog/collector-sidecar/generated/filebeat.yml` ? ---
**Author:** ![cdeng](https://avatars.discourse-cdn.com/v4/letter/c/e79b87/32.png) [@cdeng](https://community.graylog.org/u/cdeng)\ **Post date:** [February 13, 2018, 9:50am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/4 "2018-02-13T09:50:52Z")
sidecar doesn’t create the filebeat.yml file. and the log: ```auto cat collector_sidecar.log time="2018-02-13T15:51:22+08:00" level=info msg="Starting signal distributor" time="2018-02-13T15:51:22+08:00" level=info msg="[filebeat] Starting (exec driver)" time="2018-02-13T15:51:23+08:00" level=error msg="[filebeat] Backend finished unexpectedly, trying to restart 1/3." time="2018-02-13T15:51:23+08:00" level=info msg="[filebeat] Stopping" time="2018-02-13T15:51:25+08:00" level=info msg="[filebeat] Starting (exec driver)" time="2018-02-13T15:51:26+08:00" level=error msg="[filebeat] Backend finished unexpectedly, trying to restart 2/3." time="2018-02-13T15:51:26+08:00" level=info msg="[filebeat] Stopping" time="2018-02-13T15:51:28+08:00" level=info msg="[filebeat] Starting (exec driver)" time="2018-02-13T15:51:29+08:00" level=error msg="[filebeat] Backend finished unexpectedly, trying to restart 3/3." time="2018-02-13T15:51:29+08:00" level=info msg="[filebeat] Stopping" time="2018-02-13T15:51:31+08:00" level=info msg="[filebeat] Starting (exec driver)" time="2018-02-13T15:51:32+08:00" level=error msg="[filebeat] Unable to start collector after 3 tries, giving up!" time="2018-02-13T15:51:32+08:00" level=error msg="[RequestConfiguration] Fetching configuration failed: Get http://gl1.mylogs.com:9000/api/plugins/org.graylog.plugins.collector/8fb06d83-1cd9-4373-a12e-e1bad4a3f246?tags=%5B%22linux%22%2C%22ntp%22%2C%22chronyd%22%5D: EOF" time="2018-02-13T15:51:32+08:00" level=error msg="[UpdateRegistration] ``` ---
**Author:** ![cdeng](https://avatars.discourse-cdn.com/v4/letter/c/e79b87/32.png) [@cdeng](https://community.graylog.org/u/cdeng)\ **Post date:** [February 13, 2018, 9:55am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/5 "2018-02-13T09:55:14Z")
sorry, the previous are old one, the new logs: ```auto time="2018-02-13T16:56:38+08:00" level=info msg="Stopping signal distributor" time="2018-02-13T16:57:05+08:00" level=debug msg="Add collector backend: filebeat" time="2018-02-13T16:57:05+08:00" level=info msg="Starting signal distributor" time="2018-02-13T16:57:05+08:00" level=debug msg="[signal-processor] (seq=1) handling cmd: restart" time="2018-02-13T16:57:05+08:00" level=info msg="[filebeat] Starting (exec driver)" time="2018-02-13T16:57:05+08:00" level=debug msg="Creating rotated log writer for: /var/log/graylog/collector-sidecar/filebeat_stderr.log.%Y%m%d%H%M" time="2018-02-13T16:57:05+08:00" level=debug msg="Creating rotated log writer for: /var/log/graylog/collector-sidecar/filebeat_stderr.log.%Y%m%d%H%M" time="2018-02-13T16:57:05+08:00" level=debug msg="[signal-processor] (seq=1) cmd done: restart" time="2018-02-13T16:57:06+08:00" level=error msg="[filebeat] Backend finished unexpectedly, trying to restart 1/3." time="2018-02-13T16:57:06+08:00" level=debug msg="[signal-processor] (seq=2) handling cmd: restart" time="2018-02-13T16:57:06+08:00" level=info msg="[filebeat] Stopping" time="2018-02-13T16:57:08+08:00" level=debug msg="[filebeat] SIGHUP ignored, killing process" time="2018-02-13T16:57:08+08:00" level=debug msg="[filebeat] Failed to kill process os: process already finished" time="2018-02-13T16:57:08+08:00" level=info msg="[filebeat] Starting (exec driver)" time="2018-02-13T16:57:08+08:00" level=debug msg="Creating rotated log writer for: /var/log/graylog/collector-sidecar/filebeat_stderr.log.%Y%m%d%H%M" time="2018-02-13T16:57:08+08:00" level=debug msg="Creating rotated log writer for: /var/log/graylog/collector-sidecar/filebeat_stderr.log.%Y%m%d%H%M" time="2018-02-13T16:57:08+08:00" level=debug msg="[signal-processor] (seq=2) cmd done: restart" time="2018-02-13T16:57:09+08:00" level=error msg="[filebeat] Backend finished unexpectedly, trying to restart 2/3." time="2018-02-13T16:57:09+08:00" level=debug msg="[signal-processor] (seq=3) handling cmd: restart" time="2018-02-13T16:57:09+08:00" level=info msg="[filebeat] Stopping" time="2018-02-13T16:57:11+08:00" level=debug msg="[filebeat] SIGHUP ignored, killing process" time="2018-02-13T16:57:11+08:00" level=debug msg="[filebeat] Failed to kill process os: process already finished" time="2018-02-13T16:57:11+08:00" level=info msg="[filebeat] Starting (exec driver)" time="2018-02-13T16:57:11+08:00" level=debug msg="Creating rotated log writer for: /var/log/graylog/collector-sidecar/filebeat_stderr.log.%Y%m%d%H%M" time="2018-02-13T16:57:11+08:00" level=debug msg="Creating rotated log writer for: /var/log/graylog/collector-sidecar/filebeat_stderr.log.%Y%m%d%H%M" time="2018-02-13T16:57:11+08:00" level=debug msg="[signal-processor] (seq=3) cmd done: restart" time="2018-02-13T16:57:12+08:00" level=error msg="[filebeat] Backend finished unexpectedly, trying to restart 3/3." time="2018-02-13T16:57:12+08:00" level=debug msg="[signal-processor] (seq=4) handling cmd: restart" time="2018-02-13T16:57:12+08:00" level=info msg="[filebeat] Stopping" time="2018-02-13T16:57:14+08:00" level=debug msg="[filebeat] SIGHUP ignored, killing process" time="2018-02-13T16:57:14+08:00" level=debug msg="[filebeat] Failed to kill process os: process already finished" time="2018-02-13T16:57:14+08:00" level=info msg="[filebeat] Starting (exec driver)" time="2018-02-13T16:57:14+08:00" level=debug msg="Creating rotated log writer for: /var/log/graylog/collector-sidecar/filebeat_stderr.log.%Y%m%d%H%M" time="2018-02-13T16:57:14+08:00" level=debug msg="Creating rotated log writer for: /var/log/graylog/collector-sidecar/filebeat_stderr.log.%Y%m%d%H%M" time="2018-02-13T16:57:14+08:00" level=debug msg="[signal-processor] (seq=4) cmd done: restart" time="2018-02-13T16:57:15+08:00" level=error msg="[filebeat] Unable to start collector after 3 tries, giving up!" time="2018-02-13T16:57:15+08:00" level=info msg="[RequestConfiguration] No configuration found for configured tags!" time="2018-02-13T16:57:25+08:00" level=info msg="[RequestConfiguration] No configuration found for configured tags!" ``` ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [February 13, 2018, 10:11am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/6 "2018-02-13T10:11:19Z")
please answer my question > [@Sidecar cannot get the configuration for filebeat](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/3): > > what did your filebeat logfile in /var/log/graylog/collector-sidecar gives you back? What is the configuration in /etc/graylog/collector-sidecar/generated/filebeat.yml ? ---
**Author:** ![cdeng](https://avatars.discourse-cdn.com/v4/letter/c/e79b87/32.png) [@cdeng](https://community.graylog.org/u/cdeng)\ **Post date:** [February 13, 2018, 10:12am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/7 "2018-02-13T10:12:44Z")
no, there is no filebeat.yml generated. this is the problem. ---
**Author:** ![cdeng](https://avatars.discourse-cdn.com/v4/letter/c/e79b87/32.png) [@cdeng](https://community.graylog.org/u/cdeng)\ **Post date:** [February 13, 2018, 10:14am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/8 "2018-02-13T10:14:30Z")
```auto cat filebeat_stderr.log filebeat2018/02/13 10:13:46.077438 beat.go:339: CRIT Exiting: error loading config file: stat /etc/graylog/collector-sidecar/generated/filebeat.yml: no such file or directory Exiting: error loading config file: stat /etc/graylog/collector-sidecar/generated/filebeat.yml: no such file or directory filebeat2018/02/13 10:13:49.080472 beat.go:339: CRIT Exiting: error loading config file: stat /etc/graylog/collector-sidecar/generated/filebeat.yml: no such file or directory Exiting: error loading config file: stat /etc/graylog/collector-sidecar/generated/filebeat.yml: no such file or directory filebeat2018/02/13 10:13:52.080407 beat.go:339: CRIT Exiting: error loading config file: stat /etc/graylog/collector-sidecar/generated/filebeat.yml: no such file or directory Exiting: error loading config file: stat /etc/graylog/collector-sidecar/generated/filebeat.yml: no such file or directory filebeat2018/02/13 10:13:55.084897 beat.go:339: CRIT Exiting: error loading config file: stat /etc/graylog/collector-sidecar/generated/filebeat.yml: no such file or directory Exiting: error loading config file: stat /etc/graylog/collector-sidecar/generated/filebeat.yml: no such file or directory ``` ---
**Author:** ![cdeng](https://avatars.discourse-cdn.com/v4/letter/c/e79b87/32.png) [@cdeng](https://community.graylog.org/u/cdeng)\ **Post date:** [February 13, 2018, 10:33am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/9 "2018-02-13T10:33:01Z")
Should the key and certs for filebeat put on graylog server for sidebar download or manually put on filebeat host? ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [February 13, 2018, 10:42am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/10 "2018-02-13T10:42:00Z")
is your configured `server_url` in the sidecar configuration your Graylogs `rest_listen_uri` ? Did you checked your `collector_sidecar.yml` that is is a valid .yml file? Are you able to reach the configured `server_url` from the server where you run the collector sidecar? Did you add your CA in a proper way to that Servers trust store? Given your certifiate is named `foo.crt` ## Debian / Ubuntu ```auto Copy your CA to dir `/usr/local/share/ca-certificates/` Use command like: `sudo cp foo.crt /usr/local/share/ca-certificates/foo.crt` Update the CA store: `sudo update-ca-certificates` ``` ## CentOS / RedHat ```auto Install the ca-certificates package: `yum install ca-certificates` Enable the dynamic CA configuration feature: `update-ca-trust force-enable` Add it as a new file to /etc/pki/ca-trust/source/anchors/: `cp foo.crt /etc/pki/ca-trust/source/anchors/` Use command: `update-ca-trust extract` ``` Are you able to reach the configure `server_uri` with curl? What is the output of `curl -I YOURURI` ? ---
**Author:** ![cdeng](https://avatars.discourse-cdn.com/v4/letter/c/e79b87/32.png) [@cdeng](https://community.graylog.org/u/cdeng)\ **Post date:** [February 13, 2018, 10:48am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/11 "2018-02-13T10:48:04Z")
Yes. i have configured server\_url to the rest\_listen\_uri, and collector sidecar can reach the server\_url. i have add the CA cert into Java Trusted CA store on the graylog-server, but not the system’s trust CA store: ```auto cat /etc/graylog/collector-sidecar/collector_sidecar.yml server_url: https://gl1.mylogs.com:9000/api/ update_interval: 10 tls_skip_verify: true send_status: true list_log_files: /var/log/chrony node_id: clr.mylogs.com collector_id: file:/etc/graylog/collector-sidecar/collector-id cache_path: /var/cache/graylog/collector-sidecar log_path: /var/log/graylog/collector-sidecar log_rotation_time: 86400 log_max_age: 604800 tags: - linux - ntp - chronyd backends: - name: nxlog enabled: false binary_path: /usr/bin/nxlog configuration_path: /etc/graylog/collector-sidecar/generated/nxlog.conf - name: filebeat enabled: true binary_path: /usr/bin/filebeat configuration_path: /etc/graylog/collector-sidecar/generated/filebeat.yml ``` ---
**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\ **Post date:** [February 13, 2018, 10:49am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/12 "2018-02-13T10:49:06Z")
@cdeng Please properly format your configuration and text snippets for readability: [http://commonmark.org/help/](http://commonmark.org/help/) Example: ```` ``` Some text More text ``` ```` ---
**Author:** ![cdeng](https://avatars.discourse-cdn.com/v4/letter/c/e79b87/32.png) [@cdeng](https://community.graylog.org/u/cdeng)\ **Post date:** [February 13, 2018, 10:54am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/13 "2018-02-13T10:54:48Z")
> [@jan](#): > > server\_uri curl -I [https://gl1.mylogs.com:9000/api/](https://gl1.mylogs.com:9000/api/) HTTP/1.1 200 OK X-Graylog-Node-ID: f9818ad6-9b6b-41d0-83ae-0bfe8ab4fa72 X-Runtime-Microseconds: 1325 Content-Length: 232 Content-Type: application/json Date: Tue, 13 Feb 2018 10:54:14 GMT ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [February 13, 2018, 11:16am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/14 "2018-02-13T11:16:28Z")
> i have add the CA cert into Java Trusted CA store on the graylog-server Your client server - where the collector-sidecar runs - need to have the CA which is used to sign the certificate that is used to secure your Graylog server. How should a _go_ program running on another server know that the _CA_ certificate you have used to sign the certificate can be trusted? ---
**Author:** ![cdeng](https://avatars.discourse-cdn.com/v4/letter/c/e79b87/32.png) [@cdeng](https://community.graylog.org/u/cdeng)\ **Post date:** [February 13, 2018, 11:27am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/15 "2018-02-13T11:27:20Z")
> [@jan](#): > > update-ca-trust extract the collector side already add the CA to the system trusted CA list. ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [February 13, 2018, 11:31am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/16 "2018-02-13T11:31:35Z")
and you have configurations in Graylog for your configured tags? ```auto tags: - linux - ntp - chronyd ``` with some kind of configuration? ---
**Author:** ![cdeng](https://avatars.discourse-cdn.com/v4/letter/c/e79b87/32.png) [@cdeng](https://community.graylog.org/u/cdeng)\ **Post date:** [February 13, 2018, 11:31am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/17 "2018-02-13T11:31:51Z")
The strange is that on the graylog server’s collector’s status, we can see the log files list, but it seems the configuration does not download. ---
**Author:** ![cdeng](https://avatars.discourse-cdn.com/v4/letter/c/e79b87/32.png) [@cdeng](https://community.graylog.org/u/cdeng)\ **Post date:** [February 13, 2018, 11:32am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/18 "2018-02-13T11:32:49Z")
yes. i have attached all those tags with the configuration on graylog server side. ---
**Author:** ![cdeng](https://avatars.discourse-cdn.com/v4/letter/c/e79b87/32.png) [@cdeng](https://community.graylog.org/u/cdeng)\ **Post date:** [February 13, 2018, 11:46am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/19 "2018-02-13T11:46:38Z")
It seems the SSL/TLS between sidecar and graylog works, but when make a configuration for collector failed. i am not trying to use the server self signed certificate, but input the key file and cert file for collector. does the key/cert file in the output configuration should point to path on the graylog server or collector host ? is there any ownership requirements for it ? ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [February 13, 2018, 11:48am UTC](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139/20 "2018-02-13T11:48:48Z")
did you have created a `beats` input on Graylog to receive the messages? The certificates needs to be on the server where they need to be used (filebeat on the sending server, beats input on all Graylog servers). Did you tried the communication between filebeat and graylog without tls to verify that everything else is working? [Next page](https://community.graylog.org/t/sidecar-cannot-get-the-configuration-for-filebeat/4139.md?page=2)