• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Search results

  1. Klaus

    [PPP-26478] After update to onyx backup does not work

    Thanks, what I don't understand is that it worked perfectly well in former versions of Plesk
  2. Klaus

    [PPP-26478] After update to onyx backup does not work

    It's a bit annoying, to say the least. For one of my servers I haven't got a valid external backup for weeks now.
  3. Klaus

    [PPP-26478] After update to onyx backup does not work

    Yes please, do something about that. It's uncomfy the way it is now. It works for a couple of days if I start with a blank list of backups, but various different errors re-occur after some days. :eek:
  4. Klaus

    [PPP-26478] After update to onyx backup does not work

    Another point is, that the sizes don't fit. In the panel it adds up to 486 GB and on the FTP server I got 523 GB ... and the list of backups takes forever to load, the progress indicator of the latest hangs, spins forever. If I click on it it shows progress at 100% ... and if I click on a file...
  5. Klaus

    [PPP-26478] After update to onyx backup does not work

    Got this one: Runtime error: pmm-ras command completed with non-zero exit code at /usr/local/psa/PMM/agents/shared/Storage/ArchiveStorage.pm line 120. CentOS 6.8 Worked again after a reboot last time, but reappeared.
  6. Klaus

    Issue phpMyAdmin error 500 https://kb.plesk.com/en/129220

    So its broken for now? Great ...
  7. Klaus

    Issue phpMyAdmin error 500 https://kb.plesk.com/en/129220

    When are you going to do that?
  8. Klaus

    Issue phpMyAdmin error 500 https://kb.plesk.com/en/129220

    Its leased software, should I install 4.6.1 on Plesk 12?
  9. Klaus

    Issue phpMyAdmin error 500 https://kb.plesk.com/en/129220

    Hi, I just ran into exactly this error, too: https://kb.plesk.com/en/129220 Any suggestions how to fix that? Plesk 12.5.30 #48 CentOS 6.6 >Cause >This is Plesk internal issue with ID #PPPM-4635, which is planned to be fixed in nearest Plesk updates. As of Jun 17, 2016 Cheers
Back
Top