# Graylog 3.2.4 file sidecar "Collector Administration" page empty **URL:** \ **Category:** Graylog Central (peer support)\ **Tags:** sidecar, filebeat-windows\ **Created:** [April 2, 2020, 6:32pm UTC](https://community.graylog.org/t/graylog-3-2-4-file-sidecar-collector-administration-page-empty/14797 "2020-04-02T18:32:58Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![greenmind](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/greenmind/32/6142_2.png) [@greenmind](https://community.graylog.org/u/greenmind)\ **Post date:** [April 2, 2020, 6:32pm UTC](https://community.graylog.org/t/graylog-3-2-4-file-sidecar-collector-administration-page-empty/14797/1 "2020-04-02T18:32:58Z")
I’m using Graylog v3.2.4 with a nginx proxy using ubuntu 18.04 on google cloud. I’m fairly new to this and have made progress but cannot compete the setup. I’ve got the instance up and running on the web and am following the step-by-step guide found here: [https://docs.graylog.org/en/3.0/pages/sidecar.html#sidecar-overview](https://docs.graylog.org/en/3.0/pages/sidecar.html#sidecar-overview) I get to the part that reads: Next we need to assign our newly created configuration (and therefore the Filebeat collector) to our sidecar. Go to the `Collector Administration` page. However, when I go to the Collector Administration page as the instructions say, I get an empty screen with nothing to select from. ![image](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/2X/b/b34770e0ddab035b8374451520d6a5526f3145b3.png) I’ve searched for help on this but everything I find is for older versions. I’m using the sidecar 1.0.x and filebeat 7.6.2. Any thoughts? ---
**Author:** ![shoothub](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/shoothub/32/6412_2.png) [@shoothub](https://community.graylog.org/u/shoothub)\ **Post date:** [April 3, 2020, 9:18am UTC](https://community.graylog.org/t/graylog-3-2-4-file-sidecar-collector-administration-page-empty/14797/2 "2020-04-03T09:18:57Z")
Check these great resources: > **[Introduction to Graylog Sidecar | Features](https://www.graylog.org/features/sidecar)** > > Graylog Sidecar allows for centralized and stackable configuration, utilizing any log collection agent. It was created with built-in security and compatibility. > **[Graylog Inputs | Graylog](https://www.graylog.org/webinars/graylog-inputs)** > > Graylog is a leading centralized log management solution built to open standards for capturing, storing, and enabling real-time analysis of terabytes of machine data. We deliver a better user experience by making analysis ridiculously fast,... > **[Windows Filebeat Configuration and Graylog Sidecar | The Graylog Blog](https://www.graylog.org/post/windows-filebeat-configuration-and-graylog-sidecar)** > > Graylog sidecar can create and manage a centralized configuration for a filebeat agent, to gather logs from a local server that is not part of the Windows Event Channel and across all your infrastructure hosts. ---
**Author:** ![tmacgbay](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tmacgbay/32/3878_2.png) [@tmacgbay](https://community.graylog.org/u/tmacgbay)\ **Post date:** [April 3, 2020, 8:11pm UTC](https://community.graylog.org/t/graylog-3-2-4-file-sidecar-collector-administration-page-empty/14797/3 "2020-04-03T20:11:24Z")
Until you have something set up with beats/nxlog reporting in to your properly set up INPUT, you won’t see it listed in Administration. Check your sidecar client side configuration - there are log file in there that will tell you what it’s doing… or trying to do. Details on all that in the links shoothub gave you. ---
**Author:** ![greenmind](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/greenmind/32/6142_2.png) [@greenmind](https://community.graylog.org/u/greenmind)\ **Post date:** [April 6, 2020, 3:32pm UTC](https://community.graylog.org/t/graylog-3-2-4-file-sidecar-collector-administration-page-empty/14797/4 "2020-04-06T15:32:38Z")
OK, got it! Unfortunately it looks like my filebeat configuration is incorrect as I now get: logstash/async.go:256 Failed to publish events caused by: write tcp 10.100.2.137:51752-\>34.68.168.211:5044: write: broken pipe ---
**Author:** ![tmacgbay](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tmacgbay/32/3878_2.png) [@tmacgbay](https://community.graylog.org/u/tmacgbay)\ **Post date:** [April 6, 2020, 7:18pm UTC](https://community.graylog.org/t/graylog-3-2-4-file-sidecar-collector-administration-page-empty/14797/5 "2020-04-06T19:18:19Z")
There are some posts around for working filebeat configurations - I think I posted one a while back… something to compare to that might help find where the error is (Mine are for windows). ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\ **Post date:** [April 20, 2020, 7:18pm UTC](https://community.graylog.org/t/graylog-3-2-4-file-sidecar-collector-administration-page-empty/14797/6 "2020-04-20T19:18:21Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.