Nextcloud migration issue

Linux4All · October 12, 2025, 12:16pm

Hi @davidep ,
I have same issue on my end. Since there were so much information in that topic not sure what finally solved the issue.

Could you maybe give me a hint?

Issue on NS8:
module/nextcloud1/import-module

Fehler bei der Validierung von Aufgabe module/nextcloud1/import-module

In die Zwischenablage kopierenAufgabenverlauf kopieren

module/nextcloud1/import-module

Aufgaben-ID: In die Zwischenablage kopierene 360de5d-0faf-4a49-9fcf-6b888252d9b1

Issue on NS7 if I try to finish migration:
root@asterix ~]# echo ‘{“app”:“nethserver-nextcloud”,“action”:“finish”,“migrationConfig”:{“virtualHost”:“obelix.linux.local”}}’ | /usr/bin/setsid /usr/bin/sudo /usr/libexec/nethserver/api/nethserver-ns8-migration
/migration/update | jq
{
“progress”: “0.00”,
“time”: “0.0”,
“exit”: 0**,**
“event”: “migration-sync”,
“state”: “running”,
“step”: 0**,**
“pid”: 0**,**
“action”: “”
}
rsync: failed to connect to 10.0.1.1 (10.0.1.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(126) [sender=3.1.2]

I have also started migration for Email in parallel, not sure if relevant:

Restart of both servers, did not help.

If I click on abort for Mail migration, I get the following:

Last lines of ns8migration.log

podman-pull-missing Package rsync · GitHub
<7>podman run --rm --privileged --network=host --workdir=/srv --env=RSYNCD_NETWORK=10.0.1.0/24 --env=RSYNCD_ADDRESS=cluster-localnode --env=RSYNCD_PORT=20002 --env=RSYNCD_USER=nextcloud1 --env=RSYNCD_PASSWORD=xxxxxxxx
d0d199-6cfa-4116-ba4d-ee83a9ea7571 --env=RSYNCD_SYSLOG_TAG=nextcloud1 --volume=/dev/log:/dev/log --replace --name=rsync-nextcloud1 --volume=/home/nextcloud1/.config/state:/srv/state --volume=nextcloud-app-data:/srv/
volumes/nextcloud-app-data Package rsync · GitHub
""Validation errors: [host: Does not match format ‘hostname’]
[{“error”: “host_format”, “field”: “host”, “parameter”: “host”, “value”: “https://obelix.linux.local/nextcloud/”}]----------- finish nethserver-nextcloud Sat, 11 Oct 2025 14:42:28 +0200
----------- finish nethserver-nextcloud Sat, 11 Oct 2025 14:43:48 +0200
----------- finish nethserver-nextcloud Sat, 11 Oct 2025 14:50:22 +0200
----------- finish nethserver-nextcloud Sat, 11 Oct 2025 14:51:29 +0200
----------- finish nethserver-nextcloud Sat, 11 Oct 2025 15:19:03 +0200
----------- finish nethserver-nextcloud Sat, 11 Oct 2025 15:19:45 +0200
----------- sync nethserver-nextcloud Sat, 11 Oct 2025 15:20:22 +0200
----------- sync nethserver-nextcloud Sat, 11 Oct 2025 15:21:32 +0200
----------- finish nethserver-nextcloud Sun, 12 Oct 2025 14:00:34 +0200
----------- abort nethserver-mail Sun, 12 Oct 2025 14:13:12 +0200
----------- abort nethserver-mail Sun, 12 Oct 2025 14:13:57 +0200
----------- finish nethserver-nextcloud Sun, 12 Oct 2025 14:14:12 +0200
----------- abort nethserver-mail Sun, 12 Oct 2025 14:21:49 +0200
----------- abort nethserver-mail Sun, 12 Oct 2025 14:23:42 +0200
----------- finish nethserver-nextcloud Sun, 12 Oct 2025 14:23:59 +0200
----------- finish nethserver-nextcloud Sun, 12 Oct 2025 14:29:43 +0200
----------- finish nethserver-nextcloud Sun, 12 Oct 2025 14:42:49 +0200
----------- finish nethserver-nextcloud Sun, 12 Oct 2025 14:45:04 +0200

Many thanks for your help

Benjamin

Linux4All · October 12, 2025, 12:31pm

Looks like something with validation fails.
Found that at the nextcloud container log
025-10-12T14:29:44+02:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/71d49def-7ebc-4371-a010-b7c40ac5456c: action “import-module” status is “validation-failed” (2) at step 00validate_import

mrmarkuz · October 12, 2025, 4:57pm

Hi,

is the latest version of the migration tool installed on the NS7?

[root@neth ~]# yum list nethserver-ns8-migration
nethserver-ns8-migration.x86_64 1.3.4-1.ns7 @nethserver-updates

Did you change the default 10.5.4.0/24 wireguard network?

Does pinging 10.0.1.1 still work from the NS7?

I usually migrate one app after the other so maybe that’s the issue…

For aborting a migration of an app manually see NS7 to NS8 Migration issue - #11 by davidep

If nothing works you can reset the migration on NS7 so the NS7 services are working again and you can start over with a fresh NS8, see GitHub - NethServer/nethserver-ns8-migration

Maybe related:

See NethServer 7 migration — NS8 documentation for more information about the migration.

Linux4All · October 12, 2025, 5:36pm

Thank you @mrmarkuz. Please find related answers below.

[root@neth ~]# yum list nethserver-ns8-migration nethserver-ns8-migration.x86_64 1.3.4-1.ns7 @nethserver-updatesnethserver-updates

Installed Packages
nethserver-ns8-migration.x86_64 1.3.4-1.ns7

Did you change the default 10.5.4.0/24 wireguard network?

No

Does pinging 10.0.1.1 still work from the NS7?

yes

For aborting a migration of an app manually see NS7 to NS8 Migration issue - #11 by davidep

If nothing works you can reset the migration on NS7 so the NS7 services are working again and you can start over with a fresh NS8, see GitHub - NethServer/nethserver-ns8-migration

Ok, got it. But would try to avoid it because resyncing needs several days to huge amount of data.

I think this is something different. Ping is still working and no firewall in between.

mrmarkuz · October 12, 2025, 5:59pm

Is there still enough disk space on the NS8?

Is DNS working for obelix.linux.local and pointing to the NS8 IP?

You could check if the data was transferred by checking the size on NS8 like

du -hs /home/nextcloud*
du -hs /home/mail*

OK, so I assume 10.0.1.1 is the LAN IP of the NS8 and 10.5.4.1 is the wireguard IP (wg0)

To check the IPs on the NS8:

ip a

It’s strange because usually the data is rsynced to the wireguard IP and not the LAN IP.

Linux4All · October 12, 2025, 6:42pm

Space if enough available.
/dev/sdb 5.5T 1.2T 4.0T 23% /home

Is DNS working for obelix.linux.local and pointing to the NS8 IP?

yes, working.

You could check if the data was transferred by checking the size on NS8 like

Initial sync has worked. Only finalize migration did not work. Probably I entered wrong servername for virtualhost starting with https:// after that sync was broken

OK, so I assume 10.0.1.1 is the LAN IP of the NS8 and 10.5.4.1 is the wireguard IP (wg0)
To check the IPs on the NS8:

LAN IP is 192.168.0.152
WG IP is 10.0.1.1

2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 08:00:27:c2:4d:0d brd ff:ff:ff:ff:ff:ff
inet 192.168.0.152/24 brd 192.168.0.255 scope global dynamic noprefixroute enp0s3
valid_lft 844804sec preferred_lft 844804sec
inet6 2003:cb:3f4a:9800:a00:27ff:fec2:4d0d/64 scope global dynamic noprefixroute
valid_lft 7042sec preferred_lft 1184sec
inet6 fd4a:30de:44c0:0:a00:27ff:fec2:4d0d/64 scope global dynamic noprefixroute
valid_lft 7042sec preferred_lft 3442sec
inet6 fe80::a00:27ff:fec2:4d0d/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000
link/none
inet 10.0.1.1/32 scope global wg0
valid_lft forever preferred_lft forever

I have started a new install in parallel and will migrate data by myself without the migration wizard. That gives me more flexibility with testing the new NS8 server.

Would also be interesting, if there is some kind of a config reset for final sync or any hint where the config for final sync is stored.

But if you need some more troubleshooting for bugfixing I am happy to help.

mrmarkuz · October 12, 2025, 6:51pm

Yes, that could be a reason because just the FQDN without https:// is needed for the virtualhost name.

Linux4All · October 12, 2025, 6:54pm

Maybe something for improvement on checking the input to be valid.
Is there any config file to correct this?

mrmarkuz · October 12, 2025, 7:02pm

Yes, you could check the /var/lib/nethserver/nethserver-ns8-migration/nethserver-nextcloud/bind.env file on the NS7, see also GitHub - NethServer/nethserver-ns8-migration

Linux4All · October 12, 2025, 7:05pm

Already found that. But nothing special in regarding hostname:
RSYNC_ENDPOINT=rsync://nextcloud1@10.0.1.1:20002
RSYNC_PASSWORD=sdfsfsfsa13213131
MODULE_INSTANCE_ID=nextcloud1
MODULE_NODE_ID=1
IMPORT_TASK_ID=module/nextcloud1/task/8444ce4d-299f-41c8-9684-d3f866729cc9

mrmarkuz · October 12, 2025, 7:15pm

~~Did you already try to search for it by using grep? See Mastering Grep command in Linux/Unix: A Beginner's Tutorial | DigitalOcean~~

EDIT:

You could try to finish the Nextcloud migration on CLI by using

MIGRATE_ACTION=finish NEXTCLOUD_VHOST=nextcloud.obelix.linux.local ./migrate

See also GitHub - NethServer/nethserver-ns8-migration

EDIT2:

The apps in NS8 need dedicated vhost names like nextcloud.obelix.linux.local, maybe you tried to use the same name for more apps?

Linux4All · October 12, 2025, 9:37pm

Thanks, in which folder is the migrate executable?
I have meanwhile made quite good progress with configuring a complete new server and transfering all the needed data manually.

mrmarkuz · October 13, 2025, 7:13am

In /usr/share/nethesis/nethserver-ns8-migration/apps/nethserver-nextcloud, see GitHub - NethServer/nethserver-ns8-migration

davidep · October 13, 2025, 7:36am

If so it’s a migration tool bug that didn’t raise a validation error for the user. What do you think Markus, is it a bug?

mrmarkuz · October 13, 2025, 7:40am

I’m not sure as a validation error was shown.
Maybe we could improve the error message, like “An FQDN has to be entered.”

EDIT:

Tested the issue and confirm it’s a bug. Thanks @Linux4All for pointing out.

github.com/NethServer/dev

Migration tool gets stuck at 0% after entering wrong virtual host name

opened 01:50PM - 13 Oct 25 UTC

mrmarkuz

When migrating Nextcloud to NS8, the migration tool gets stuck at 0% when a wron…g virtual host name was entered before, for example "https://nextcloud.domain.tld" instead of "nextcloud.domain.tld". **Steps to reproduce** - On an NS7, install and configure Nextcloud and the NS8 migration tool - Migrate Nextcloud and sync - Finish the Nextcloud migration and enter a wrong virtual host name like "https://nextcloud.domain.tld" **Expected behavior** An error is thrown so the user knows that he entered a wrong virtual host name. **Actual behavior** There's an error message, that doesn't explain the issue: <img width="1920" height="510" alt="Image" src="https://github.com/user-attachments/assets/6008d99e-3fe4-498d-9e6e-c3ec71128ad4" /> After retrying with correct virtual host name the migration is stuck at 0%: <img width="1920" height="568" alt="Image" src="https://github.com/user-attachments/assets/4ad1866f-7fe7-478d-a7f3-69fc6805ca41" /> **Components** - nethserver-ns8-migration.x86_64 1.3.4-1.ns7 **See also** - https://community.nethserver.org/t/nextcloud-migration-issue/26471 - https://mattermost.nethesis.it/nethserver/pl/f4cmhzrue3b69gxh56jw3c5jnr (private) ---- Thanks to Linux4All

Linux4All · October 13, 2025, 9:40pm

You are welcome! Happy to help.