[Solved] Can't see owncloud interface

Hi everybody again,
here I am with some other newby’s issues.
I’m trying to install Owncloud, to try to create a NAS.
I followed the instructions posted here https://dietpi.com/docs/software/cloud/#owncloud and the software installation went good (using ssh).
After that, I tried to connect through the browser (using IP/owncloud), but it give me this error:

Not Found
The requested URL was not found on this server.

Apache/2.4.51 (Raspbian) Server at 192.168.1.15 Port 80

I’m not sure the is a sort of relation but, If I try to reach the pi through the browser it opens the Apache2 Debian Default Page.
Do you have any suggestions?
Thanks

getting the default Apache page while entering IP only, is totally fine. It shows the web server themselves is working fine.

can you share following

ls -la /var/www

Here the answer:

 root@DietPi:~# ls -la /var/www
total 136
drwxr-xr-x  4 root     root      4096 Dec  2 21:05 .
drwxr-xr-x 12 root     root      4096 Nov 19 21:16 ..
-rw-r--r--  1 root     root     38294 Dec  2 21:03 apc.php
drwxr-xr-x  2 root     root      4096 Dec  2 20:49 html
-rw-r--r--  1 root     root      3388 Nov 20 06:31 index.lighttpd.html
-rw-r--r--  1 root     root     71038 Dec  2 21:03 opcache.php
drwxr-xr-x 13 www-data www-data  4096 Dec  2 21:10 owncloud
-rw-r--r--  1 root     root        20 Dec  2 21:03 phpinfo.php
root@DietPi:~#

Is it ok?
Just another info: in this moment I’m connecting through ssh from outside the pi network, using a ddns domain Name (no-ip provider). I’m not sure this can affect the command you are suggesting

ok owncloud folder is available in web server root. Let’s have a look to owncloud folder

ls -la /var/www/owncloud/

Can you share Apache config as well

cat /etc/apache2/apache2.conf

IP 192.168.1.15 is the address of your DietPi device?
And opening http://192.168.1.15/owncloud in browser doesn’t work?

This is the first command

 root@DietPi:~# ls -la /var/www/owncloud/
total 532
drwxr-xr-x 13 www-data www-data   4096 Dec  2 21:10 .
drwxr-xr-x  4 root     root       4096 Dec  2 21:05 ..
-rw-r--r--  1 www-data www-data   3487 Dec  2 21:10 .htaccess
-rw-r--r--  1 www-data www-data    163 Jul 21 16:40 .user.ini
-rw-r--r--  1 www-data www-data   8859 Jul 21 16:40 AUTHORS
-rw-r--r--  1 www-data www-data 347443 Jul 21 16:40 CHANGELOG.md
-rw-r--r--  1 www-data www-data  34520 Jul 21 16:40 COPYING
-rw-r--r--  1 www-data www-data   2500 Jul 21 16:40 README.md
drwxrwxrwx 22 www-data www-data   4096 Jul 21 16:41 apps
drwxr-xr-x  2 www-data www-data   4096 Dec  2 21:08 apps-external
drwxrwxrwx  2 www-data www-data   4096 Dec  5 21:45 config
-rw-r--r--  1 www-data www-data   4618 Jul 21 16:40 console.php
drwxr-xr-x 16 www-data www-data   4096 Jul 21 16:41 core
-rw-r--r--  1 www-data www-data   1717 Jul 21 16:40 cron.php
-rw-r--r--  1 www-data www-data  31204 Jul 21 16:40 db_structure.xml
-rw-r--r--  1 www-data www-data    179 Jul 21 16:40 index.html
-rw-r--r--  1 www-data www-data   3518 Jul 21 16:40 index.php
drwxr-xr-x  6 www-data www-data   4096 Jul 21 16:40 lib
-rwxr-xr-x  1 www-data www-data    283 Jul 21 16:40 occ
drwxr-xr-x  2 www-data www-data   4096 Jul 21 16:40 ocm-provider
drwxr-xr-x  2 www-data www-data   4096 Jul 21 16:40 ocs
drwxr-xr-x  2 www-data www-data   4096 Jul 21 16:40 ocs-provider
-rw-r--r--  1 www-data www-data   3135 Jul 21 16:40 public.php
-rw-r--r--  1 www-data www-data   5618 Jul 21 16:40 remote.php
drwxr-xr-x  4 www-data www-data   4096 Jul 21 16:40 resources
-rw-r--r--  1 www-data www-data     26 Jul 21 16:40 robots.txt
drwxr-xr-x 12 www-data www-data   4096 Jul 21 16:40 settings
-rw-r--r--  1 www-data www-data   2231 Jul 21 16:40 status.php
drwxr-xr-x  6 www-data www-data   4096 Nov 14  2019 updater
-rw-r--r--  1 www-data www-data    280 Jul 21 16:40 version.php
root@DietPi:~#

And this is the second

 root@DietPi:~# cat /etc/apache2/apache2.conf
# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
#       /etc/apache2/
#       |-- apache2.conf
#       |       `--  ports.conf
#       |-- mods-enabled
#       |       |-- *.load
#       |       `-- *.conf
#       |-- conf-enabled
#       |       `-- *.conf
#       `-- sites-enabled
#               `-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
#   together by including all remaining configuration files when starting up the
#   web server.
#
# * ports.conf is always included from the main configuration file. It is
#   supposed to determine listening ports for incoming connections which can be
#   customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
#   directories contain particular configuration snippets which manage modules,
#   global configuration fragments, or virtual host configurations,
#   respectively.
#
#   They are activated by symlinking available configuration files from their
#   respective *-available/ counterparts. These should be managed by using our
#   helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
#   their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables, in
#   the default configuration, apache2 needs to be started/stopped with
#   /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
#   work with the default configuration.


# Global configuration
#

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
#Mutex file:${APACHE_LOCK_DIR} default

#
# The directory where shm and other runtime files will be stored.
#

DefaultRuntimeDir ${APACHE_RUN_DIR}

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5


# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel warn

# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf

# Include list of ports to listen on
Include ports.conf


# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.
<Directory />
        Options FollowSymLinks
        AllowOverride None
        Require all denied
</Directory>

<Directory /usr/share>
        AllowOverride None
        Require all granted
</Directory>

<Directory /var/www/>
        Options Indexes FollowSymLinks
        AllowOverride None
        Require all granted
</Directory>

#<Directory /srv/>
#       Options Indexes FollowSymLinks
#       AllowOverride None
#       Require all granted
#</Directory>




# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
        Require all denied
</FilesMatch>


#
# The following directives define some format nicknames for use with
# a CustomLog directive.
#
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
#
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
root@DietPi:~#

I confirm that 192.168.1.15 is my pi address and when I try to reach the owncloud from the browser nothing happens…

ok how did you install Apache? This is not the default DietPi configuration file we use

https://github.com/MichaIng/DietPi/blob/master/.conf/dps_83/apache2.conf

Honestly, I don’t remember to have installed it.
Could be that It has installed when I installed LLSP and/or LLMP?
Do you think the owncloud problem could be related to the wrong Apache configuration?
How can I fix this, then?

Let’s check what you have installed

dietpi-software list | grep " =2 "

here all my installation:

root@DietPi:~# dietpi-software list | grep " =2 "
ID 5 | =2 | ALSA: Advanced Linux Sound Architecture |
ID 6 | =2 | X.Org X Server: aka X11 - X Window System implementation |
ID 9 | =2 | Node.js: JavaScript runtime environment |
ID 16 | =2 | Build-Essential: GNU C/C++ compiler, development libraries and headers |
ID 23 | =2 | LXDE: ultra lightweight desktop | +ALSA +X.Org X Server +browser | https://dietpi.com/docs/software/desktop/#lxde
ID 47 | =2 | ownCloud: File sync, sharing and collaboration platform | +MariaDB +PHP +Redis +webserver | https://dietpi.com/docs/software/cloud/#owncloud
ID 67 | =2 | Firefox: web browser for desktop | +ALSA +X.Org X Server | https://dietpi.com/docs/software/desktop/#firefox
ID 69 | =2 | Python 3 RPi.GPIO: Control Raspberry Pi GPIO channels in Python 3 | | https://dietpi.com/docs/software/hardware_projects/#rpigpio
ID 77 | =2 | Grafana: platform for analytics and monitoring | | https://dietpi.com/docs/software/hardware_projects/#grafana
ID 81 | =2 | LLSP: Lighttpd | SQLite  | PHP | +Lighttpd +SQLite +PHP | https://dietpi.com/docs/software/webserver_stack/#llsp-web-stack
ID 82 | =2 | LLMP: Lighttpd | MariaDB | PHP | +Lighttpd +MariaDB +PHP | https://dietpi.com/docs/software/webserver_stack/#llmp-web-stack
ID 84 | =2 | Lighttpd: Extremely lightweight webserver | +PHP | https://dietpi.com/docs/software/webserver_stack/#lighttpd
ID 87 | =2 | SQLite: Persistent single-file database system | | https://dietpi.com/docs/software/databases/#sqlite
ID 88 | =2 | MariaDB: Persistent cached file-per-table database server | | https://dietpi.com/docs/software/databases/#mariadb
ID 89 | =2 | PHP: Hypertext Preprocessor for dynamic web content | | https://dietpi.com/docs/software/webserver_stack/#php
ID 91 | =2 | Redis: Volatile in-memory non-SQL database server | | https://dietpi.com/docs/software/databases/#redis
ID 96 | =2 | Samba Server: Feature-rich SMB/CIFS server | | https://dietpi.com/docs/software/file_servers/#samba
ID 103 | =2 | DietPi-RAMlog: Makes /var/log a RAM disk, preserves file structure on reboot | | https://dietpi.com/docs/software/log_system/#dietpi-ramlog
ID 104 | =2 | Dropbear: Lightweight SSH server | | https://dietpi.com/docs/software/ssh/#dropbear
ID 120 | =2 | RealVNC Server: desktop for remote connection | +desktop | https://dietpi.com/docs/software/remote_desktop/#realvnc-server
ID 122 | =2 | Node-RED: tool for wiring devices, APIs and online services | +Node.js +Build-Essential +Python 3 RPi.GPIO | https://dietpi.com/docs/software/hardware_projects/#node-red
root@DietPi:~#

You have 2 web server installed conflicting each other. Apache seems to be installed manually by yourself and Lighttpd which was installed by DietPi due to owncloud install. If not needed I would recommend to purge Apache.

Thanks Joulinar , as always precious :wink: .
How can I purge it without damaging something else?
Which is the right command?

to remove Apache

apt purge apache2

try to start Lighttpd now

systemctl restart lighttpd.service

Great Joulinar !!
Again problem solved.
Now I can see the owncloud web interface :muscle:

ok, hope there was no other application relying on Apache2. At least there was a reason to have it installed in past.

I’m really trying to learn with this pi. So I’m quite sure it was installed without a specific reason.
Thanks again