Some weeks ago, I bought some Raspberry Pis 3 B+ for some different projects.
One of these was intended to be running NextCloud and I chose to use the official NextCloud Pi/Plus project image.
Unfortunately, I was not able to get it to work yetā¦
First, I had problems concerning my router and āsshā but those problems are fixed now. Now after the first devices are running fine, I am running into problems with NextCloud Plusā¦
On the activation page, when I click activate the installer only shows the message: āNextCloudPlus not yet initialized, trying again in a few seconds ā¦ā and when I wait for a longer time: āSomething went wrong. Try refreshing the pageā. I tried different browsers, different computers but it just will not work.
I do not know what to do anymoreā¦ even that I am not a newbie, I followed the guides on GitHub systematically but cannot find the problem.
I can confirm this issue, latest Docker image seems broken:
from Docker logs:
Starting Redis
Starting Cron
Starting Postfix
Nextcloud is not installed - only a limited number of commands are available
[Symfony\Component\Console\Exception\CommandNotFoundException]
There are no commands defined in the "config:system" namespace.
Init done
By the way, please tag the Docker images and do not override the images, because we do not have the possibility that we can checkout an older image, if the newer one is broken.
(I am using Nextcloudpi a few month now and till now I am really satisfied - thanks for the awesome work!)
did you try to upgrade by pulling? how did you end up in this situation?
the docker container is not broken, just tested it now. Maybe you tried to upgrade by pulling, or you tried to start from zero but didnāt do so in a clear volume? you can pass any folder to the -v /myfolder:/data parameter to verify that it works (will start a clean instance), without deleting/losing your current volume.
It gets always stuck in the situation mentioned in my previous post, which therefore does not progress on the activation web interface.
I luckily found an old image because Docker has also updated the systemd service config to use the default docker directory again, so I was able to use the Docker image from February again.
With the new image I could not get it up and running.
your issue is unrelated to @patrick0210ās ( he kinda hijacked the thread xD )
just go for the SD card version. If weird things fail (your case) suspect a hardware issue which is very commonly due to cheap power supplies and SD cards.
Yeah, it is easy to call it a hardware problemā¦ All my other projects are working fine even on this raspberry. I am really disappointed to be honestā¦ I could think of wrong settings in my router or my PC but the raspberry is fineā¦
Sorry, I did not meant to offend you I was just using it as an expression.
But in this case I doubt something different could be the problem, funny that Dieter_Muller an I both are German maybe a local issue? Router/Firewall/IP/ Providerā¦ could that cause problems?