Version 2.3.4 is available.
-
Hi All,
I have issues with update from 2.3.3-RELEASE-p1 to 2.3.4.
Web GUI says: Unable to check for updates.
From command line, I got the following:
pfSense-upgrade -4
Updating repositories metadata…
Updating pfSense-core repository catalogue...
pkg: https://pkg.pfsense.org/pfSense_v2_3_4_amd64-core/meta.txz: Not Found
repository pfSense-core has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_3_4_amd64-core/packagesite.txz: Not Found
Unable to update repository pfSense-core
Updating pfSense repository catalogue…
pkg: https://pkg.pfsense.org/pfSense_v2_3_4_amd64-pfSense_v2_3_4/meta.txz: Not Found
repository pfSense has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_3_4_amd64-pfSense_v2_3_4/packagesite.txz: Not Found
Unable to update repository pfSenseDNS resolution and internet connection are working fine.
I have copied and tried to get the file via browser, but it seems update site has issue:
404 Not Found
nginx/1.10.3Can you please help me?
-
I have two machines that I updated remotely that are no longer available via openvpn, although they are up and pingable. I use a TAP UDP configuration, and both machines are awake, but fail TLS negotiation. I am using the current Tunnelblick beta.
The relevant error from Tunnelblick reads:
2017-05-07 08:22:20 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
2017-05-07 08:22:20 TLS Error: TLS handshake failedOh well… There goes my Sunday. :-[
-
I have two machines that I updated remotely that are no longer available via openvpn, although they are up and pingable. I use a TAP UDP configuration, and both machines are awake, but fail TLS negotiation. I am using the current Tunnelblick beta.
The relevant error from Tunnelblick reads:
2017-05-07 08:22:20 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
2017-05-07 08:22:20 TLS Error: TLS handshake failedOh well… There goes my Sunday. :-[
[/quote]Maybe your clients use outdated TLS version or the configuration of the server and clients differs.
-
Upgraded my main and backup pfsense under ESXi.
Quicker and smoother than previous times.Good job pfSense Team!
-
I award this update a solid E. E for Epic fail.
PCEngines APU2, applied update from webui -> fails to boot.
And here I am with all my serial cables at work. Awesome.
Is this one of the "new features"?
-
I award this update a solid E. E for Epic fail.
PCEngines APU2, applied update from webui -> fails to boot.
And here I am with all my serial cables at work. Awesome.
Is this one of the "new features"?
I award your update preparedness a solid F. F for fail.
Apparently without even knowing what the issue is you assign blame. Another F.
-
I award your update preparedness a solid F. F for fail.
Update preparedness == I have another router preconfigured.
Apparently without even knowing what the issue is you assign blame. Another F.
Considering that the only change involved here is an update via the webui, I have a fairly good idea as to what broke it…
Took a backup -> rebooted -> ran update -> boot fail.Sure, I'd love to see the console messages, but like I said I won't have a serial cable handy until tomorrow.
Given the almost total lack of disk access, it appears to be failing at the bootloader, or at the very start of the boot process.This thing is supposed to be a network appliance, needing to break out a console cable for a minor point-release is pretty sad...
-
It's not all bad news. Updated 3 APU1's over the last 3 days, without one issue.
Next on the list is a 4860 HA setup… -
My APU2C4 updated to 2.3.4 with no issues, not that this helps you much.
-
Without knowing what is on the console it's impossible to speculate as to cause. You could have a hardware failure that didn't present itself until reboot, in which case the update did nothing.
-
Locking this. If you encounter problems, please start new threads in appropriate areas of this forum.
