• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Search results

  1. R

    Resolved Docker with Nginx proxy - 502 Bad Gateway

    Hello, I have a problem with the Nginx proxy for the docker. When trying to enter the site from the container is: 502 Bad Gateway: 2020/03/16 12:15:06 [error] 28661#0: *27 connect() failed (111: Connection refused) while connecting to upstream, client: 31.0.xxx.xxx, server: ubuntu.led-glass.eu...
  2. R

    Resolved innodb_table_stats has length mismatch

    Thanks for help @Monty
  3. R

    Resolved innodb_table_stats has length mismatch

    Hi All, There is such a warning after upgrading from Onyx to Obsidian: [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name...
  4. R

    Issue Error on upgrade to Obsidian

    I solved the problem myself, changed it in the table "smb_users" in database PSA: - contactName: varchar(255) to TEXT - companyName: varchar(255) to TEXT - country: varchar(255) to TEXT
  5. R

    Issue Error on upgrade to Obsidian

    I have the same problem: Migration failed: 17.9.6/2019-04-23-11-14-00_add_recovery_email.php Query failed: ALTER TABLE `smb_users` ADD COLUMN `externalEmail` varchar(255) Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage...
  6. R

    Issue Backup restore too very very long

    Yes, the backup file is bigger But downloading and unpacking in the / tmp directory takes only a 10-15 minutes - restoring 5 hours I also launched a test server, 100MB backup file and the same problem. Also it is not the fault or configuration settings for my server.
  7. R

    Issue Backup restore too very very long

    Load Average 0.84 .069 0.70 Load Average 0.22 0.34 0.53 within a few minutes For example, I also have Softaculous installed, which I use for a Prestashop backup of the store. Restoring the 300 Mb database and 2 GB directories takes 2-3 minutes. Plesk is a good solution, but the backup...
  8. R

    Issue Backup restore too very very long

    Dedicated Root Server Hosting - Hetzner Online GmbH The restoring process uses around ~1%
  9. R

    Issue Backup restore too very very long

    There are no errors or similar things in the logs. The all process has a usage of 2-5% processor at that time. I started the second test server on a different system, but also with the same version Plesk Onyx - this is exactly the same problem! There are some entries on the net about a slow...
  10. R

    Issue Backup restore too very very long

    I would also like to know? the restoring process used 0.5-.1.5% of the processor, It may be a problem? no matter what I restore
  11. R

    Issue Backup restore too very very long

    It restored after 10 hours. :confused: I do not have damaged copies, I checked this way nothing helps! As part of the test I wanted to restore the SQL database 1MB, after an hour I turned off The backup file was downloaded from sftp to / tmp a few minutes and restoring from this file is a joke.
  12. R

    Issue Backup restore too very very long

    Hello, Backup restore files 200MB and database sql 5 MB too very very long!!, it already takes 5 hours :mad: I've tried to restore several times, but after an hour I got angry then I stopped
  13. R

    Resolved Can not add a mailbox - DB query failed: SQLSTATE[23000]...

    Well, finally someone knew. Big Thanks IgorG
  14. R

    Resolved Can not add a mailbox - DB query failed: SQLSTATE[23000]...

    And there is no solution?
  15. R

    Resolved Can not add a mailbox - DB query failed: SQLSTATE[23000]...

    But it has nothing to do with the backup first e-mail account has been created and the next accoun is not
  16. R

    Resolved Can not add a mailbox - DB query failed: SQLSTATE[23000]...

    Nothing helped DB query failed: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '10' for key 'PRIMARY', query was: insert into spamfilter (`id`,`username`,`preferences`,`serviceNodeId`) VALUES ('0','edyta.malek@led-glass.de','true','1') plesk db "show table status where...
  17. R

    Resolved Can not add a mailbox - DB query failed: SQLSTATE[23000]...

    Hello, I have an error adding a mailbox: DB query failed: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '9' for key 'PRIMARY', query was: insert into spamfilter (`id`,`username`,`preferences`,`serviceNodeId`) VALUES ('0','edyta.malek@led-glass.de','true','1') Here is the...
  18. R

    Issue Problem witch adding subdomains

    That was the first thing I did
  19. R

    Issue Problem witch adding subdomains

    I went only to Apache - it does not work I only went to Nginx - it does not work Now Ngnix is off, everything has been reconfigured shop.led-glass.eu - error 500 All browsers are cleaning, then it is the same redirect led-glass.eu to led-glass.de
  20. R

    Issue Problem witch adding subdomains

    I stopped Nginx I stopped Apache without result led-glass.eu - must not going to redirect now! shop.led-glass.eu: Server Error 500 Internal Server Error
Back
Top