-
-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error on Updating on Netgate 4200 24.11 from v2.3.0 to v2.3.1 #633
Comments
This is normal for a period of time after you initiate the update in the UI and should resolve on its own once the update completes. The update process runs in the background and part of that process is removing the previously installed package, which will temporarily remove some of the files the REST API forms need to render which will throw an error if you try to access the page in this state. There's not a great way to prevent that entirely, but some changes could be made to hopefully shorten that window and make it more apparent that the behavior is normal for a short period of time after starting an update. |
Before, access REST API resources resulted in a PHP error traceback which could cause unnecessary concern. This change will allow both endpoints and forms to give a friendlier, more informative notice.
* style: run prettier on changed files * docs: add info about unavailability during updates #633 * fix: give friendlier error messages during updates #633 Before, access REST API resources resulted in a PHP error traceback which could cause unnecessary concern. This change will allow both endpoints and forms to give a friendlier, more informative notice. * fix: correctly set http response code for 503s during updates
Describe the bug
Updating from v2.3.0 to v2.3.1 resulted in the following error, after the update:
Despite the error, it updated fine.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No error after the update.
Screenshots or Response
See the error above.
pfSense Version & Package Version:
Affected Endpoints:
n/a
Additional context
n/a
The text was updated successfully, but these errors were encountered: