Steps to reproduce
- Install docker image for owncloud:10.5 with Docker Compose (and docker-compose.yml & .env files as presented in the official documentation
- Launch with docker-compose up -d
- Owncloud runs fine over http
- Try to configure the system in the container for SSL
- Log into the container with docker exec -ti XXXX bin/bash
- Try to stop, restart apache2
Expected behaviour
apache2 stops or restarts
Actual behaviour
Get following error:
root@xxxx: /etc/apache2/ # service apache2 stop
/etc/init.d/apache2: 46: .: Can’t open /etc/apache2/envvars
/etc/init.d/apache2: 57: .: Can’t open /etc/apache2/envvars
ERROR: APACHE_PID_FILE needs to be defined in /etc/apache2/envvars
When checking, there is no ennvars file in /etc/init.d/apache2
Server configuration
Operating system: official owncloud:10.5 container image
Web server:
Database:
PHP version:
**ownCloud version:1.5 (see ownCloud admin page)
**Updated from an older ownCloud or fresh install: fresh
Where did you install ownCloud from:
Signing status (ownCloud 9.0 and above):
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
set -eo pipefail
[[ "${DEBUG}" == "true" ]] && set -x
if [[ -z "${OWNCLOUD_ENTRYPOINT_INITIALIZED}" ]]
then
for FILE in $(find /etc/entrypoint.d -iname \*.sh | sort)
do
source ${FILE}
done
fi
if [[ "$(id -u)" == "0" ]]
then
su-exec www-data php /var/www/owncloud/occ "${@}"
else
php /var/www/owncloud/occ "${@}"
fi
*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 here
ownCloud log (data/owncloud.log)
Insert your ownCloud log here
Browser log
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...