Nextcloud with Letsencrypt using OMV and docker-compose - Q&A

https://ownyourbits.com/2019/0…oving-nextcloud-previews/

Maybe it's power related, which plattform do you use? My setup is a Xeon 4C/8T with 32 GB of RAM.

I am using Intel^® Quad-Core Processor N3150 and 8GB of RAM.

Why should it not work with a lower power machine? I guess indexing and thumbnailing will just be slower...

Guys I can't access to Nextcloud, I get this message:

Internal Server Error

The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the webserver log.

and this log

 -1 }">PHP Fatal error:  Uncaught Error: Call to a member function getLogger() on null in /config/www/nextcloud/cron.php:161
 -1 }">
Stack trace:
 -1 }">
 -1 }">
}
 -1 }">  thrown in /config/www/nextcloud/cron.php on line 161

I followed exactly the tutorial, what should I do?

How do I push the nextcloud instance into maintenance-mode from the host?

I tried something like this:

docker exec nextcloud sudo -u abc php /www/nextcloud/occ maintenance:mode --on

but did not work. My assumtions:

- user abc runs the webserver within the nextcloud container

- the path to occ must be the leative one within the container

This works for me:

Log in to docker CLI via portainer. Then:

root@a241c3c02115:/# cd /config/www/nextcloud/
root@a241c3c02115:/config/www/nextcloud# occ maintenance:mode --on

So occ is executed as root.

Zitat von riff-raff

docker exec nextcloud sudo -u abc php /www/nextcloud/occ maintenance:mode --on

Or try docker exec nextcloud sudo -abc php /config/www/nextcloud/occ maintenance:mode --on

A little Typo within your command

docker exec nextcloud sudo -u abc php /config/www/nextcloud/occ maintenance:mode --on

docker exec nextcloud sudo -u abc php /config/www/nextcloud/occ maintenance:mode --off

works like a charm.

Next do do: Dump of database for backup purposes.

Thank you Morlan

Edit:

docker exec nextclouddb /usr/bin/mysqldump -u nextcloud --password=xxx nextcloud > /srv/dev-disk-by-label-xxx/backup/nextcloud_backup.sql

Seems to work, but backup database seems a litte too small somehow. (Previous natively installed MariaDB backups of NC were >120 MB, this is only 40 MB and there was not much activity on this cloud lately)

Last night, following the macom guide I installed Nextcloud on my OMV 5.x.

To speed up Nextcloud as suggested by monsen I also added redis to the stack.

Everything worked perfectly so I turned OMV off.

When I restarted it this morning, I received the "Internal Server Error" message.

I checked the logs, but there was no obvious error.

I therefore went to check the port assigned to redis container which was different from the one used before the restart.

My question then is:

is there any way to fix the port used by redis container so that it doesn't change with every reboot?

Nextcloud config.pho now start with:

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'memcache.distributed' => '\\OC\\Memcache\\Redis',
  'redis' =>
  array (
     'host'     => '172.18.0.3', # <== this value changes with each reboot
     'port'     => 6379,
  ),  

Do I need to change the host value?

If yes, what value should be entered?

Thanks.
Davide.

The port 6379 stays fix for me. Not sure why it would change. It shouldn't

Zitat von monsen

The port 6379 stays fix for me. Not sure why it would change. It shouldn't

On reboot change the host IP, not the port

If you are using a stack for all containers, best is probably to use docker hostnames instead of IP adresses. I believe the docker containers receive their ip addresses after a first-come-first-server principle. So it might change.

I try with network name, but with this setting receive Internal Server Error again...

Are all your containers belonging to nextcloud in the same stack?

Yes.

This is a screenshot of stack details

Zitat von macom

When trying to use hostname instead of IP, did you edit the stack and the config.php like here?

RE: [How-To] Nextcloud with Letsencrypt using OMV and docker-compose

Just tried it and works for me.

Now it works!

Hi,

I've used that tutorial to install nextcloud and it's been running for a few month now without issue, until a few days ago.

I'm now seeing a "502 Bad Gateway" error from nginx when I try connecting to the nextcloud URL, and the only thing I managed to find by myself is a ton of the following error messages when I run docker logs letsencrypt as well as docker logs nextcloud :

ERROR: No pool defined. at least one pool section must be specified in config file
ERROR: failed to post process the configuration
ERROR: FPM initialization failed

I more or less understand it probably means some kind of php-fpm conf is messed up which is preventing nextcloud (and letsencrypt as well?) from starting up, but I have no clue how to dig further...

Any help appreciated

Hi! First of all thanks for all the guides! They have helped me a lot. There is already the manual for an integration of a OnyOffice docker, but I like CollaboraOffice more. Is there already a customized manual for it? I can only find general installation instructions and I'm not sure enough in docker that I can customize them to omv.

From yesterday, my NextCloud Docker installation result in Maintenance Mode.

How I can disabled It?

SOLVED!

Problem was due to a plugin incomplete update.
To resolve, enter on docker bash:

sudo docker exec -it <YOUR-DOCKER-NAME> /bin/bash

To remove maintenance mode, digit:

sudo -u abc php /config/www/nextcloud/occ maintenance:mode --off

(where "abc" is the user owner of config.php)

To avoid timeouts with large installations, you can run the following command from the installation folder.
So digits:

cd /config/www/nextcloud   #installation folder for Nextcloud docker
occ upgrade

Thats all!