Nextcloud Bad Gateway

Zitat von ciaphas2037

I've been trying to follow KM0201's instructions on a Raspberry Pi 4 running Raspbian lite with OMV on top (and nothing else) and keep running into the same problem. I run the docker script in step 1, but when I check the logs after deploying the stack I get the following error message in my nextcloud container:

Exception: Not installed in /config/www/nextcloud/lib/base.php:282

Stack trace:

#0 /config/www/nextcloud/lib/base.php(663): OC::checkInstalled()

#1 /config/www/nextcloud/lib/base.php(1104): OC::init()

#2 /config/www/nextcloud/cron.php(43): require_once('/config/www/nex...')

My docker script is attached here:

Code

version: "2.1"
services:
  nextcloud:
    image: ghcr.io/linuxserver/nextcloud:latest
    container_name: nextcloud
    ##network_mode: swag_default
    environment:
      - UID=998
      - PGID=100
    volumes:
      - /srv/dev-disk-by-uuid-e711fbe1-bda4-43e9-85b6-051f9588ff89/nextcloud/config:/config
      - /srv/dev-disk-by-uuid-e711fbe1-bda4-43e9-85b6-051f9588ff89/nextcloud/data:/data
      - /etc/localtime:/etc/localtime:ro
    depends_on:
      - mariadb
    ports:
      - 450:443
    restart: unless-stopped
  mariadb:
    image: ghcr.io/linuxserver/mariadb:latest
    container_name: nextclouddb
    ##network_mode: swag_default
    environment:
      - UID=998
      - PGID=100
      - MYSQL_ROOT_PASSWORD=______________
    volumes:
      - /srv/dev-disk-by-uuid-e711fbe1-bda4-43e9-85b6-051f9588ff89/nextcloud/mariadb:/config
      - /etc/localtime:/etc/localtime:ro
    restart: unless-stopped

Alles anzeigen

When I go to lines 282 and 663 of /config/www/nextcloud/lib/base.php I find a function that I think is checking of whether something called 'systemConfig' is installed.

Code

        public static function checkInstalled(\OC\SystemConfig $systemConfig) {
                if (defined('OC_CONSOLE')) {
                        return;
                }
                // Redirect to installer if not installed
                if (!$systemConfig->getValue('installed', false) && OC::$SUBURI !== '/index.php' && OC::$SUBURI !== '/status.php') {
                        if (OC::$CLI) {
                                throw new Exception('Not installed');
                        } else {
                                $url = OC::$WEBROOT . '/index.php';
                                header('Location: ' . $url);
                        }
                        exit();
                }
        }

Alles anzeigen

I made sure I updated and upgraded all packages prior to install, is this something wrong with my compose script, something missing from the linuxserver image or something wrong with my machine (which I've re-installed from scratch twice with only OMV on).

Any help would be appreciated, search engines don't seem to be finding anyone else with this problem.

Alles anzeigen

You didn't follow anything I wrote, so... not sure why you brought me up there

What was the first sentence in that? Don't mix this with other tutorials... and what did you do, you mixed it with a dbtech tutorial

First, get a proper PUID/PGID, rather than using admin's

I suspect that error is because your paths are not right... under nextcloud. you have your config and data folders, both under "nextcloud". from previous experiences... Nextcloud puts some harsh permissions on that data folder... thus why my paths there are totally different..

Zitat von HannesJo

That worked at least on my test setup lately.

Its possible it does. I've helped several on Reddit however that was an issue, and simply adjusting those two folders fixed it.

I think part of it is, people go "root crazy", ssh in as root and start creating directories as root, etc. And it just causes problems. Usually just recommend letting the stack/compose file create the folders.

I haven't tested that theory in a while, but I've seen it and issue a few times.

Zitat von HannesJo

KM0201 No problemo. Just remembered that I did it some days ago and had no problems

ciaphas2037

I've just checked it. As I said this is expected behavior.

My test stack:

Code

---
version: "3.5"
services:
  nextcloud:
    image: lscr.io/linuxserver/nextcloud:latest
    container_name: nextcloud
    environment:
      - PUID=1002
      - PGID=1005
      - TZ=Europe/Berlin
    volumes:
      - ../../config/nextcloud/appdata:/config
      - ../../config/nextcloud/data:/data
    ports:
      - 2444:443
    depends_on:
      - nextcloudDB
    restart: unless-stopped

  nextcloudDB:
    image: linuxserver/mariadb:latest
    container_name: nextcloudDB
    environment:
      - PUID=1002
      - PGID=1005
      - TZ=Europe/Berlin
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
      - FILE__MYSQL_ROOT_PASSWORD=/run/secrets/db_root_password
      - FILE__MYSQL_PASSWORD=/run/secrets/db_password
    secrets:
      - db_root_password
      - db_password
    volumes:
      - ../../config/nextcloud/nextcloudDB:/config
    restart: unless-stopped

secrets:
  db_password:
    file: secrets/db_password.txt
  db_root_password:
    file: secrets/db_root_password.txt

Alles anzeigen

Container log:

Code

% docker-compose logs -f nextcloud
Attaching to nextcloud
nextcloud      | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
nextcloud      | [s6-init] ensuring user provided files have correct perms...exited 0.
nextcloud      | [fix-attrs.d] applying ownership & permissions fixes...
nextcloud      | [fix-attrs.d] done.
nextcloud      | [cont-init.d] executing container initialization scripts...
nextcloud      | [cont-init.d] 01-envfile: executing... 
nextcloud      | [cont-init.d] 01-envfile: exited 0.
nextcloud      | [cont-init.d] 02-tamper-check: executing... 
nextcloud      | [cont-init.d] 02-tamper-check: exited 0.
nextcloud      | [cont-init.d] 10-adduser: executing... 
nextcloud      | 
nextcloud      | -------------------------------------
nextcloud      |           _         ()
nextcloud      |          | |  ___   _    __
nextcloud      |          | | / __| | |  /  \
nextcloud      |          | | \__ \ | | | () |
nextcloud      |          |_| |___/ |_|  \__/
nextcloud      | 
nextcloud      | 
nextcloud      | Brought to you by linuxserver.io
nextcloud      | -------------------------------------
nextcloud      | 
nextcloud      | To support LSIO projects visit:
nextcloud      | https://www.linuxserver.io/donate/
nextcloud      | -------------------------------------
nextcloud      | GID/UID
nextcloud      | -------------------------------------
nextcloud      | 
nextcloud      | User uid:    1002
nextcloud      | User gid:    1005
nextcloud      | -------------------------------------
nextcloud      | 
nextcloud      | [cont-init.d] 10-adduser: exited 0.
nextcloud      | [cont-init.d] 20-config: executing... 
nextcloud      | [cont-init.d] 20-config: exited 0.
nextcloud      | [cont-init.d] 30-keygen: executing... 
nextcloud      | generating self-signed keys in /config/keys, you can replace these with your own keys if required
nextcloud      | Generating a RSA private key
nextcloud      | .................................+++++
nextcloud      | ...........+++++
nextcloud      | writing new private key to '/config/keys/cert.key'
nextcloud      | -----
nextcloud      | [cont-init.d] 30-keygen: exited 0.
nextcloud      | [cont-init.d] 40-config: executing... 
nextcloud      | [cont-init.d] 40-config: exited 0.
nextcloud      | [cont-init.d] 50-install: executing... 
nextcloud      | [cont-init.d] 50-install: exited 0.
nextcloud      | [cont-init.d] 60-memcache: executing... 
nextcloud      | [cont-init.d] 60-memcache: exited 0.
nextcloud      | [cont-init.d] 70-aliases: executing... 
nextcloud      | [cont-init.d] 70-aliases: exited 0.
nextcloud      | [cont-init.d] 90-custom-folders: executing... 
nextcloud      | [cont-init.d] 90-custom-folders: exited 0.
nextcloud      | [cont-init.d] 99-custom-files: executing... 
nextcloud      | [custom-init] no custom files found exiting...
nextcloud      | [cont-init.d] 99-custom-files: exited 0.
nextcloud      | [cont-init.d] done.
nextcloud      | [services.d] starting services
nextcloud      | [services.d] done.
nextcloud      | Exception: Not installed in /config/www/nextcloud/lib/base.php:282
nextcloud      | Stack trace:
nextcloud      | #0 /config/www/nextcloud/lib/base.php(663): OC::checkInstalled()
nextcloud      | #1 /config/www/nextcloud/lib/base.php(1104): OC::init()
nextcloud      | #2 /config/www/nextcloud/cron.php(43): require_once('/config/www/nex...')
nextcloud      | #3 {main}

Alles anzeigen

Opening https://localhost:2444 I can see the page to install nextcloud. Installed without any problems. But as KM0201 said, you should stick to one guide and not mix them. And please use proper PUID and PGID.

Alles anzeigen

I'll take your word for it.. I've not seen the issue in a while but I've had chats w/ several folks on reddit that that was an issue (or at the very least, changing the paths there worked... who knows what else they were doing on their system). From looking at the two folders in the past (/config and /daa) they had some fairly significant permission differences... but just to take a look, SSH'd my box and took a look at the permissions... they aren't exactly the same, but far more similar than I remember them in the past.

ken0201@openmediavault:~$ cd /srv/dev-disk-by-uuid-408aa422-44c0-40d4-8e38-5c1f5ee1a56b/Disk_1/Media/
ken0201@openmediavault:/srv/dev-disk-by-uuid-408aa422-44c0-40d4-8e38-5c1f5ee1a56b/Disk_1/Media$ ls -l .Nextcloud/
total 172
drwxrwsr-x  4 root users   4096 Feb 19 08:22 admin
drwxrwsr-x 11 root users   4096 Feb 19 08:54 appdata_ocmm9rxcetsh
-rw-rw-r--  1 root users      0 Feb 19 08:19 index.html
drwxrwsr-x  7 root users   4096 Feb 21 14:57 ken8521
-rw-rw-r--  1 root users 154477 Feb 24 03:18 nextcloud.log
-rw-rw-r--  1 root users    947 Feb 22 17:25 updater.log
ken0201@openmediavault:/srv/dev-disk-by-uuid-408aa422-44c0-40d4-8e38-5c1f5ee1a56b/Disk_1/Media$ cd /srv/dev-disk-by-uuid-408aa422-44c0-40d4-8e38-5c1f5ee1a56b/AppData/
ken0201@openmediavault:/srv/dev-disk-by-uuid-408aa422-44c0-40d4-8e38-5c1f5ee1a56b/AppData$ ls -l nextcloud
total 40
drwxr-sr-x 2 ken0201 users 4096 Mar  7 03:15 crontabs
drwxr-sr-x 2 root    root  4096 Jun  6 20:45 custom-cont-init.d
drwxr-sr-x 2 ken0201 users 4096 Mar  7 03:15 custom-cont-init.d.sybsIVzU
drwxr-sr-x 2 root    root  4096 Jun  6 20:45 custom-services.d
drwxr-sr-x 2 ken0201 users 4096 Mar  7 03:15 custom-services.d.sybsIVzU
drwxr-sr-x 2 ken0201 users 4096 Mar  7 03:15 keys
drwxr-sr-x 4 ken0201 users 4096 Jun 20 21:00 log
drwxrwsr-x 3 ken0201 users 4096 Mar  7 03:15 nginx
drwxr-sr-x 2 ken0201 users 4096 May 30 13:25 php
drwxrwsr-x 3 ken0201 users 4096 Mar  7 03:15 www
ken0201@openmediavault:/srv/dev-disk-by-uuid-408aa422-44c0-40d4-8e38-5c1f5ee1a56b/AppData$ 

Zitat von ciaphas2037

I wasn't sure what gid/uid to use, the guidance on linuxserver.io just confused me a bit (https://docs.linuxserver.io/ge…derstanding-puid-and-pgid) as it seemed to suggest that docker runs everything as root, but I didn't think the root gid/uid would be correct. Because I don't really understand how docker runs these things I just took the uid/gid of the admin account from my OMV. I've now created a user (docker1) who is in groups user, ssh, sudo and docker. I've also put everything in seperate directories. I've got nextcloud installed and working locally now, just need to get SWAG up and running for remote access.

Thanks for the quick response, I'm very new to server-related things so guides like yours and community responses are really helpful.

If you have trouble I'll be in discord for a bit tonight. Link is in my sig.

Also, for what it's worth, I'd probably take that "docker" user out of the docker and sudo group. sudo, unless you really intend to use sudo priv's with this user, no need for it. docker.. there's a security issue there where someone of ill intent could delete your root partition if they were so inclined w/o root or sudo privileges just by being in this group.

You may have already figured this out, but to get your puid and pgid, ssh into your server and enter id <your-user>. You should get something like this if your user was wayne:

wayne@m4:~$ id wayne

uid=1000(wayne) gid=100(users)

Or for your docker1 user enter id docker1.

You will use the same puid and pgid in your swag yml file that you used in your nextcloud/mariadb yml file.

Zitat von Agricola

You may have already figured this out, but to get your puid and pgid, ssh into your server and enter id <your-user>. You should get something like this if your user was wayne:

wayne@m4:~$ id wayne

uid=1000(wayne) gid=100(users)

Or for your docker1 user enter id docker1.

You will use the same puid and pgid in your swag yml file that you used in your nextcloud/mariadb yml file.

Alles anzeigen

You can also get them from the webUI now... (users group 100 is default for all users created in the webUI, so that one should always work by default)

https://github.com/openmediavault/openmediavault/issues/1068

Zitat von Zoki

You forgot to remove ssh too. I do nt thing this user will be loggin in with ssh. And to be really safe you can set his login shell to disabled /bin/false.

This is probably true for most users.. I use my regular user (don't create a special user just for docker).. so I SSH w/ that user a lot and thus need it in that group. I may rethink this at some point.