Can't upload file less 5Mb via desktop client

[TristisOris]

fread(): file created in the system's temporary directory at /var/www/html/apps/files_external/3rdparty/icewind/streams/src/Wrapper.php#54

More 5Mb upload works fine. Web upload also fine.
sys_temp_dir and tempdirectory specified.

[vawaver]

Hello,

To help you effectively troubleshoot this issue, it would be great if you could provide more details about your setup. Specifically, consider including the following information:

1. Operating System: What OS and version is the server running (e.g., Ubuntu 22.04, Debian 12)?
2. Nextcloud Version: Which version of Nextcloud are you using?
3. Nextcloud Client Version: If applicable, include the version of the Nextcloud desktop or mobile client you are using.
4. PHP Version: Which version of PHP is installed on your server?
5. Configuration Details:
   • The current value of sys_temp_dir and tempdirectory settings in your configuration.
   • Any additional changes you made to the PHP or Nextcloud configuration related to temporary file handling.
6. Logs: Are there any related logs (Nextcloud, Apache/Nginx, PHP error logs) besides the one mentioned? These could provide more clues.
7. Storage Backend: Are you using any external storage or object storage? If yes, which one, and how is it configured?
8. Upload Context: Does the error occur with a specific type of file or under certain conditions (e.g., size, file type)?
9. Extensions and Apps: Are you using any third-party apps that could be interfering?

These details will give us a clearer picture of your environment and help pinpoint the root cause of the issue. Let us know!

[TristisOris]

1. ubuntu 24, docker
2. [Nextcloud Hub 9] (30.0.2)
3. desktop 3.14.3
4. php 8.2

sys_temp_dir and tempdirectory /var/upload_temp
also php upload_tmp_dir = /var/nextcloud_temp
6. no.
7. nfs as local path
8. any type of files
9. onlyoffice

[vawaver]

Based on the information you shared, here are some steps and recommendations to help diagnose and potentially resolve the syncing issue:

1. Nextcloud and PHP Temp Directories:

   • Your temp directories (/var/upload_temp and /var/nextcloud_temp) should be writable by the Nextcloud Docker container. Verify their permissions and ownership (www-data for UID/GID 33).
   • Ensure enough space is available in these directories, as insufficient space can cause issues with file handling during uploads or syncing.

2. PHP Configuration:

   • Confirm that post_max_size and upload_max_filesize in your PHP settings are set high enough for your users’ needs (e.g., post_max_size=2G and upload_max_filesize=2G).
   • Check if opcache.enable is set to 1 and opcache.interned_strings_buffer is adequately configured to handle your Nextcloud instance.

3. NFS as Local Path:

   • NFS mounts can sometimes cause delays or inconsistencies with file locking. Ensure your NFS setup supports locking (flock) and that oplocks are enabled.
   • Add the following lines to your config.php if not already present:

     'filesystem_check_changes' => 1,
     'memcache.local' => '\\OC\\Memcache\\APCu',
     

     This ensures changes in the NFS share are detected promptly, and caching improves performance.

4. Desktop Client:

   • The Nextcloud Desktop Client version 3.14.x has been reported to cause issues with syncing on some devices. I recommend downgrading to version 3.13.x and testing if the issue persists.
   • You can download older versions of the client here.
   • After downgrading, let us know if syncing works more reliably.

5. File Types and OnlyOffice:

   • Since the issue affects all file types and involves OnlyOffice, check the OnlyOffice logs for any relevant errors. Ensure your OnlyOffice service has sufficient resources and isn’t affecting Nextcloud’s file operations.

6. Log Analysis:

   • Look for errors in the Nextcloud logs (data/nextcloud.log) and Docker container logs (docker logs <nextcloud-container>).
   • If possible, increase logging verbosity temporarily to capture more details:

     'loglevel' => 0,
     

     in your config.php.

7. Advanced Proxy Configuration:

   • Double-check your NGINX proxy settings. Ensure the advanced settings I mentioned earlier are in place:

     client_body_buffer_size 512k;
     proxy_read_timeout 86400s;
     client_max_body_size 0;
     

     These settings can help prevent issues with large file syncing or timeouts.

8. Network Stability:

   • If the issue still persists, test the stability of your NFS network connection and the Docker network bridge. Any instability here can result in resyncing issues.

Let us know the results after trying the client downgrade. This could be a significant factor in resolving your issue.

[TristisOris]

solved. it was different path to temp folder at configs.