I tried again today and it failed. I found this post https://forum.pfsense.org/index.php?topic=134042.0 which referred to:
https://forum.pfsense.org/index.php?topic=125873.msg695386#msg695386 I did that procedure as stated (switch to dev, check for update via SSH, cancel, switch to stable) and the update installs now. Log shows: [1/75] Fetching pfSense-rc-2.3.4_1.txz: . done Looks like it was maybe stuck looking for 2.3.4 and should have been looking for 2.3.4_1? -- Steve Yates ITS, Inc. -----Original Message----- From: List [mailto:list-boun...@lists.pfsense.org] On Behalf Of Steve Yates Sent: Monday, July 24, 2017 12:39 PM To: pfSense Support and Discussion Mailing List <list@lists.pfsense.org> Subject: [pfSense] Update to 2.3.4(_1) fails (Not Found) This happened last week so I thought I'd wait a bit and try again. I'm updating from 2.3.3_1 to 2.3.4_1. Error: pkg: https://pkg.pfsense.org/pfSense_v2_3_4_amd64-core/All/pfSense-rc-2.3.4.txz: Not Found Remembering earlier conversations, pfSense uses an SRV record for downloading, so: ; <<>> DiG 9.10.3-P4 <<>> srv _https._tcp.pkg.pfsense.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54700 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 5 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4000 ;; QUESTION SECTION: ;_https._tcp.pkg.pfsense.org. IN SRV ;; ANSWER SECTION: _https._tcp.pkg.pfsense.org. 60 IN SRV 10 10 443 files00.netgate.com. _https._tcp.pkg.pfsense.org. 60 IN SRV 10 10 443 files01.netgate.com. ;; ADDITIONAL SECTION: files00.netgate.com. 3471 IN A 162.208.119.41 files00.netgate.com. 3471 IN AAAA 2610:1c1:0:6::41 files01.netgate.com. 3231 IN A 162.208.119.40 files01.netgate.com. 3231 IN AAAA 2610:1c1:0:6::40 However https://files00.netgate.com/pfSense_v2_3_4_amd64-core/All/pfSense-rc-2.3.4.txz shows a 404 error? https://files00.netgate.com/pfSense_v2_3_4_amd64-core/All/ does not list that file...it lists several 2.3.4_1 files. Should a version upgrade from 2.3.3_1 to 2.3.4 and then to 2.3.4_1, which is what I recall from earlier upgrades? Or straight to 2.3.4_1 in which case the upgrader seems to be looking for an old file...? Update Settings is using Stable (Default) branch. Log shows: >>> Updating repositories metadata... Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. >>> Unlocking package pfSense-kernel-pfSense... done. >>> Downloading upgrade packages... Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. Checking for upgrades (129 candidates): .......... done Processing candidates (129 candidates): ..... done The following 76 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: (...long list...) Installed packages to be REINSTALLED: (...15 packages...) Number of packages to be upgraded: 61 Number of packages to be reinstalled: 15 The process will require 1 MiB more space. 68 MiB to be downloaded. pkg: https://pkg.pfsense.org/pfSense_v2_3_4_amd64-core/All/pfSense-rc-2.3.4.txz: Not Found >>> Locking package pfSense-kernel-pfSense... done. Failed -- Steve Yates ITS, Inc. _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold