Settings tab not working (server side error)


#1

Steps to reproduce

1.
2.
3.

Expected behaviour

When click on "settings" the account (and server) settings page should be shown

Actual behaviour

Browser tell me that the server could not handle the request.

Server configuration

Operating system:
Ubuntu14

Web server:
Apache2

Database:
MySql

PHP version:
7.0

ownCloud version: (see ownCloud admin page)
10.0.2

Updated from an older ownCloud or fresh install:
Fresh install, but database and files are copied from the previus instalation

Where did you install ownCloud from:
Official page ( https://owncloud.org/install/# )

Signing status (ownCloud 9.0 and above):
"No errors found"

The content of config/config.php:
<?php
$CONFIG = array (
'instanceid' => 'ocryfvvdrihv',
'passwordsalt' => 'mysalt',
'secret' => 'mysecret',
'trusted_domains' =>
array (
0 => 'user.aljaxus.eu',
),
'datadirectory' => '/var/www/aljaxus/user/data',
'overwrite.cli.url' => 'https://user.aljaxus.eu',
'dbtype' => 'mysql',
'version' => '10.0.2.1',
'dbname' => 'mydatabase',
'dbhost' => 'localhost:3306',
'dbtableprefix' => 'oc_',
'dbuser' => 'myuser,
'dbpassword' => 'mypassword',
'logtimezone' => 'UTC',
'installed' => true,
'ldapIgnoreNamingRules' => false,
);

If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your ownCloud installation folder

https://pastebin.com/bMKK8X3A

List of activated apps:

If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your ownCloud installation folder.

https://pastebin.com/dswgs3pM

Are you using encryption: yes/no
Yes

Client configuration

Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 OPR/45.0.2552.888

Operating system:
Windows10

Logs

Web server error log

https://pastebin.com/Pf0u7y8R

ownCloud log (data/owncloud.log)

https://pastebin.com/11prYwJ5

Browser log

Can't find anything


#2

So the issue was caused by an addon "GpxEdit"

lp.


#3

Have you reported this issue to the app developer of that app? I think that would make sense if this app is causing such issues.