-
Notifications
You must be signed in to change notification settings - Fork 27
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
RangeError: Model is only valid from Tue Dec 10 2019 to Tue Dec 10 2024 #110
Comments
This is already fixed in the unms-images which are used to build this image (see dockerfile). Or just use my image until @Nico640 recreted his image |
Here the same issue after a reboot of mij docker VM. |
Wow... apparently a npm package that UISP uses has a fixed expiration date set to Dec 10 2024, after which it'll take the whole app down. |
@Nico640 what a strange thing to have hardcoded but I'm glad you found the issue! I hear that Ubiquiti has released a hotfix for 2.4.155 - I'm assuming you will rebuild your image for this version? Any chance you can let me know if you rebuild your 1.7.5 image to circumvent this issue as well, as I haven't quite made my upgrade path up to the latest as yet. Cheers |
Fixed in the @rtucker666 for 1.7.5, try executing this inside the UISP container and waiting a few mins for it to come back up:
|
Hi Nico640, This works perfectly, you are officially my saviour. Is this fix persistant, or will I have to remember to execute this line of code if the container is restarted? Thanks so much |
works also for me after a re-create! good job! |
Thank you @aleex1848 and @Nico640 for the quick solution and fix. I did initially try pulling a new image but no luck. Gotta love node packages sometimes... |
Should persist between container restarts, as long as the container doesn't get deleted and recreated. |
Please see the issue from the latest UISP release. Causes loop and no load in docker container.
https://community.ui.com/questions/UISP-v2-4-143-and-v2-4-155-UISP-Fails-to-start-Geomagnetism-date-comparison-BUG/0cb32012-9afb-41d4-9f37-6a9ba94c4c36
The text was updated successfully, but these errors were encountered: