• 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. J

    Resolved Unable to upload backups since 18.0.29

    Since the upgrade to Plesk 18.0.29 the upload of back-ups via FTP is failing: I did the checks mentioned in the warning and those are not failing. Besides the upgrade of Plesk, nothing has changed in the setup of the FTP-server.
  2. J

    Resolved Plesk backups failing with error

    Hi Peter, Yes, I think those issues might be related because they share same symptoms. However, the solutions provided in the articles are not applicable or not solving my issue. I think it is a bug in version 18.0.27. Kind regards, Joost
  3. J

    Resolved Plesk backups failing with error

    Hi all, Since Plesk 18.0.27 Update #1 I receive the following error after each backup run: Despite the error the backups are uploaded to the remote FTP, but I'm not sure if I'm able to restore the backups because of this error. Kind regards, Joost de Bruijn
  4. J

    Resolved IPv6 not working for sites

    Solved myself by completely removing the IPv6 address from the server and add it again afterwards. Everything works fine now.
  5. J

    Resolved IPv6 not working for sites

    I removed the IP-address from the Plesk installation completely and tried re-adding it: plesk bin ipmanage --reread -> Doesn't add the IPv6-address plesk bin ipmanage -c '2a00:xx:xxx:x:xxx:xxxx:xxx:xxx' -mask 64 -interface ens3 -type shared -> Results in: ERR [util_exec] proc_close() failed...
  6. J

    Resolved IPv6 not working for sites

    Hi AYamshanov, Thanks for the quick reply! I can confirm the IPv6 address on the interfaces and the configured address in Plesk are exactly the same.
  7. J

    Resolved IPv6 not working for sites

    I've a Plesk installation (Ubuntu 16.04.6, Plesk 18.0.23 mu3) running for some years and since some time IPv6 connectivity is broken. The internet adapter has both an IPv4 and IPv6 address assigned: ens3 Link encap:Ethernet HWaddr 06:43:d2:xx:xx:xx inet addr:185.87.xxx.xxx...
  8. J

    Resolved Backup Manager doesn't work after updating to 17.8.11 MU3

    It's resolved after upgrading to MU4, so this issue can be closed.
  9. J

    Resolved Backup Manager doesn't work after updating to 17.8.11 MU3

    I'm running Ubuntu 16.04.4. Thanks for the other logfile location, I was not aware of that one. Maybe this can be interesting: [31395]: 2018-04-01 03:37:57.745 ERROR e2f249fa-71ac-42fd-8777-79af0226c968 Dump validation utility returned empty result [31395]: 2018-04-01 03:37:57.807 ERROR...
  10. J

    Resolved Backup Manager doesn't work after updating to 17.8.11 MU3

    Yesterday my Plesk 17.8.11 installation was updated to MU3. This night I received the following error by mail: The following error occurred during the scheduled backup process: Runtime error: Dump validation utility returned empty result at /opt/psa/admin/bin/plesk_agent_manager line 1297. ...
  11. J

    Resolved Plesk 17.0 -> 17.5 upgrade fails on database prep

    I tried to upgrade my current Plesk Onyx 17.0 (running on Ubuntu 16.04.2, MySQL 5.7.17-0ubuntu0.16.04.1). installation to Plesk Onyx 17.5. However, during the preparation stage of the upgrade via the both the cli installer as the web interface, an error occured: Installation started in...
  12. J

    Resolved [PPP-27349] Old back-ups are not removed

    Nice, thanks! Now it is clear to me.:)
  13. J

    Resolved [PPP-27349] Old back-ups are not removed

    Hi, I'm using the global Plesk back-up functionality to make a backup of all the websites on the server. The back-ups are stored on a remote server by FTP. The backups are made every day incremental and once a week full. In the settings, I configured a maximum of 20 back-ups. However, it seems...
Back
Top