NextcloudPI Docker container still asks for activation even after restore

Peter · June 8, 2019, 8:48am

Is there a way to automate the Activation page of the NextcloudPI-X86 Docker container ?

NCP still asks for the Activation after deploying a new container, even when restoring from a backup with ncp-restore.

I didn´t find any “ncc” command to get over the activation page.

Any ideas ?

nachoparker · June 8, 2019, 6:05pm

Hi,

The whole idea is to force the user to get a random password, so this cannot be skipped.

It can be automated though, you can use the activation test

github.com

nextcloud/nextcloudpi/blob/master/tests/activation_tests.py

#!/usr/bin/env python3

"""
Automatic testing for NextCloudPi

Copyleft 2017 by Ignacio Nunez Hernanz <nacho _a_t_ ownyourbits _d_o_t_ com>
GPL licensed (see LICENSE file in repository root).
Use at your own risk!

   ./activation_tests.py [IP]

More at https://ownyourbits.com
"""

import sys
import time
import urllib
import os
import getopt
import configparser

This file has been truncated. show original

, which will store the random passwords on a text file.

Peter · June 9, 2019, 7:49am

I agree to the force random password, but let´s assume I want to move my data to another docker host. I deploy the new container and then I use ncp-restore with docker exec.

Of course the restore contains NOT the default passwords, but the activation page is still showing up. Is it enough to call the two commands from nc-passwd.sh ?

activate NCP

a2ensite ncp nextcloud
a2dissite ncp-activation

Moreover I think showing up the activation page at an early stage is a potential security issue for docker deployments in public areas. As soon as you run the docker compose command, Apache is up with the activation page, but the rest of the init takes a while, depending on your docker host. Since the public ip of your docker host is added to the trusted domains, there is enough time for one to get the random generated passwords.

Wouldn´t it be nice to have an option in the docker-compose.yaml to “secure” the deployment until a docker exec command to change the initial passwords is called ? Just an idea…

nachoparker · June 9, 2019, 11:47pm

The idea is to activate and then restore, you can automate activation with that python script, or with nc-passwd + nc-admin.

Nextcloud is not operative until the activation ends. Also no public IP is added unless you add it yourself.

That been said, there are lots of possible improvements, so contributions are very welcome.