Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Pkg system died again-Unable to check for updates, No trusted public keys found

    Scheduled Pinned Locked Moved 2.4 Development Snapshots
    1 Posts 1 Posters 941 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • luckman212L
      luckman212 LAYER 8
      last edited by

      I was humming along with the 2.4 snaps until yesterday.  Suddenly my pkg system stopped working and pfSense refused to update:

      [2.4.0-BETA][admin@r1]/root: pkg update
      Updating pfSense-core repository catalogue...
      Fetching meta.txz: 100%    940 B   0.9kB/s    00:01
      pkg: No trusted public keys found
      repository pfSense-core has no meta file, using default settings
      Fetching packagesite.txz: 100%    2 KiB   2.3kB/s    00:01
      pkg: No trusted public keys found
      Unable to update repository pfSense-core
      Updating pfSense repository catalogue...
      Fetching meta.txz: 100%    936 B   0.9kB/s    00:01
      pkg: No trusted public keys found
      repository pfSense has no meta file, using default settings
      Fetching packagesite.txz: 100%  122 KiB 124.9kB/s    00:01
      pkg: No trusted public keys found
      Unable to update repository pfSense
      

      I have gotten in this jam before but this time it took more aggressive steps to get out of it. Not sure how to better troubleshoot but…

      • tried simple reboot (no good)
      • tried pkg update -f and pkg upgrade -f
      • tried pkg info -x pfSense to make sure pfSense-base was installed (it was)
      • tried pfSense-upgrade -4 (no good)
      • checked DNS resolution (both v4 and v6) from the console (it was all fine)
      • restarted Unbound (didn't help)
      • added '8.8.8.8' to /etc/resolv.conf as a test (did not help)
      • checked my /usr/local/etc/pkg/repos/pfSense.conf file (seemed correct)
      • re-downloaded keys (they were already there, and this did not fix the problem)
      fetch -qo /usr/local/share/pfSense/keys/pkg/trusted/ https://raw.githubusercontent.com/pfsense/pfsense/master/src/usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406
      

      In the end the only thing that "worked" was to change the URLs in the repo from the Netgate ones to the pfSense community ones:

      pkg+https://beta.pfsense.org/packages/pfSense_master_amd64-core
      pkg+https://beta.pfsense.org/packages/pfSense_master_amd64-pfSense_devel
      
      

      Once I did that I was able to update + gitsync again and am now on 2.4.0.b.20170207.2344 snap.

      Of course, I am now on the CE edition which wasn't my intention.  :( Is there any way to get "back on track"?  Still puzzled as to how this happened.

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.