# Graylog https access issue **URL:** \ **Category:** Graylog Central (peer support)\ **Tags:** sidecar, nxlog, nodatanx\ **Created:** [March 12, 2018, 2:12am UTC](https://community.graylog.org/t/graylog-https-access-issue/4521 "2018-03-12T02:12:51Z")\ **Posts on this page:** 3\ **Page:** 2
**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:** [March 14, 2018, 2:47pm UTC](https://community.graylog.org/t/graylog-https-access-issue/4521/21 "2018-03-14T14:47:28Z")
lets clarify @v_2nas on this. You have the Graylog Webinterface and API configured to run with https. Now you need to configure the collector-sidecar to use this https URL ( because the `rest_listen_uri` is only reachable via https ). The Input that you have running in Graylog and use as a log target in NXLOG is independent - you can run that with TLS or without. ---
**Author:** ![v\_2nas](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/v_2nas/32/268_2.png) [@v\_2nas](https://community.graylog.org/u/v_2nas)\ **Post date:** [March 16, 2018, 8:18am UTC](https://community.graylog.org/t/graylog-https-access-issue/4521/22 "2018-03-16T08:18:29Z")
Thanks @jan for clarifying. I have made the changes to the sidecar collector yml file and was able to see them reporting again to graylog. ---
**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:** [March 30, 2018, 8:18am UTC](https://community.graylog.org/t/graylog-https-access-issue/4521/23 "2018-03-30T08:18:38Z")
Closed on March 30, 2018, 8:18am UTC This topic was automatically closed 14 days after the last reply. New replies are no longer allowed. [Previous page](https://community.graylog.org/t/graylog-https-access-issue/4521.md?page=1)