Describe the Bug
I've been deploying the Openhamclock via Portainer as a stack so that it is always up-to-date locally. However, after recent updates, an error pops up: "OpenHamClock hit an error. Something went wrong rendering the dashboard. This usually fixes itself after a reload. If it keeps happening, try clearing your browser cache." It happens with and without the callsign and locator being set properly.
Error details
RangeError: invalid time zone: Etc/Unknown
hw@https://openhamclock.mydomain.com/assets/index-tx2xjj17.js:1265:110
Dg@https://openhamclock.mydomain.com/assets/index-tx2xjj17.js:17:10993
mw@https://openhamclock.mydomain.com/assets/index-tx2xjj17.js:1265:12053
To Reproduce
Steps to reproduce the behavior:
- Deploy Openhamclock from https://github.com/accius/openhamclock.git via Portainer (Stack)
- Clear your browser cache and and try to load it.
Expected Behavior
Even without setting the variables callsign and locator, I'd expect to be able to load it without issues.
Environment
- OS: OMV - 7.7.24-7 (Sandworm)
- Browser: Firefox 149.0.2
- OpenHamClock Version: [26.1.3]
- Running As: [Docker/Portainer stack]
73!
Describe the Bug
I've been deploying the Openhamclock via Portainer as a stack so that it is always up-to-date locally. However, after recent updates, an error pops up: "OpenHamClock hit an error. Something went wrong rendering the dashboard. This usually fixes itself after a reload. If it keeps happening, try clearing your browser cache." It happens with and without the callsign and locator being set properly.
To Reproduce
Steps to reproduce the behavior:
Expected Behavior
Even without setting the variables callsign and locator, I'd expect to be able to load it without issues.
Environment
73!