Customizable or get more Details from Internal Server Error Messages?

Hi everyone,

from time to time i get “internal server errors” displayed, so in general this seems to be an HTTP response of 500 ~ . Let me show you an example how this looks like.

Only information we can get here is the requesting remote adress and an access key string, but no details why or what happend, not even which module was causing this.

Once logged in to the admin account and checking the protocolls it gets a bit more clear.

I have also checked the error log via ssh but this is quite similar.

[index] Error: OCP\Files\NotFoundException: at <<closure>>

0. /var/www/ line 141
1. /var/www/ line 166
2. /var/www/ line 99
OC\AppFramework\Http\Dispatcher->executeController(OCA\Files\Controller\ViewController {}, "showFile")
3. /var/www/ line 126
OC\AppFramework\Http\Dispatcher->dispatch(OCA\Files\Controller\ViewController {}, "showFile")
4. /var/www/ line 47
ViewController", "showFile", OC\AppFramework\ ... {}, {fileid: "3992", ... "})
5. <<closure>>
OC\AppFramework\Routing\RouteActionHandler->__invoke({fileid: "3992", ... "})
6. /var/www/ line 297
undefinedundefinedcall_user_func(OC\AppFramework\ ... {}, {fileid: "3992", ... "})
7. /var/www/ line 975
8. /var/www/ line 42

GET /index.php/f/3992
at 2020-07-21T05:39:35+00:00

So question is:

  • Is it possible to customize those Internal Server Errors?
  • Or is it possible to enable more details to be shown on a non admin access?
  • Or is it possible to display the stacktrace or parts of it on the error page?

These are the details of my environment:

Nextcloud version ( 16.0.3):
Operating system and version ( Debian 10 ):
Apache or nginx version ( Apache 2.4.38 ):
PHP version ( 7.3.14 ):

The issue i am facing is not happening the first time. Steps to replicate it: (For this single example, there are more cases i am not able to reproduce so far)

  1. create file
  2. share file and sent link to someone
  3. delete file

Any help or idea is much appreciated, many thanks in advance.

Best regards

The Problem still exists.
How are you guys handling this? Just click the error away and search in the logs or have you implemented / adjusted something?

Any help is appreciated. Many thanks

last push, is anyone having an idea for me?

many thanks