Search results

The only workaround we can suggest until the bug fix is released is to is to add the overflow: visible style to the element with the scrollable-list-wrapper class. This can be done through the browser's developer tools. 1. Hover over the table, right click and choose the "Inspect" option. 2...

Hello, @nmdpa3 . Thank you for the input. I have forwarded your feedback to the team that manages our technical documentation. I will follow-up with more details as soon as possible.

@marcDE I discussed the case with the team in charge and they agreed to increase the priority of task. However, I still cannot provide any ETA on when it will be implemented.

Thank you for the additional details, @klowet . I was able to replicate the issue and forwarded it to our engineers for further review. At this point, they recommend to avoid converting our repositories through apt modernize-sources. In case that has been already performed, the workaround is to...

Hi, @amayen . Thank you for the update. My guess is that the update process was not properly finished, which resulted in the reported errors. What you can try is cleaning the duplicate packages and re-attempting the update...

@WebHostingAce , the release is scheduled for for the beginning of January.

Hi, @simone.ceschi@tiscali . The reference in the changelog is for the introduction of MariaDB 11.8 in Plesk. Our team is working on introducing support for it in Performance booster as well. The ETA is Q1 of 2026. Thank you in advance for your patience.

@klowet , the reason for sticking to the old format is to use unified approach for all supported Debian-based OSes. Is there any real issue you have experienced? I can log an internal task for further check if you can provide some additional details on the impact. Thank you in advance.

As @scsa20 mentioned, DEB822 is not yet enforced and .list is still supported. Anyhow, I will confirm with our team why it is used over DEB822 and follow-up with more details.

Hi, @Andreas Mause . I don't believe the SSL setting has any relation to the reported error. The primary thing is that the connection cannot be established on the specified address. I am assuming that represents external IP address, so that's very likely the reason for the failure.

Hi, everyone. I just want to add that our team reviewed this matter and, unfortunately, there is no way to change the repository used to obtain MariaDB packages within the scope of the MariaDB update tool. Thus, apart from the manual upgrade option, the only other alternative is to wait until...

Hello, @mariodieck . Is the database in question considerably large and can you confirm how exactly are you attempting to restore it, please?

Hello, @amayen . There might be duplicate packages left after the upgrade. Could you please run the following command to check: yum check

Hello everyone! If you are a U.S.-based freelancer or agency doing SEO or WordPress client work we would like to hear from you. Our team is opening the final round of applications for the XOVI U.S. Pilot. You’ll get full access to XOVI PRO + AI Signal for 2 months, and participants can earn...

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.