You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
System Time
Local time: Wed 2024-08-28 20:39:55 EDT
Universal time: Thu 2024-08-29 00:39:55 UTC
RTC time: Thu 2024-08-29 00:39:55
Time zone: America/New_York (EDT, -0400)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
I am running a Zimaboard, which I bought in December 2023. I noticed this error after updating to 0.4.11, though I may not have noticed it before and it could have been introduced with a previous update.
The text was updated successfully, but these errors were encountered:
I read somewhere that not having the wrong timezone is an issue connected to this problem. Seemed unlikely, since I didn't change the timezone when receiving the Zimaboard and didn't have this problem. Also, while I don't understand the logfiles posted above, they seem to indicate a different problem.
Even so, I changed to the correct timezone (Asia/Bangkok), rebooted the Zimaboard and as expected it did not fix the issue. However the nature of the logfiles does seem to have changed:
Describe the bug
When I click on the CasaOS Appstore, I get a sceen with the error message:
There was an error loading the data. Please try again.
Screenshot
Expected behavior
I'd expect to see the App Store
System Information
System Time
Local time: Wed 2024-08-28 20:39:55 EDT
Universal time: Thu 2024-08-29 00:39:55 UTC
RTC time: Thu 2024-08-29 00:39:55
Time zone: America/New_York (EDT, -0400)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
Logs
sudo journalctl -xeu casaos-app-management --no-pager > output.txt
output.txt
Additional context
I am running a Zimaboard, which I bought in December 2023. I noticed this error after updating to 0.4.11, though I may not have noticed it before and it could have been introduced with a previous update.
The text was updated successfully, but these errors were encountered: