Nextcloud Instance just dies after Uploading a file via Android App

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 31.0.7
  • Operating system and version (e.g., Ubuntu 24.04):
    • Linux 4.18.0-477.13.1.lve.el7h.x86_64 x86_64
  • Web server and version (e.g, Apache 2.4.25):
    • /
  • PHP version (e.g, 8.3):
    • 8.3.25
  • Is this the first time you’ve seen this error? (Yes / No):
    • Yes
  • When did this problem seem to first start?
    • This week
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • Custom
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • Cloudflare

Summary of the issue you are facing:

When Uploading a file via the Android Nextcloud App, my Nextcloud instance literally just dies.

Android App Version is 3.33.0

Uploading a file via Web does not crash the instance.

I only uploaded .pdf files as of now, the automated backup from my phone does not crash the instance however, only if I manually upload a file from the app.

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

  1. Open Android App

  2. Manually upload a file to a folder/subfolder (.pdf)

  3. Loading error while refreshing

  4. File can be seen

  5. App prompt upload again

  6. No internet connection message

  7. Check url via Browser → Error 503

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.

https://pastebin.com/J5XCB7ds

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.

/

Web server / Reverse Proxy

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

No access, will ask Hoster

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!):

https://pastebin.com/JVj57Qnu

Apps

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

  • activity: 4.0.0
  • admin audit: 1.21.0
  • announcementcenter: 7.2.1
  • app_api: 5.0.2
  • bruteforcesettings: 4.0.0
  • cfg share links: 7.0.1
  • checksum: 1.2.6
  • circles: 31.0.0
  • cloud federation api: 1.14.0
  • comments: 1.21.0
  • contacts: 7.3.0
  • contactsinteraction: 1.12.0
  • dashboard: 7.11.0
  • dav: 1.33.0
  • epubviewer: 1.8.0
  • externalpassword: 1.1.2
  • federatedfilesharing: 1.21.0
  • federation: 1.21.0
  • files: 2.3.1
  • files archive: 1.2.7
  • files downloadactivity: 1.18.1
  • files downloadlimit: 4.0.0
  • files pdfviewer: 4.0.0
  • files reminders: 1.4.0
  • files sharing: 1.23.1
  • files trashbin: 1.21.0
  • files versions: 1.24.0
  • firstrunwizard: 4.0.0
  • logreader: 4.0.0
  • lookup server_connector: 1.19.0
  • metadata: 0.22.0
  • nextcloud announcements: 3.0.0
  • notifications: 4.0.0
  • oauth2: 1.19.1
  • password _policy: 3.0.0
  • photos: 4.0.0
  • privacy: 3.0.0
  • profile: 1.0.0
  • provisioning_api: 1.21.0
  • recommendations: 4.0.0
  • related resources: 2.0.0
  • richdocuments: 8.7.4
  • support: 3.0.0
  • survey_client: 3.0.0
  • systemtags: 1.21.1
  • text: 5.0.0
  • richdocumentscode: 25.4.403
  • serverinfo: 3.0.0
  • settings: 1.14.0
  • sharebymail: 1.21.0
  • webhook listeners: 1.2.0
  • workflowengine: 2.13.0
  • files antivirus: 6.0.4 (installed 6.0.4)
  • files_external: 1.23.0
  • files rightclick: 0.15.1 (installed 0.15.1)
  • hsts: 0.9.0 (installed 0.9.0)
  • richdocumentscode arm64: 25.4.403
  • suspicious_login: 9.0.1
  • twofactor nextcloud notification: 5.0.0
  • twofactor_totp: 13.0.0-dev.0
  • user ldap: 1.22.0
  • theming: 2.6.1
  • twofactor_backupcodes: 1.20.0
  • updatenotification: 1.21.0
  • user status: 1.11.0
  • viewer: 4.0.0
  • weather status: 1.11.0

Disabled:

  • backup: 1.4.0 (installed 1.4.0)
  • breezedark: 29.0.0 (installed 29.0.0)
  • encryption: 2.19.0
  • external: 6.0.2 (installed 6.0.2)

Much of your log indicates you have this configured to use a richdocumentscode installation (Nextcloud Office + Built-in CODE), but it may be having problems.

You also have some apps force enabled, which disables compatibility checks, and some are not compatible (e.g. files_rightclick).

Lastly, can you elaborate what you mean specifically by crashes? Have you checked your OS kernel logs? May just me a out of memory situation or similar. I see you’re running a lot of things besides Office, including the antivirus scanner. Those can be resource intensive + file type specific.

I disabled Built-in CODE as of now as well as Antivirus for files was disabled previously.

”Right click”, I guess this should be it is also disabled, I guess deletion is better than deactivation?

With crashes I mean it as described. The Webserver seems to go down and does respond after a couple of minutes again. So it pretty much looks like to me, that the whole nginx/apache2 service crashes.
Unfortunately, I do use a Webserver/Webhost, therefore I cannot act as the instance would’ve been on a client/server itself.

I do know, that the base is nginx. I can also execute ssh commands.

With that symptom you will want to ask your manager hosting provider. The things to check require root privileges for the most part.