Search results

Hello, Pleskians! We would like to announce that the Black Friday deals are officially on! Promo code: blackfriday2025 Offer: 50% off new licenses (monthly and yearly) for the first period Audience: New sign-ups and active trials Valid: 24 Nov 2025 - 1 Dec 2025 If you have any questions...

@MHC_1 , do you happen to know whether the server those email accounts were migrated from was configured with hashing for mail passwords? If yes, please try switching to hashing and then reset the password of the affected email account. During migrations the storage mechanism depends on the...

Thank you for the screenshots and the provided details. I tried replicating the issue just to make sure there isn't some compatibility issue during Debian 12=>13 migrations, but I was unable to reproduce it, so my guess would be that something went wrong during the migration/restoration process...

Hello, @bernes_stainz . That case is still under review by our development team. Unfortunately, at this point, there's no workaround suggested.

@marcDE , thank you for the provided feedback. That particular case is assigned low priority - likely because there's a relatively simple workaround and it doesn't affect wide range of users (that's my personal guess). It is understandable the workaround is not convenient in all cases. I will...

Peter, according to our team, Jodit is still considered in beta in Plesk 18.0.73. It has been moved to production in 18.0.74. I would like to apologize for any possible inconvenience and confusion. The release notes will be adjusted accordingly to avoid any further misunderstanding.

There shouldn't be an issue for the user to connect through the hostname.

Thanks for the confirmation. I think that might be related to the issue reported in your other thread. If it still persists after changing the email account passwords, could you please also check what's being logged at /var/log/maillog at the time of the failure?

There's no need to apologize. I am sorry for the inconvenience caused by the bug. Our team tested the fix and the same will be introduced with Plesk Obsidian 18.0.75.

Unfortunately, an option to disable to notifications selectively hasn't been introduced yet. At this point, the only suggestion we got is to disable the Imunify notifications altogether (Plesk > Tools & Settings > Notifications), but that will affect the malware scanner notifications as well. I...

@marc@orxo , we do have an internal task (EXTPHPCOMP-115) for improving the behavior, but I cannot provide an ETA for the release. Currently, the other alternatives, apart from the command already suggested, are: Reinstall Composer PHP extension (but it'll remove information about all scanned...

Glad to hear the issue is sorted. Could you please confirm the configuration of the websites you experienced the issue with prior the migration. More specifically the "Apache & Nginx Settings". When you say served by Apache, I would guess that you mean proxy mode enabled, am I right?

Hi, @dijitul . As per the documentation, there is no option there's no option to use a specific SSL/TLS certificate for mail with Courier, so this is somehow expected:

Hello, @InnoDIGI . Could you please try running the repair utility for the domain affected by the issue: plesk repair mail example.com That should update the Plesk database and SQlite database /var/lib/plesk/mail/outgoing/data.db in case there's some inconsistency.

@InnoDIGI , this appears to be local issue. I am unable to replicate it and there are recent open tickets in our team's processing queue. Have you tried submitting the ticket using another browser? If the issue persists on more than one browser could you please take a screenshot (blurring the...

@MHC_1 , please execute the repair utility for the domain names related to the issue and let us know if it returns any errors: plesk repair mail -v example.com -y

Hello, @mariodieck . Could you please try increasing the timeout and execution period according to this article: https://support.plesk.com/hc/en-us/articles/12377534030871-An-operation-fails-in-Plesk-upstream-timed-out-110-Connection-timed-out-while-reading-response-header-from-upstream Once...

@derchris , could you please run the following command and save the output: sa-learn --dump magic Then move messages to spam or vice versa depending on your situation - re-run the aforementioned command and compare the token count. It is supposed to go up if training is working.

Hello, @ic3_2k . Could you please try manually killing those processes: ps auxf | grep awstats.pl kill PID If the issue reoccurs next time the Awstats process runs, please provide us with the content of /etc/awstats/awstats.model.conf

The behavior was recognized as a bug identified with ID PPPM-15223. At this point, I cannot provide an ETA for the fix. Thank you once again for bringing in to our attention.