Issue After wp-toolkit website move its reported as broken, can't clear cache site not found

[Shamrock]

Server operating system version

Ubuntu 22.4

Plesk version and microupdate number

18.0.71#2

Before moving our staging, newly build, website to production. I wanted to move the current production website to the dev.example.com subdomain.
The move seems to be done well, all documents seem to be present.
Even the maintenance state was copied over.
However:
* wp-toolkit keeps reporting the site as broken
* ERR [
{extension/wp-toolkit} failed to reset cache for instance #X reason: Error: site 'dev.example.com/' not found. Verify DOMAIN_CURRENT_SITE matches an existing site or use --url=<url> to override.
* error is proeprted reported twice, then a line telling me there is a broken wordpress instance found then twice again.
DNS checks all out okay, all records are correct and resolvable. Yes also checked externally
SOmehow somwhere wp-toolkit doesn't get it and is unable to resolve.
And yes DOMAIN_CURRENT_SITE is correct as well, even the details in the instances table in the wp-toolkit sqlite3 db is set correctly.
I even have tried detaching it, cleaning if present the remaining entries in the sqlite3 database and scanning for it again, no luck.
Any suggestions to get this working again? I want to have this fixed before even attempting a move from staging to production in case I run into the same errors.

 

[Shamrock]

Update: clearing the WPT cache doesn't resolve the issue, unfortunately.

 

[Shamrock]

Looks like there is a bug in wp-toolkit that is causing this behaviour.
Plesk support is going to try a fix tomorrow morning.
I will update this thread with the details as soon as that's complete and confirmed to be working.

 

[Shamrock]

Update:
There are multiple bugs in wp-toolkit when trying to clone a multisite to another subdomain within the same subscription.
The error is just the symptom of a lot of stuff breaking behind the scenes, including hostnames being rewritten incorrectly and others not being rewritten at all.

If anybody has any more advice then either use something else or take the following precautions, let me know.
Any advice is very welcome.

From Plesk support regarding things to be aware of when using clone and multisite:
Things you should keep in mind are at least:
Remove the DOMAIN_CURRENT_SITE directive from the wp-config file of the original domain before the cloning.
Adjust the database name, user and password in the wp-config file of the cloned domain after the cloning.
Adjust the URLs in the wp_blogs table of the cloned domains database.

Additional question: which rewrites should have happened, is that only for the database table named above or do all the URLS in the database require to be rewritten? (e.g. option, post pages etc. tables).

 

[Shamrock]

For those coming across this, the official advice (and I have to concur for now):
Whatever you do: DON"T USE wp-toolkit for multisite cloning, that is until Plesk fixes their multiple bugs.
That's almost 2 days of work lost and requiring another $399 (regular price) plugin to solve what I hoped wp-toolkit would do (and what is advertised it should have done).
I've added a feature request for this in the Plesk product board (would have posted the link if I could find it back).