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

Recent content by landrei

  1. L

    Resolved Imunify360 can't find archive

    Thanks @AndyWe that worked for me too
  2. L

    Issue Plesk backup. Unable to back up database #. Error: Unable to find row with id in data_bases table.

    After deleting that subscription and recreating it, then manually add files, db, mails - as expected - the error is gone, but this is not a solution for all ...
  3. L

    Issue Plesk backup. Unable to back up database #. Error: Unable to find row with id in data_bases table.

    This guide doesn't nothing: https://support.plesk.com/hc/en-us/articles/12376926083607-Backup-in-Plesk-is-created-with-warning-Unable-to-back-up-database-Error-Unable-to-find-row-with-id-in-data-bases-table Did anyone managed to solve this, is quite anoying. I was thinking to recreated that...
  4. L

    Issue Plesk backup. Unable to back up database #. Error: Unable to find row with id in data_bases table.

    Same here, every daily backup comes with a mail with warning file attached.
  5. L

    Issue Plesk backup. Unable to back up database #. Error: Unable to find row with id in data_bases table.

    Warning: Application "WordPress" Unable to back up database #28. Error: Unable to find row with id 28 in data_bases table. If I run the queries listed here a table is missing (probably renamed)...
  6. L

    Issue Server backup fails after moving domain to subscription

    Thanks, I run again repair all and few issues have been found, DB inconsistency, FTP accounts orphan, filesystem permissions. All these because a few domains have been moved from one subscription to another?
  7. L

    Issue Server backup fails after moving domain to subscription

    But that domain has nothing to do with the one I was trying to run Laravel deployment To better understand... Subscription A, domainA.com - I was trying to run Laravel deployment (*git pull) Error says something about a domainB.com from Subscription B, a domain that was part of Subscription C...
  8. L

    Issue Server backup fails after moving domain to subscription

    Another error appear now when I deploy changes from git on a subscription that has nothing to do with those two where I moved few domains. The task "ext-git-task\deployment" has failed. There is no web hosting configured on domain *******.com.
  9. L

    Issue Server backup fails after moving domain to subscription

    Hello, Yesterday, I moved a domain from a subscription to a dedicated subscription. Nothing fancy a simple WP install, 10 posts max, really small website. That didn't work as expected, after moving website content was unavailable, even no error was displayed when I made that move. Then, - I...
  10. L

    Issue IPv6 as Remote Backup address is not allowed?

    I hope this will change soon because more and more servers come only IPv6 as default and IPv4 as extraoption.
  11. L

    Issue IPv6 as Remote Backup address is not allowed?

    Can you help me with a link or anything? You can't use a hostname if is just AAAA record (without A record/ipv4). Is IPv4 mandatory in this case?
  12. L

    Issue IPv6 as Remote Backup address is not allowed?

    Why is not possible to use IPv6 as a FTP server IP? Same thing for AAAA record, if I add that instead, then Plesk will try to resolve an A record instead of AAAA.
  13. L

    Resolved Latest Update to Git Extension is Broken

    Everything seems to be fine after this update! (2.4.7)
  14. L

    Resolved Latest Update to Git Extension is Broken

    I will, thanks -- please see post #11
  15. L

    Resolved Latest Update to Git Extension is Broken

    Git Version 2.4.6-445 My last two comments are after this update. #11 #12
Back
Top