# Debian repo seems unhappy **URL:** \ **Category:** Graylog Central (peer support)\ **Created:** [November 19, 2020, 6:38pm UTC](https://community.graylog.org/t/debian-repo-seems-unhappy/17901 "2020-11-19T18:38:27Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![patcable](https://avatars.discourse-cdn.com/v4/letter/p/a698b9/32.png) [@patcable](https://community.graylog.org/u/patcable)\ **Post date:** [November 19, 2020, 6:38pm UTC](https://community.graylog.org/t/debian-repo-seems-unhappy/17901/1 "2020-11-19T18:38:28Z")
`apt update` seems a little broken using the Graylog repos: ```auto Get:5 https://packages.graylog2.org/debian stable InRelease [1,926 B] Err:5 https://packages.graylog2.org/debian stable InRelease Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?) Reading package lists... Done E: Failed to fetch https://packages.graylog2.org/debian/dists/stable/InRelease Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?) E: Some index files failed to download. They have been ignored, or old ones used instead. ``` Indeed, curling those URLs seem to indicate an issue with what gets pulled down. Looks like there’s a redirect to the packages s3 bucket since I get redirected to ```auto https://graylog2-package-repository.s3.eu-west-1.amazonaws.com/debian/dists/stable/Release?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20201119T183643Z&X-Amz-SignedHeaders=host&X-Amz-Expires=600&X-Amz-Credential=AKIA...%2Feu-west-1%2Fs3%2Faws4_request&X-Amz-Signature=removed ``` ---
**Author:** ![bernd](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/bernd/32/5_2.png) [@bernd](https://community.graylog.org/u/bernd)\ **Post date:** [November 19, 2020, 7:10pm UTC](https://community.graylog.org/t/debian-repo-seems-unhappy/17901/2 "2020-11-19T19:10:57Z")
@patcable I am unable to reproduce this on an Ubuntu 20.04 machine. It looks like you are using the wrong repository URL. Please following the instructions here if you want to install the sources list file manually: > **[Operating System Packages — Graylog 4.0.0 documentation](https://docs.graylog.org/en/4.0/pages/installation/operating_system_packages.html#manual-repository-installation)** You can also use the repository package that will also install the correct GPG key automatically: > **[Operating System Packages — Graylog 4.0.0 documentation](https://docs.graylog.org/en/4.0/pages/installation/operating_system_packages.html#deb-apt)** A quick fix is probably to change the entry in your sources.list like this: ```diff - deb https://packages.graylog2.org/debian/ stable 4.0 + deb https://packages.graylog2.org/repo/debian/ stable 4.0 ``` ---
**Author:** ![patcable](https://avatars.discourse-cdn.com/v4/letter/p/a698b9/32.png) [@patcable](https://community.graylog.org/u/patcable)\ **Post date:** [November 19, 2020, 7:38pm UTC](https://community.graylog.org/t/debian-repo-seems-unhappy/17901/3 "2020-11-19T19:38:25Z")
Oh man… this is 100% my bad - so sorry for the package panic! I was using Chef to deploy, and the Chef cookbook references [this url](https://raw.githubusercontent.com/Graylog2/fpm-recipes/master/recipes/graylog-repository/files/deb/graylog-keyring.gpg) for the gpg key. That moved, and the way that the error presented to me had me change the URL, and got the second error. Happy to make a PR for the value at [https://github.com/Graylog2/graylog2-cookbook/blob/master/attributes/default.rb#L22](https://github.com/Graylog2/graylog2-cookbook/blob/master/attributes/default.rb#L22) if I know where it should be pulled from… ---
**Author:** ![bernd](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/bernd/32/5_2.png) [@bernd](https://community.graylog.org/u/bernd)\ **Post date:** [November 19, 2020, 7:46pm UTC](https://community.graylog.org/t/debian-repo-seems-unhappy/17901/4 "2020-11-19T19:46:23Z")
> [@patcable](#): > > Oh man… this is 100% my bad - so sorry for the package panic! No worries! 😄 Oh, that’s a good catch! We removed the `master` branch from the fpm-recipes repository, that’s why it’s failing for you now. Sorry about that! You can use the following URL to get the public key: [https://packages.graylog2.org/repo/debian/pubkey.gpg](https://packages.graylog2.org/repo/debian/pubkey.gpg) That’s in the debian path, but it’s the same for RPM. We will update our repos to copy the public key file into the RPM repos as well. Thanks for the report! 👍 ---
**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:** [December 3, 2020, 7:46pm UTC](https://community.graylog.org/t/debian-repo-seems-unhappy/17901/5 "2020-12-03T19:46:24Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.