• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Unable to back up extensions. Error: Failed to exec backup_restore_helper.exe: Exit code: 3: There is no active configuration

Bart Heimenberg

New Pleskian
Server operating system version
Microsoft Windows Server 2016
Plesk version and microupdate number
Plesk Obsidian 18.0.65
Since Plesk Obsidian 18.0.64, I am facing issues with the backups.

Warning: Subscription "xxx"
Unable to back up extensions. Error: Failed to exec backup_restore_helper.exe: Exit code: 3: There is no active configuration

This is only on my Windows machine.

I update this morning to 18.0.65, hoping that the issue would disapear, but it is still broken.

On the server, in the Event viewer I find the below message arround the time I strated to create manully a backup:

The description for Event ID 100 from source MariaDB cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Aborted connection 95232 to db: 'unconnected' user: 'unauthenticated' host: 'xxx' (This connection closed normally without authentication)

My knowledge gets as far as updating things and finding the Event viewer. I hope someoe can help me with this issue?

Thanks a million!

BB

Bart
 
It is a known issue; it happened on systems with the Docker extension where no active configuration is configured. The error is related to the Docker extension only; since there is no active configuration, the configuration is not saved. We are going to fix the issue in the next extension release. Here is a known workaround,
  • if you do not use Docker on Windows (remote nodes), you can remove the extension,
  • if you use Docker, then make one of the environments active,

    1730483295545.png
 
It is a known issue; it happened on systems with the Docker extension where no active configuration is configured. The error is related to the Docker extension only; since there is no active configuration, the configuration is not saved. We are going to fix the issue in the next extension release. Here is a known workaround,
  • if you do not use Docker on Windows (remote nodes), you can remove the extension,
  • if you use Docker, then make one of the environments active,

    View attachment 27279

Many thanks for your prompt reply. Highly appreciated.
 
Hello, everyone. We have released an update which fixes the issue with the backup creation. If you have automatic updates enabled (and already run Plesk version 18.0.66/Docker 2.1.0-848) this update should have been installed already:

Fixed the issue where, on servers with the Docker extension installed, backup creation would fail if only remote docker nodes’ management was supported by the extension. (EXTPLESK-6106)
 
Back
Top