Steps to reproduce
1.I don’t really know
2.Same as 1
3.Same as 2
Expected behaviour
I except OwnCloud Login page to load
Actual behaviour
Gives a 404 error.
Server configuration
Operating system:
Ubuntu 16.04
Web server:
NGINX
Database:
PostgreSQL
PHP version:
7.2
ownCloud version: (see ownCloud admin page)
10.5
Updated from an older ownCloud or fresh install:
Nope
Where did you install ownCloud from:
The ZIP file at website
Signing status (ownCloud 9.0 and above):
I don’t know what this is supposed to mean.
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:
<?php $CONFIG = array ( 'instanceid' => 'REDACTED', 'passwordsalt' => 'REDACTED', 'secret' => 'REDACTED', 'trusted_domains' => array ( 0 => 'bobelifx.pro', ), 'datadirectory' => '/var/www/bobelifx.pro/html/cloud/data', 'overwrite.cli.url' => 'https://bobelifx.pro/cloud', 'dbtype' => 'pgsql', 'version' => '10.5.0.10', 'dbname' => 'REDACTED due to privacy', 'dbhost' => 'localhost', 'dbtableprefix' => 'oc_', 'dbuser' => 'REDACTED', 'dbpassword' => 'REDACTED', 'logtimezone' => 'UTC', 'apps_paths' => array ( 0 => array ( 'path' => '/var/www/bobelifx.pro/html/cloud/apps', 'url' => '/apps', 'writable' => false, ), 1 => array ( 'path' => '/var/www/bobelifx.pro/html/cloud/apps-external', 'url' => '/apps-external', 'writable' => true, ), ), 'installed' => true, ); ``` 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. ``` I cant access it at all. **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: Failed to load resource: the server responded with a status of 404 (Not Found) ``` I don't know whats the issue, I would be happy to pay anyone 50 cents in BTC if they give me a fix. My nginx config is ## # You should look at the following URL's in order to grasp a solid understanding # of Nginx configuration files in order to fully unleash the power of Nginx. # http://wiki.nginx.org/Pitfalls # http://wiki.nginx.org/QuickStart # http://wiki.nginx.org/Configuration # # Generally, you will want to move this file somewhere, and start with a clean # file but keep this around for reference. Or just disable in sites-enabled. # # Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples. ## # Default server configuration # server { # SSL configuration # # listen 443 ssl default_server; # listen [::]:443 ssl default_server; # # Note: You should disable gzip for SSL traffic. # See: https://bugs.debian.org/773332 # # Read up on ssl_ciphers to ensure a secure configuration. # See: https://bugs.debian.org/765782 # # Self signed certs generated by the ssl-cert package # Don't use them in a production server! # # include snippets/snakeoil.conf; root /var/www/bobelifx.pro/html; # Add index.php to the list if you are using PHP index index.html index.php index.htm index.nginx-debian.html *.php; server_name bobelifx.pro www.bobelifx.pro; location / { # First attempt to serve request as file, then # as directory, then fall back to displaying a 404. try_files $uri $uri/ /index.php$is_args$args; } fastcgi_split_path_info ^(.+\.php)(/.*)$; # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000 # location ~ \.php$ { include snippets/fastcgi-php.conf; # # # With php7.0-cgi alone: # fastcgi_pass 127.0.0.1:9000; # # With php7.0-fpm: fastcgi_pass unix:/run/php/php7.2-fpm.sock; } # deny access to .htaccess files, if Apache's document root # concurs with nginx's one # location ~ /\.ht { deny all; } location /ws/ { proxy_pass https://127.0.0.1:8080/; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto https; proxy_redirect off; } listen [::]:443 ssl ipv6only=on; # managed by Certbot listen 443 ssl; # managed by Certbot ssl_certificate /etc/letsencrypt/live/staff.bobelifx.pro/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/staff.bobelifx.pro/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } # Virtual Host configuration for example.com # # You can move that to a different file under sites-available/ and symlink that # to sites-enabled/ to enable it. # #server { # listen 80; # listen [::]:80; # # server_name example.com; # # root /var/www/example.com; # index index.html; # # location / { # try_files $uri $uri/ =404; # } #} server { if ($host = www.bobelifx.pro) { return 301 https://$host$request_uri; } # managed by Certbot if ($host = bobelifx.pro) { return 301 https://$host$request_uri; } # managed by Certbot listen 80 default_server; listen [::]:80 default_server; server_name bobelifx.pro www.bobelifx.pro; return 404; # managed by Certbot } If it's a nginx issue, give me this config with the issues fixed.