Search results

Hello, @hzl . Can you please navigate to Tools & Settings > Info and Statistics and confirm if there a sufficient amount of available disk space?

Hello, @zaytsev . Thank you for the report. We are aware of the issue and our team is already working on a hotfix PPP-69251. It is expected for the fix to be released in the upcoming week. At this point, there is no workaround we can suggest, unfortunately. You can monitor the change log here.

@TorbHo , if the migration is performed through Plesk Migrator, the Storage method of passwords (hash or sym) for the migrated passwords will depend on the default method selected on the destination server. If the default method is hashing, then all migrated email account passwords will be...

The behavior was identified as a bug with ID PPPM-15085. The fix will be introduced at one of the upcoming releases. In the meantime, the only workaround is setting Default Site to none in Tools & Settings > IP Addresses as already suggested by @LRLD .

The behavior was identified as a bug with ID PPPM-15085. The fix will be introduced at one of the upcoming releases. In the meantime, the only workaround is setting Default Site to none in Tools & Settings > IP Addresses.

@TorbHo , thank you for the question. I will confirm with our team and I will follow-up as soon as possible.

@MaasRick , could you please confirm if you have the affected domain set as Default Site in Tools & Settings > IP Addresses?

Thank you for the report, @LRLD . I was able to replicate the issue. I opened an internal case for further investigation and I will update you with confirmation as soon as possible.

The functionality is still supported only by the Plesk Premium Email, powered by Kolab extension.

Our team was able to identify the issue and they are actively working on resolving it. At this point, I cannot provide any ETA on when it will be fixed. I will follow-up with more details as soon as possible.

Thank you for the additional details. I am still unable to replicate it, unfortunately. I would suggest opening a ticket with Plesk support for further investigation on your server. To sign-in and open a ticket please go to: https://support.plesk.com If you got your license from a reseller...

The fix is now published, you may proceed and update the extension according to these instructions.

@othmaqsa , as of Plesk Obsidian 18.0.72, you should no longer see the false-positive warnings about the 'sw-tar' and 'plesk-mysql-server' packages.

@RalfMeyer , this is a registered bug. Our team is actively working on fixing it and a new release is expected in the upcoming few hours. Once there will be an extension update available, you will need to update it following these instructions. I will follow-up again with confirmation when the...

Hello, @CrackerJax . On a Windows-based environment MySQL 8.0 is supported as remote database server only. The workaround we can suggest is to install MySQL 8.0 on a separate server or Docket container and add it as a remote database server to your Plesk server.

Thank you for the provided details, @DubStepMad . I attempted to reproduce the issue on a test environment through a skeleton installation and remote repository, but both went without errors. Is there anything specific in your attempt? A subdomain, subdirectory installation, etc. ? If you can...

Hello, @DubStepMad . The issue should be sorted in Laravel Toolkit 1.5.2-3677. Can you please confirm the OS, your Plesk version, and whether you install a skeleton or from a remote repository? Thanks in advance.

Hello, everyone. The issue with the DKIM keys is fixed in Plesk Migrator 2.30.0: You can update the extension following these instructions.

I just want to confirm that the issue with the DKIM keys is fixed in Plesk Migrator 2.30.0:

Thank you. Please try commenting out: #bind-address = 127.0.0.1 then kindly let us know if the dump process still fails.