I updated 2.4 beta from the gui yesterday and ended up with 2.4.1 development. When the update is set to stable, it says the system is up to date. When the update is set to development, there are repository errors. These issues were reported but the thread was locked. As a result, there are two new threads relating to the same problem.

There seems to be a disconnect and locking a thread about the specific problem is the exact opposite of a useful response. Some people, myself included, did a routine update which was prompted by the pfsense gui. Others saw the link for pfsense 2.4.0 RC and installed it. If pfsense is offering the update and a link is provided, with all due respect, how are we supposed to know the repository was not ready? Irrespective of whether it was ready or not, the update has been installed by a number of people and pfsense says 2.4.1 development, not 2.4.0 RC. How do we get to 2.4.0 RC?

If a firewall upgraded to 2.4.1, it must not have been set to follow the correct line of updates. On System > Update, Update Settings tab, "Development Snapshots (experimental)" had to be chosen which means it will track master and will skip releases. The "Stable (Default)" choice there will track snapshots as well but it will move to RC, then Release, and then later will track point releases and security/errata (a.k.a. "Stable" updates).

At the moment, the two branches are practically identical, so it is safe to switch back without a reinstall. To get back to 2.4.0-RC after accidentally upgrading to 2.4.1:

* Navigate to System > Update, Update Settings tab* Select Stable there, and click Save (even if no changes were made)* Open a root/admin shell via ssh or the console and issue the following commands: