• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Backup-Manager: Fehler: no element found: line 1, column 0

Tempah

New Pleskian
Hello Team,

I configure the personal repositories it's not working with FTPes, so I tryed with normal FTP it works. The FTP server was for a week not reachable the backup job saved all backup jobs now on the local disk, the reason was the disk was 100% full and I was forced to manual delete the dumps in /var/lib/psa/dumps because the webinterface was not working.

Now i cant change the backup routine or repositories. I click on Tools & Settings > Backup-Manager after this I get a forwarding to the start page with the error:

Fehler: no element found: line 1, column 0


Here some information about the host system:

OS Debian 7.5
Plesk Version 12.0.18 Update #7, zuletzt aktualisiert: Juli 14, 2014 07:01 AM




- With best regards,

- Marco
 
Did you ever figure this one out? I have a Plesk 12.0.18 on centos doing the same thing.
 
Last edited:
Same here !

ERR [panel] no element found: line 1, column 0

After clicking Backup Manager
 
Did you try updating to the latest Plesk version?

--

Habt ihr versucht auf die neueste Plesk Version zu aktualisieren?
 
In our case it was a backup process running.

1. Killed the process ( ps aux | grep backup )
2. deleted temporary files

rm -rf /usr/local/psa/PMM/rsessions/*
rm -rf /usr/local/psa/PMM/sessions/*
rm -rf /usr/local/psa/PMM/tasks/*


and the backup is back to normal ...
 
Back
Top