Hey folks,

 

Im an unRaid newbie but got my first server up and running. Im in th eprocess of migrating services from my old Ubuntu (corrupted) machien to a new unRaid setup.It was a steep learnign curve but Im happy to say that most things are up and running, except the most important service Nextcloud!

My old server was stuck on php 7.4 since I couldnt install any new software anymore and I guess thatshwy NC remains on version 25.0.9. It was a "plain" install without any docker or virtualization.

 

After copying my mySQL, Nextcloud dir and the Nextcloud data dir I wanted to startup the container on the unraid machine but got confronted with an error saying that the old instance found is two major versions behind the current version on the new server. And its only supported to be one major version behind.

 

So now it seems Im stuck having an old NC 25 backup and an up to date but empty unraid/docker container on version 27.

Can someone guide me on how to resue my Nextcloud restoration project? Ideally pointing to some step by step guide since I already had my fair share of challenges moving all the files from a standalone install to a docker based setup.

 

Any help is greatly appreciated! Thank you in advance!!

 

Server setup:

- unRaid 6.12.3

- Appdata / Cache on a mirrored ZFS Pool 2x NVME SSD
- ZFS RaidZ1 Pool with 3 HDDs (replacing the classic Array)

 

tower-diagnostics-20230730-0726.zip

The most probable solution would be to append the tag for the specific version you want instead of the latest tag that is used by default until you can upgrade nextcloud using the internal updater.

 

You will need to look at the support thread for the specific nextcloud container you are using to determine what the exact syntax of that tag should be. There are many different nextcloud containers, and each one has their own support thread, you need to post in that thread instead of general support for issues with that container.

Thank you!

I think I got docker to pull the 26.0.2 version from linuxserver.

 

However, I seem to be lost in the next steps. Here is what I did:

1. Left MariDB Docker and Nextcloud data directory untouched (already had copied my backup into the respective folders).

2. Reinstalled Nextcloud container with 26.0.2 version.

3. Then copied my nextcloud dir backup into /mnt/cache/appdata/nextcloud/www/nextcloud/

 

Starting Nextcloud doesnt seem to recognize any of my restoration attempts.

Here is the log after starting nextcloud container:

 

Quote

using keys found in /config/keys
**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
│  old date  │  new date  │ path                                                                   │
├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│ 2023-06-23 │ 2023-04-13 │ /config/nginx/site-confs/default.conf                                  │
│ 2023-06-24 │ 2022-08-20 │ /config/nginx/ssl.conf                                                 │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘
**** The following site-confs have extensions other than .conf ****
**** This may be due to user customization. ****
**** You should review the files and rename them to use the .conf extension or remove them. ****
**** nginx.conf will only include site-confs with the .conf extension. ****
/config/nginx/site-confs/default
[custom-init] No custom files found, skipping...

 

When I try to open the webgui I just get a 404.

 

I still feel very insecure whether I restored everything to the right folders since Im new to the docker environment. What is the best step by step routine to troubleshoot the situation and find out where things have gone wrong?

 

Also when I open a terminal into the docker image and try to use my known commands e.g. activating maintenance mode in var/www/ Im just getting an error message. Where am I uspposed to run these (will be relevant for future OCC database issues going forward as well)?

On 7/31/2023 at 9:02 AM, JonathanM said:

you need to post in that thread instead of general support for issues with that container.