Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Key 417A0893 can't be retrieved from keyserver for apt
See original GitHub issueSteps to reproduce
During adding the new apt-get feed:
sudo apt-key adv --keyserver apt-mo.trafficmanager.net --recv-keys 417A0893
Actual behavior
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --homedir /tmp/tmp.P0TjF2Xu2x --no-auto-check-trustdb --trust-model always --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-security-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-stable.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-squeeze-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-squeeze-stable.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg --keyserver apt-mo.trafficmanager.net --recv-keys 417A0893
gpg: requesting key 417A0893 from hkp server apt-mo.trafficmanager.net
gpgkeys: key 417A0893 can't be retrieved
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
Environment data
uname -a output:
Linux debian 3.16.0-4-amd64 dotnet/sdk#4283 SMP Debian 3.16.7-ckt20-1+deb8u4 (2016-02-29) x86_64 GNU/Linux
curl apt-mo.trafficmanager.net --head output (besides being behind corporate proxy):
HTTP/1.1 200 OK
Date: Fri, 01 Apr 2016 10:58:11 GMT
Server: Apache/2.4.7 (Ubuntu)
Last-Modified: Mon, 29 Sep 2014 19:32:50 GMT
ETag: "2cf6-50439550f3c1c"
Accept-Ranges: bytes
Content-Length: 11510
Vary: Accept-Encoding
Content-Type: text/html
And gpg --keyserver hkp://apt-mo.trafficmanager.net -v --list-keys output:
gpg: using PGP trust model
And more /etc/apt/sources.list.d/dotnetdev.list output:
deb [arch=amd64] http://apt-mo.trafficmanager.net/repos/dotnet/ trusty main
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:14 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Since keyservers are synchronizing keys you can actually use any other keyserver like the Ubuntu one for getting the MS key:
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 417A0893I agree that it’s a good idea to switch the docs for apt-mo.trafficmanager.net to port 80 too (on Mono we did this because users were constantly running into firewall issues).
failed:
sudo apt-key adv --keyserver apt-mo.trafficmanager.net --recv-keys 417A0893worked:
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 417A0893