Failed to modify Server: An Nginx virtual host with the same name already exists

SYSTEM INFORMATION
OS type and version Ubuntu Linux 20.04.6
Webmin version 2.111
Usermin version 2.010
Virtualmin version 7.10.0
Theme version 21.10
Package updates All installed packages are up to date

Reproduce

I’ve created a new Server xlivery.com and add LetsEncrypt-Certificate to it.
Anything work as expected.

Then I’ve created a SubServer xlivery.shop below xlivery.com.
As I later on better want to have it as parent server, I’ve used the Manage Virtual Server > Move Virtual Server and moved this subserver to a “parent” one.

It work so far, as it was a parent now.

Issue

But the issue is, the previous parent server xliver.com has lost it’s ssl-config, and even don’t have any checkbox to activate it again in “Edit Virtual Server”:

Thats not all, the “Checkbox” “Nginx website enabled” is unchecked, but the vhos-file still exist in /etc/nginx/sites-available for this server.

But inside the file, all previous SSL-Settings (means as the xlivery.shop still was an sub-server of xlivery.com) are gone. There isn’t any SSL-Section at all in that file.

Both http: and https: URL’s to xlivery.shop throw an 404 from nginx.

Error

Got this error, if I try to set the checkbox in the “Edit Virtual Server” Dialog

Failed to modify server : An Nginx virtual host with the same name already exists

Any Idea what’s wrong here?

Fully removing xlivery.shop - which need to go to CLI, and recursively delete all xlivery.shop entries in /etc/nginx and then do create xlivery.shop as new Virtual-Server work.

If Server is set up this way, I see 2 checkboxes for NGINX in the dialog. One for Nginx, one for NGINX SSL.

BUT

If I then edit the virtual-server and e.g. only change the “Account-Plan” and click save, it removes the SSL-Certificate from the domain, and deactivate the NGINX-Setup AGAIN, then same behavior happen as described above.

…if you try to re-activate the NGINX by checking the box, above error-message occur.

BTW:
I use Webmin / Virtualmin since years on this server, and in the past it work as expected. So it might be an issue which came with last Webmin-Update?!?