Netgate SG-1000 microFirewall

Author Topic: Brand new install: Unable to retrieve package information.  (Read 186 times)

0 Members and 1 Guest are viewing this topic.

Offline Maxburn

  • Newbie
  • *
  • Posts: 8
  • Karma: +0/-0
    • View Profile
Brand new install: Unable to retrieve package information.
« on: January 11, 2018, 09:22:52 am »
note; I'm very new to pfsense

Problem:
Edit: the larger problem seems to be no internet access. I thought the wizard would leave me with a working router but I guess not.
Under Package Manager/Available Packages I'm getting: Unable to retrieve package information. Searched around a bit and found some advice regarding pkg clean, pkg update, pkg upgrade, reboot. Errors for those are below, and searching around I'm seeing results from 2.3 failed upgrades and it being necessary to create directories for these missing files or directories but this being a brand new install this all seems weird, what's wrong?

History:
I installed 2.4.2 release last night and went through the wizard choosing mostly defaults, nothing strange I'm aware of, chose 9.9.9.9 and 8.8.4.4 for DNS. I didn't have the WAN connected, I wanted to have everything in and working before I connected it to the internet. Now with everything connected it acts as a router fine and update check says it's good.

Results from pkg clean
Quote
pkg: Repository pfSense-core missing. 'pkg update' required
pkg: No package database installed.  Nothing to do!

Results from pkg update
Quote
Updating pfSense-core repository catalogue...
pkg: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
pkg: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-core/meta.txz: Authentication error
repository pfSense-core has no meta file, using default settings
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
pkg: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-core/packagesite.txz: Authentication error
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
pkg: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-pfSense_v2_4_2/meta.txz: Authentication error
repository pfSense has no meta file, using default settings
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
pkg: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-pfSense_v2_4_2/packagesite.txz: Authentication error
Unable to update repository pfSense
Error updating repositories!

« Last Edit: January 11, 2018, 10:12:35 am by Maxburn »

Offline Maxburn

  • Newbie
  • *
  • Posts: 8
  • Karma: +0/-0
    • View Profile
Re: Brand new install: Unable to retrieve package information.
« Reply #1 on: January 11, 2018, 10:03:11 am »
On a hunch my PiHole on my network was blocking it I connected WAN straight to my cable modem and had pfsense reboot. In that configuration windows still was reporting no internet connection and I couldn't reach this site for example but the pkg update comes back differently now. Even reset to defaults and reran the wizard same results.

Quote
Updating pfSense-core repository catalogue...
pkg: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
pkg: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-core/meta.txz: No address record
repository pfSense-core has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-core/packagesite.txz: No address record
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
pkg: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-pfSense_v2_4_2/meta.txz: No address record
repository pfSense has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-pfSense_v2_4_2/packagesite.txz: No address record
Unable to update repository pfSense
Error updating repositories!

Offline KOM

  • Hero Member
  • *****
  • Posts: 5609
  • Karma: +688/-23
    • View Profile
Re: Brand new install: Unable to retrieve package information.
« Reply #2 on: January 11, 2018, 10:27:29 am »
Do you have ANY connectivity from WAN, eg Diagnostics - Ping?

Here is a large list of things to check.

https://doc.pfsense.org/index.php/Connectivity_Troubleshooting

Offline Maxburn

  • Newbie
  • *
  • Posts: 8
  • Karma: +0/-0
    • View Profile
Re: Brand new install: Unable to retrieve package information.
« Reply #3 on: January 11, 2018, 12:53:36 pm »
Thanks for that list, should have started with the most obvious being that WAN wasn't getting an IP lease. Everything working much better now after fixing that.