Nextcloud 33 Docker - Serverinfo bug: getTime not a function

ℹ️ Support
,
1
Bug Description:After upgrading to Nextcloud 33 (official Docker image), the Server Info app (v5.0.0) completely crashes when loading the hard drives section.

Every disk shows this JavaScript error:
Unexpected error: (intermediate value).getTime is not a function

The frontend JavaScript is trying to call .getTime() on an unformatted string or null value returned by the disk check.

Environment:

  • Nextcloud: 33 (Docker)
  • App: Server Info 5.0.0
  • DB / Cache: MariaDB 10.11 / Redis
  • Temporary Fix: Running php occ app:disable serverinfo stops the crash.

e you’ve seen this error? (Yes / No):

    • replace me
  • When did this problem seem to first start?
    • replace me
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • replace me
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • replace me

Summary of the issue you are facing:

[…]

Steps to replicate it (hint: details matter!):

Log entries

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

PASTE HERE

Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

PASTE

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

PASTE HERE

Apps

The output of occ app:list (if possible).

Tips for increasing the likelihood of a response

  • Use the preformatted text formatting option in the editor for all log entries and configuration output.
  • If screenshots are useful, feel free to include them.
    • If possible, also include key error output in text form so it can be searched for.
  • Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.