Error — Perl execution failed: after Virtualmin 7.7 upgrade

SYSTEM INFORMATION
OS type and version Ubuntu 22.04
Webmin version 2.021
Virtualmin version 7.7 GPL
Related packages up to date

After upgrading to Virtualmin 7.7 when going to Backup and Restore on 2 servers I get:

HTTP/1.0 500 Perl execution failed Server: MiniServ/2.021 Date: Sat, 22 Apr 2023 02:18:08 GMT Content-type: text/html; Charset=utf-8 Connection: close
Error — Perl execution failed

Undefined subroutine &virtual_server::can_use_gcloud_storage_creds called at /usr/share/webmin/virtual-server/cloud-lib.pl line 304.

line 304; elsif (&can_use_gcloud_storage_creds()) {

I restart Webmin from command line as suggested in older threads and it doesn’t change.

thanks
Marvin

I just noticed the thread below and deleted

elsif (&can_use_gcloud_storage_creds()) {
return { ‘ok’ => 1,
‘desc’ => $text{‘cloud_gcpcreds’},
};
}

from
cloud-lib.pl

it cleared the error and backup is working fine. Restored fine on new server.

The great part is that it was a large legacy email account that was migrated without having to make an extra unix user. It receives email from outside. Magic from my point of view :sunglasses:

When will this problem be solved? @Joe

Same problem here

Problem persist on subdomains after 7.7-2 upgrade. @Joe @Jamie

Can you explain more about what is happening? Virtualmin 7.7-2 fixes it for me. Did you try to restart Webmin manually?

Yes I did.
I am getting this error everytime.

Creating backup for virtual server abc.domain.net
Copying virtual server configuration …
… done

Copying records in DNS domain …
… domain not found!

Was this domain created just recently, with the bugged Virtualmin 7.7-1 GPL version?

Version is 7.7-2 GPL. No this is old domain and DNS records exist. Created on 30/Jan/2023 by user

Does BIND DNS domain config file exists on your system and how does it look like?

The file can be found in /var/lib/bind on Debian systems and in /var/named/ on RHEL.

Also, I recommend you to open a separate ticket! This is completely unrelated issue to the original topic.

I will close this treat. Please open a new ticket!