10.0.0.6
Steps to reproduce
- initiated owncloud update 10.0.0.4 to 10.0.0.6
2.
3.
Expected behaviour
Tell us what should happen
plain n simple update and occ upgrade
restarted apache service
continue as normal
Actual behaviour
Tell us what happens instead
what I would've expected to happen when 10.0.0.5 update critical bug was released.
which this owncloud instance of mine halted the update till 10.0.0.6.
update procedure was smooth sailing.
occ upgrade produced an error for php-intl.
so installed the module.
occ upgrade continued, all to the end.
restart web service.
reload oc webui login page, now now login.
error state of missing module intl
its installed but not seeing it.
restarted web server plenty time. no avail.
so I reinstalled the intl module.
till I did something stupid which I regret. and removed mysql instead of php-mysql.
I installed it back on immediately.
but client app cannot connect unknown error.
it was 503 service unavailable.
small steps im getting there.
removed php5.6.
7.0 is installed.
now webui gives me a text page.
about php5.6 or higher....?
Server configuration
Operating system:
debian 9
Web server:
apache 2
Database:
mysql/mariadb
PHP version:
php7.0
ownCloud version: (see ownCloud admin page)
10.0.0.6
Updated from an older ownCloud or fresh install:
10.0.0.4
Where did you install ownCloud from:
owncloud package repository
Signing status (ownCloud 9.0 and above):
na
Login as admin user into your ownCloud and access
http://example.com/index.php/settings/integrity/failed
paste the results into https://gist.github.com/ and puth the link here.The content of config/config.php:
Log in to the web-UI with an administrator account and click on
'admin' -> 'Generate Config Report' -> 'Download ownCloud config report'
This report includes the config.php settings, the list of activated apps
and other details in a well sanitized form.
or
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
*ATTENTION:* Do not post your config.php file in public as is. Please use one of the above
methods whenever possible. Both, the generated reports from the web-ui and from occ config:list
consistently remove sensitive data. You still may want to review the report before sending.
If done manually then it is critical for your own privacy to dilligently
remove *all* host names, passwords, usernames, salts and other credentials before posting.
You should assume that attackers find such information and will use them against your systems.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.Are you using external storage, if yes which one: local/smb/sftp/...
Are you using encryption: yes/no
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
LDAP configuration (delete this part if not used)
With access to your command line run e.g.:
sudo -u www-data php occ ldap:show-config
from within your ownCloud installation folder
Without access to your command line download the data/owncloud.db to your local
computer or access your SQL server remotely and run the select query:
SELECT * FROM `oc_appconfig` WHERE `appid` = 'user_ldap';
Eventually replace sensitive data as the name/IP-address of your LDAP server or groups.Client configuration
Browser:
Operating system:
Logs
Web server error log
Insert your webserver log hereownCloud log (data/owncloud.log)
Insert your ownCloud log hereBrowser log
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...