Recent content by lemoneye

As I just replied to wildeep, this is not a Plesk issue, it is something controlled at OS level, so these are security issues with Ubuntu. The version of Plesk isn't relevant. Plesk only takes updates from official repositories, so you may need to update your server OS, depending which version...

This is dependent on the version of Ubuntu that you are running, and Ubuntu 20 has vulnerabilities from OpenSSH 8.2 and onwards. Ubuntu 24 still has some OpenSSH issues flagged, but you can demonstrate mitigation against these by making sure that you have the appropriate settings on your server...

I'm not sure if the error is due to not having an "admin" unsername, or if it is just something that didn't survive the update from Onyx to Obsidian, but either way, this is surely not a horribly complex piece of coding to fix. I agree that being able to provide colour changes, or having a...

Thank you for your speedy respnse, Sebahat. I shall report this back to my client. Please mark this closed.

I note there has been previous discussion of this in the Forums (Question - Why in plesk firehouse Aws keys are public ?), but my largest customer is flagging this as something their security people are concerned about. Why do these keys need to be exposed? What are they for, and is it possible...

I have the same issue on several servers too.

We have the same issue flagged. Description The PKCS#11 feature in ssh-agent in OpenSSH before 9.3p2 has an insufficiently trustworthy search path, leading to remote code execution if an agent is forwarded to an attacker-controlled system. (Code in /usr/lib is not necessarily safe for loading...

We ended up using a Raspberry Pi with a 2Tb drive attached as a backup solution and using the SFTP Backup extension from Plesk. We configured a subdomain to point at the IP address that the Pi is on and then use that control where backups go. In this way we retain the Plesk backup page, and it...

Currently running 5 boxes (4 Ubuntu and 1 Windows) all running Plesk Obsidian. Until now we have configured these servers to backup to a local machine to store offline backups of each entire server. However, the backup file sizes of the larger two are 50Gb and 60Gb which take significant time to...

Sorry for the slow reply - Christmas rush took over. Yes, if I look at the files in Plesk File Manager, the directories and the files in them all list the subscription as the owner. The issue is now becoming a real nuisance when running theme updates as a numberdo not update inside Plesk...

The plugins and themes were installed using the WordPress Toolkit Sets - I would assume that when you install WP and add a set it would be assigned correct subscription account permissions, but my guess is that is doesn't.

We are getting messages on 2 servers where we have created sets of themes and plugins that WordPress Toolkit installs when a new site is created. When themes or plugins installed by the toolkit are updated, the panel gives out warnings like Asset 'Divi' with version '4.7.2' has different owner...

I've just migrated from Onyx to Obsidian, and whilst it's not mission critical, it does seem odd that the Skins and Colour scheme plugin essentially now does almost nothing. Is this considered a no priority item at Plesk?