[Bug]: Server fails on files modified in 1970-01-01 #49627
Open
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
I just ran into nextcloud/desktop#4332 (closed as stale), but on Debian Linux (Version 3.7.3). To me it looks like a server error, at least that's what the client reports.
Files and directories with mtime on 1970-01-01:
$ LC_ALL=C stat misc
File: misc
Size: 160 Blocks: 0 IO Block: 4096 directory
Device: 0,41 Inode: 38735767 Links: 1
Access: (0755/drwxr-xr-x) Uid: ( 1000/ quazgar) Gid: ( 1000/ quazgar)
Access: 2024-12-03 14:14:48.272056555 +0100
Modify: 1970-01-01 00:00:00.000000000 +0100
Change: 2024-12-03 14:14:48.268056818 +0100
Birth: 2024-12-03 14:14:17.278073007 +0100
I get this error in the client:
Error transferring https://cloud...../misc - server replied: Not found
Steps to reproduce
- Create directory with mtime = 1970-01-01T00:00:00
- Try to sync with server.
Expected behavior
- It should sync.
Nextcloud Server version
29
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
I do not know details about the server, it is the one hosted by large German provider Hetzner: https://www.hetzner.com/storage/storage-share
Activity