pfSense Gold Subscription

Author Topic: Upgrade Fail 2.4  (Read 193 times)

0 Members and 1 Guest are viewing this topic.

Offline appleholidays_it

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Upgrade Fail 2.4
« on: November 17, 2017, 12:50:39 am »
Hi Guys,

I'm on pfSense 2.3.4 and I need to update this to the newer version, which is 2.4.0.
The issue is when I'm running the update, it gives me following error message: "pkg-static: https://pkg.pfsense.org/pfSense_v2_4_0_amd64-pfSense_v2_4_0/All/webfonts-0.30_13.txz: Operation timed out Failed"

I think "pkg.pfsense.org" domain is not resolvable. How do I solve this?
« Last Edit: November 17, 2017, 01:12:07 am by appleholidays_it »

Offline jimp

  • Administrator
  • Hero Member
  • *****
  • Posts: 21404
  • Karma: +1437/-26
    • View Profile
Re: Upgrade Fail 2.4
« Reply #1 on: November 17, 2017, 07:44:42 am »
The pkg.pfsense.org DNS is fine (it uses SRV records, so you're probably checking it wrong). It can resolve it OK but not download the files.

If it was a DNS problem the error would be something else.

It looks like it's getting partway through and then failing or timing out though. If you try it again, does it fail on the same file? Is there anything else like a proxy or another firewall in front of this one that could be slowing it down or interfering?
Need help fast? Commercial Support!

Co-Author of pfSense: The Definitive Guide. - Check the Doc Wiki for FAQs.

Do not PM for help!

Offline binhdh

  • Newbie
  • *
  • Posts: 4
  • Karma: +0/-1
    • View Profile
Re: Upgrade Fail 2.4
« Reply #2 on: November 18, 2017, 01:27:25 am »
You should not upgrade to 2.4.
I tried and completely disappointed  ::) ::)

Offline divsys

  • Hero Member
  • *****
  • Posts: 919
  • Karma: +91/-1
    • View Profile
Re: Upgrade Fail 2.4
« Reply #3 on: November 18, 2017, 01:52:16 am »
Quote
You should not upgrade to 2.4.
I tried and completely disappointed

Sorry, have to disagree completely.
My experience migrating 20+ installations at various revisions from 2.2.5 up to 2.3.5 has been very positive.

The only (minor) headache I ran into was a system that wouldn't auto-update from 2.3.0.
It seemed to be locked down to a development stream and wouldn't let me change it.
Simplest fix was to take a backup of the config.xml, reinstall from scratch and restore the backup.

Full repair was perhaps 20min.

Other than that it's been quite painless for me.

Whatever you do, make sure you have a backup of your current setup.

Just my $.02
-jfp