Nextcloud migration stuck with wrong virtual host name

[mrmarkuz]

When migrating Nextcloud to NS8, the migration tool gets stuck at 0% when a wrong 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:

After retrying with correct virtual host name the migration is stuck at 0%:

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

[nethbot]

in 7.9.2009/testing:

• nethserver-ns8-migration-1.3.4-1.1.gcb31129.ns7.x86_64.rpm x86_64

[stephdl]

QA

The goal of these tests is to verify the installation and migration process for applications that require setting a VirtualHost (FQDN) in the migration panel.

Validation Rules:
When entering the VirtualHost:

• It must be a valid FQDN (e.g. domain.com, sub.domain.com, sub.sub.sub.domain.com).
• It must not contain invalid characters.
• Only letters, numbers, -, and . are allowed.
• The prefix http:// or https:// must be rejected.

Test Steps:

For each application listed below, perform the migration process.
When prompted for a FQDN:

• Enter an invalid value (e.g. containing spaces, special characters, or protocol prefix) and verify the validation fails.
• Enter a valid FQDN and verify it is accepted.

Applications to Test:

• Nextcloud
• NethVoice
• NethCTI
• Roundcube
• SOGo
• WebTop

Expected Result:
Each application correctly validates the VirtualHost input according to the rules above, preventing invalid entries and accepting proper FQDNs.