Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The APS Catalog has been deprecated and removed from all Plesk Obsidian versions. Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.
The reason in that Plesk could not dump current database schema because of orphaned record. One client IP pool ID (table clients.ip_pool_id) was referred with non existent pool (ip_pool.id).
If you can't fix this database inconsistency by yourself - contact support team.
I have the same Problem-both-FTP and server-repository:
(openSUSE 11, PLESK 10.0.1)
<?xml version="1.0" encoding="UTF-8"?>
<execution-result status="error">
<object name="example.de" type="domain">
<message severity="error" code="msgtext">Unable to create dump: Can't use an undefined value as a symbol reference at /usr/local/psa/PMM/agents/PleskX/PleskStructure.pm line 289.
it's the same on my server. redirected domains cause this error at backup, though there were no errors during upgrade. but even successful backups cannot be restored.
This means that I cannot use a Service Plan without hosting? I have some "Mail-Only" customers, that are causing this error. If I assign some webspace to them, it's working. But I don't want that, and Plesk doesn't tell me to do so. So it's a bug... Where can I post this bug?
Hi,
in my case I've sorted out the problem by deleting the old only-mail-accounts and creating these accounts new.
Since then it has been working well.
A second problem has occured: the partition for the dumps was to small. I have put the dump-folder into an other partition.
The reason in that Plesk could not dump current database schema because of orphaned record. One client IP pool ID (table clients.ip_pool_id) was referred with non existent pool (ip_pool.id).
If you can't fix this database inconsistency by yourself - contact support team.