Search results

Hi @LarsK The new version of the Plesk Migrator with fixed #PMT-4647 was published an hour ago. To use newer version, update Plesk Migrator to the latest version: Extensions -> Updates -> Checks now -> check 'Plesk Migrator' and update.

@LarsK, Thank you for report the issue. The migration features are delivering in the scope of a separate Plesk Migrator extension and not depends on Plesk Obsidian shipment. Anyway, we've prioritized the issue #PMT-4647 and will deliver a fix as soon as it will be fixed.

Hi @HoracioS, Thank you for reaching out to our support. AFAIK, the issue is solved now, but I would like to sum here if another forum user will face the same: the issue was caused by enabled protection for RPM repositories and actual for Plesk Obsidian as we started to ship some of the custom...

@HoracioS I would strongly recommend contacting our support Plesk Help Center You don't need to add exclude lines in the package manager configuration, an opposite, they should not be there. I still don't think it's an upgrade bug as we heavy testing such scenarios, but it could be the issue...

How to Exclude Specific Packages from Yum Update – TecAdmin How To Exclude Packages from Apt-Get Upgrade – TecAdmin

Not in RTM, but you could expect the support of Debian 10 and RHEL 8 within next 2 monthly publications.

@HoracioS Please make sure that plesk-mail-pc-driver package is not added to the exclude list of used package manager (apt/yum). To fix the issue quickly, please contact our support Plesk Help Center as we need to check it deeply.

@LarsK The autodiscovery will work and w/o adding of any DNS records as we providing requested parameters based on domain's configuration, you could check additional directives in htttd.conf and nginx.conf.

HI @LarsK The abilities to manage the mail-autodiscovery feature will be added in the next Plesk Obsidian RTM build (10 days left). If you have installed a new Plesk Obsidian Linux server with the latest update (RC4 18.0.18), the mail auto-discovery feature is enabled by default. You can also...

Hi @Hextrator, The ext-social-login options like redirectUrl, appId and appSecret are not intended to be used by Plesk administrators. We did not declare support of custom login pages for Social login extension. The reason why you found this is Panel.ini Editor extension is shown all available...

Hi @Kingsley, We are publishing stable Plesk Obsidian builds since June (first preview). But if you want to be sure and minimize business risks, the official Plesk Obsidian RTM (Ready to Market) build will be published on September 25th (10 days left).

Hi @HoracioS Please attempt to upgrade one more time. The issue is caused by the fact that we've delivered the update of Dovecot to Plesk Onyx 17.8 (due to critical vulnerability in Dovecot and fact that major number of our customers are using 17.8 version now) a bit earlier than on Plesk...

Hi, I'm glad to announce the next Plesk Obsidian Release Candidate 4 (18.0.18) has been published. Release Notes: Change Log for Plesk To help us make Plesk better fill a short survey https://pt-research.typeform.com/to/szWk8h To know what's new in upcoming Plesk Obsidian release see What's...

Hi @destan40 I confirm this issue as a bug #PMT-4642. We will fix soon. As a workaround, please use migration by customers, resellers or subscriptions.

Got it. I will back to you with updates.

Hi @urbanstudio, thank you for clarifications. I've re-checked internally, and you are right: the issue was caused by the fact that Grafana extension (used in Advanced Monitoring) and Premium Antivirus are using the same 3000 TCP port for work. This issue was fixed at Grafana 1.0.1 and...

Hi @urbanstudio, This issue not related to Advanced Monitoring nor Plesk Obsidian. It looks like old issues with Plesk Premium Antivirus itself. Please check the following articles to fix the issue: DrWeb notifications are received: The antivirus software failure DrWeb problem "filter fails to...

Hi @danami, We can't reproduce the issue on our Plesk Obsidian RC3 builds based on provided steps. I assume there could any specific details or configuration which we are missing. To fix the issue, it will be great if could check it on your Plesk installation. Please contact our support team...

Hi @Ian Bélisle This is strange. Plesk w/o WordPress Toolkit have no abilities to enable the maintenance mode for WordPress websites. I think the maintenance mode was set directly in the WordPress website using one of the following methods How to Put WordPress in Maintenance Mode (3...

No exact ETA, but we have plans to implement this feature after Plesk Obsidian RTM release in September.