New install of v2.5.0 and several things are not working...
Since a fresh install of v2.5.0, I can't check for updates. None of the repos work. But, I can't even find the repos from inside my web browser (even tried files00.netgate.net). Also, I can't see my CPU stats on the dashboard. Get a spinning cog that finally gives up. Also, I can't install any packages because there are no packages available to install.
What is going on and how do I fix this?
Here is what is happening when the repo tries to update:
[2.5.0-RELEASE][user@server]/root: pkg-static upgrade -f Updating pfSense-core repository catalogue... pkg-static: https://packages.netgate.com/pfSense_v2_5_0_amd64-core/meta.txz: No address record repository pfSense-core has no meta file, using default settings pkg-static: https://packages.netgate.com/pfSense_v2_5_0_amd64-core/packagesite.txz: No address record Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg-static: https://packages.netgate.com/pfSense_v2_5_0_amd64-pfSense_v2_5_0/meta.txz: No address record repository pfSense has no meta file, using default settings pkg-static: https://packages.netgate.com/pfSense_v2_5_0_amd64-pfSense_v2_5_0/packagesite.txz: No address record Unable to update repository pfSense Error updating repositories!
Okay. I figured it out. I'll post notes here in the hopes it helps someone else.
Under System -> General Setup:
I had three DNS servers configured. All of the servers were public and valid (owned by my ISP), but I had to remove these entries and select the "Allow DNS server list to be overridden by DHCP/PPP on WAN" checkbox. I also had to change the "DNS Resoultion Behavior" to be "Use local DNS (127.0.0.1), fall back to remote DNS Servers (Default). I then added a new public DNS server (184.108.40.206) for my DHCP clients to use if the pfSense router fails to resolve for them.
@breusshe I upgraded as well and have similar issues. DNS Reslover seems broke and OpenVPN routing was also broke. I spent the entire morning trying to find a root cause but I'm giving up and downgrading.
@nicheath did you try what I did to fix my issue?
@breusshe I ended up finding a setting that was different between my old vpn setup and the vpn company setup for 2.5. I changed that and everything suddenly worked.
I still can't really explain why though. The entire time my VPN would connect but it did not appear to route traffic. No log entries that I could find that told me what was happening on that end either.