mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 16:35:53 +02:00
[GH-ISSUE #1651] RangeError: date value is not finite in DateTimeFormat.format() #1152
Labels
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#1152
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Pulsar7 on GitHub (Mar 12, 2026).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1651
🐞 Describe the bug
When trying to access the
/account-path via the Web UI, the error page 'Oh no, ntfy crashed' is displayed.Those feature-flags are set in the
server.yaml-configuration:💻 Components impacted
ntfy-server or/and web-app
I'm not sure, if it's a specific Browser-related Problem, since I've only tested it with Firefox (Version 148.0 (64-bit) - Snap) and Brave (Brave 1.88.127 (Official Build) (64-bit)).
💡 Screenshots and/or logs
Strack-Trace from the Firefox-Browser, when trying to access
/account:Strack-Trace from the Brave-Browser, when trying to access
/account:🔮 Additional context
At the Brave-Browser I think I was able to identify the Problem at
utils.js:which gets called by
Account.jsx:I don't know if this StackOverflow-Post is related to this issue and I'm not a
React-Programmer, but this seems to me, that this might be helpful: https://stackoverflow.com/questions/63958875/why-do-i-get-rangeerror-date-value-is-not-finite-in-datetimeformat-format-w@MrPostie commented on GitHub (Mar 18, 2026):
Just installed ntfy in a docker container, got the same error.
@krzaktak commented on GitHub (Mar 20, 2026):
I have the same problem. But I investigated it, and my problem is related to token pre-provisioned in Docker Compose. The date of this token is "01 Jan 70 00:00 UTC (server config)". And when I removed this token from Docker Compose, the problem disappeared.
@zanetdev commented on GitHub (Mar 21, 2026):
It is related to the last access time.
Temporary fix is to make use of the token to publish a message which will set that date to a valid value
eg add this life cycle hook section to your docker compose where the service is named ntfy
@binwiederhier commented on GitHub (Apr 13, 2026):
Thanks for the workaround @zanetdev !