I installed a couple of days ago K6 cli following Installation
Lately i’ve runned a system update and this message is shown.
Err:10 https://dl.k6.io/deb stable InRelease
The following signatures were invalid: EXPKEYSIG C780D0BDB1A69C86 k6.io (key for signing binaries) <security@k6.io>
Hi @xiscodev Try to reinstall k6 again or follow common issues during installation k6
Hi @xiscodev
Welcome to the community forum 
Thanks for reporting this. I believe it could be related to "k6.io (key for signing binaries) <security@k6.io>" outdated · Issue #2973 · grafana/k6 · GitHub whixh we are already working on.
Until it is fixed adding --allow-unauthenticated to apt should fix it.
We’ll keep you posted.
Cheers!
If it’s urgent, you can override the expired key by editing /etc/apt/sources.list.d/k6.list:
deb [trusted=yes] https://dl.k6.io/deb stable main
Hi,
This should be fixed now. We’ll discuss this internally and improve our processes to prevent this from happening again. Apologies for the inconveniences it caused and again, many thanks for reporting the issue.
Cheers!
I confirm its working now, got to reinstall keys again to remove warning
Hello, i have the same problem today on Ubuntu 20.04.
Thanks for your answer
Hey @Fred,
can you please do a more accurate report on your issue?
Did you follow the instructions for installing on Ubuntu? What command is failing for you? Are you updating or doing a fresh installation? Any details you can add regarding the context will be useful for helping you.
Thanks.
Hi @codebien,
I’am behind a proxy, so, i try this solution.
Here the result apt-key
Thanks for your help
Hey @Fred,
sorry for the late reply.
Did you solve your issue? If not you may interested in looking into this troubleshooting documentation page.
Let me know if it helps.
Hello codebien,
no, the problem si not resolve
Hi @Fred,
judging by your screenshot and the gpg: keyserver receive failed: No name error, it seems there is some connection issue between your machine and the Ubuntu keyserver, or the keyserver itself is flaky, which is a common issue, unfortunately 
.
As a workaround, you can also download the GPG key from our package server dl.k6.io, and then import it into the keyring. The complete installation instructions in that case would be:
sudo gpg -k
curl -fsSLO https://dl.k6.io/key.gpg
sudo gpg --no-default-keyring --keyring /usr/share/keyrings/k6-archive-keyring.gpg --import key.gpg
echo "deb [signed-by=/usr/share/keyrings/k6-archive-keyring.gpg] https://dl.k6.io/deb stable main" | sudo tee /etc/apt/sources.list.d/k6.list
sudo apt-get update
sudo apt-get install k6
The important thing you should see in the output is:
gpg: keybox '/usr/share/keyrings/k6-archive-keyring.gpg' created
gpg: key 77C6C491D6AC1D69: public key "k6.io (key for signing binaries) <security@k6.io>" imported
gpg: Total number processed: 1
gpg: imported: 1
From your screenshot I see that you have added the correct key to the /etc/apt/trusted.gpg keyring, but not to the /usr/share/keyrings/k6-archive-keyring.gpg keyring which is specified in the APT sources list. I reckon that if you change the signed-by value in /etc/apt/sources.list.d/k6.list to be /etc/apt/trusted.gpg, you would be able to install k6 without an issue as well.
Hope this helps!