It's the same installer whether you do it from memstick or ISO. There isn't an upgrade ISO vs. a new install one. Definitely want to use 64 bit.

@tgharold:

Not 100% true.

It is true for valid configs. Your <ipaddrv6>FE80</ipaddrv6> isn't valid, that's not link local, it's a string that isn't a valid IP. Not permitted by the GUI and never has been at least in release versions. That was either manually edited into the config, or around from an early pre-2.1.0 beta version before all the proper input validation was in place.

Packages that no longer exist can be edited out, but that's not strictly necessary. The worst you end up with there is log spam when restoring to a clean install. In 2.3.1, those are automatically uninstalled pre-upgrade, then those that still exist are reinstalled post-upgrade. If restored to a clean 2.3.0+ version, it'll just log that it can't reinstall packages that are missing. If they had cron entries in the config, those may need manual removal.

@tgharold:

The workaround is to change those <ipaddrv6>FE80</ipaddrv6> to just <ipaddrv6>without the FE80 portion and then restore the configuration file.</ipaddrv6>

only way that happened is if you manually edited that into the config to begin with. That's not a valid IPv6 address, and the GUI's input validation won't accept that.

you can try
https://forum.pfsense.org/index.php?topic=105399.msg588219#msg588219
https://forum.pfsense.org/index.php?topic=105399.msg588787#msg588787

At the console, get to the shell (option 8) and

Then you should get better response from the webGUI.
Disable the dashboard automatic update checks.
Diag->nanoBSD set the system to permanent RW.

Then (if convenient) reboot and check that it comes back RW and the dashboard/webGUI feels happier.

You decompressed then hashed. The published hash is on the .iso.gz file.

@jim0266:

Running ALIX 2.3 with the same symptoms as Gloomrider. I cannot even get to the System>Update page. After about 3 minutes the page times out with a 504 Gateway Time-out.

Diag>NanoBSD, switch to permanent rw.

Are you entering the keystrokes through the serial console? Or are you trying to use a physical keyboard?

When using a serial console image, input would come from the serial terminal PC and not from a keyboard attached to the target device.

Just run a backup from your physical box (Diagnostics\Backup/Restore), edit the config file to allow for the possibly different NIC device IDs and import into a fresh install on your VM environment. So yeah, it's an OK idea.

The stack trace is entirely unhelpful! But maybe you are hitting a divide-by-zero problem that is fixed by:
https://github.com/pfsense/pfsense/commit/883777874d3064fc9730a0d7e870bf0bc991ae0c
and
https://github.com/pfsense/pfsense/commit/6f069e921c0a2aabe66ee069c20148b4fcbb0918

Try putting the latest status_queues.php on your system. Or even update to 2.3.1-DEVELOPMENT to get all the good stuff that has been fixed since 2.3-RELEASE.

Hi again! :-)

I enabled a tunnel, but the connection did not come up, although the other side is online, too… Dunno why the tunnel does not connect, was functional in 2.1.x, but disabled since then.

On the 2.2.6 pFsense I have in the log:
charon: 08[IKE] <con2000|1>sending retransmit 5 of request message ID 0, seq 3

Debugging IPsec is no fun….

What is this widget-thing? I didn't install anything!</con2000|1>

And you should be able to use the auto-update from the dashboard - it will find the correct "factory" upgrade image for it and do its thing automagically.

Thanks a lot.  8)

Deleting the following files and then reinstalling haproxy-devel worked for me:

/usr/local/pkg/haproxy.inc

/usr/local/pkg/haproxy_htmllist.inc

/usr/local/pkg/haproxy_rules.inc

/usr/local/pkg/haproxy_socketinfo.inc

/usr/local/pkg/haproxy_upgrade_config.inc

/usr/local/pkg/haproxy_utils.inc

/usr/local/pkg/haproxy_xmlrpcsyncclient.inc

/usr/local/pkg/pkg_haproxy_tabs.inc

I left the following files intact:

/usr/local/pkg/haproxy.xml

/usr/local/pkg/haproxy_rules.inc

A reinstall worked, I also decided its time to retire my aging fit-pc and ordered an SG-2440.

Actually the hardware was purchased in 2008.

I've considered upgrading several times (e.g. to 5.0 and 5.5) but decided not to due to performance of the migration utility (VMware Converter). For 5.x it's much slower compared to 4.x.

And also, we still use Windows XP, where newer versions of the host control utility (VMware vSphere client) doesn't seem to run smoothly.