Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debian repository not signed #7048

Open
2 tasks done
nwa573 opened this issue Oct 22, 2024 · 3 comments
Open
2 tasks done

Debian repository not signed #7048

nwa573 opened this issue Oct 22, 2024 · 3 comments
Labels

Comments

@nwa573
Copy link

nwa573 commented Oct 22, 2024

Is it a bug?

  • I know this is an issue with the app, and contacting Mullvad support is not relevant.

I have checked if others have reported this already

  • I have checked the issue tracker to see if others have reported similar issues.

Current Behavior

I followed the instructions at https://mullvad.net/en/help/install-mullvad-app-linux to add the stable repository, but when I run sudo apt update I get

W: GPG error: https://repository.mullvad.net/deb/stable bookworm InRelease: Unknown error executing apt-key
E: The repository 'https://repository.mullvad.net/deb/stable bookworm InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Expected Behavior

sudo apt update runs successfully

Steps to Reproduce

Follow the Debian instructions at https://mullvad.net/en/help/install-mullvad-app-linux

Failure Logs

No response

Operating system version

Debian 12.7

Mullvad VPN app version

No response

Additional Information

No response

@nwa573 nwa573 added the bug label Oct 22, 2024
@faern
Copy link
Member

faern commented Oct 23, 2024

We had apt repository server issues in parts of the world yesterday. Please try again today and see if it works better! Our repositories are signed.

@nwa573
Copy link
Author

nwa573 commented Oct 28, 2024

I'm still getting the same error. Is there any more debug info I can give you?

@strykenKN
Copy link

the same problem also exists under Ubuntu. I have already reported it here, but nobody seems to be interested, for whatever reason.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants