Search results

By default, when running Plesk-Roundcube 1.6.0 on Obsidian 18.0.55 it still defaults to PHP 8.0.* despite, Plesk itself (& everything else) being upgraded to run on later PHP releases. IF a removal of PHP 8.0.* is attempted (in our case, because we don't need that older & very soon to be no...

After THIS previous (but different) issue with these, which even the excellent Plesk Support Team couldn't identify the true cause of, suddenly fixed itself (after some minor, in theory, unconnected Plesk point updates on the previous main release), we now have another mysterious one, which also...

As per the title really ;) This warning, is only received (daily) via the panel generated (warning) e-mail. Any updates made via CLI run perfectly with no errors or issues at all. There's no trace of the warnings / errors within any of the logs here: /var/log/plesk or here...

We use the Juggernaut Firewall on our Cloud Servers, not the Plesk Firewall (you can't use both at the same time). Very happy with the performance from this Application, especially for its active use against DDoS attacks and geo-location banning, but the issue that we have, ironically, is with...

This started earlier with an e-mail notification: Followed by additional e-mail notifications: Whilst in the Plesk WebUI Interfaces, we have: Action log: The "Updates source and installation settings" section (within Plesk / Update Settings) is unmodified and correct, however the "summary"...

We've moved all of our web applications onto PHP 8.2.0 ( It became available as per the Plesk Changelog HERE ) No issues or problems with this & all good. The only applications that we have still running, the now EOL, PHP release of 7.4.* are Plesk itself plus some of the associated Plesk...

As per the thread title, but also taking into account THIS Plesk Support Article, which gives detailed guidance on Dist-Upgrades... We've got a couple of these to do shortly, so just asking before we start: Has anybody done exactly this (thread title) very recently? ;) If so, did you experience...

We have IONOS Cloud servers, all are idenical main specs (forum signature), but hosting different domains & some have different 3rd party packages on them. We have usuable backups of all, taken prior to theses issues becoming known, so can recover using those, if needs be. Only one server is...

We have one domain, that uses third party apps that have an issue with PHP 7.4.29. The issue was not present in PHP 7.4.28 and will (in theory) be fixed in time to use with PHP 7.4.30 as/when that's released. There have been previous posts where it was possible to do this (this one is an exmple)...

Username: TITLE Plesk 360 - Default Mis-Configuration(s) PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.41 MU # | Ubuntu 20.04.3 LTS | Nginx 1.20.2 | Apache2 2.4.41 (Ubuntu Backported) | - NB The Only Relevant Factors Are The Plesk Release & The OS PROBLEM...

We set up Plesk 360 when it first was offered. So far, it's all been good. Today, we've had lost of warnings (via Plesk's Spam Assassin) due to the sender's IP Addresse(s) that has been used, already being on certain blocklists These came from Plesk 360, but... the original e-mails (with the...

MTA-STS (reference link) is not (yet!) a current function within Plesk. It's been sat in the Plesk User Voice area for years, but has not been progressed. It should be relatively straightforward to apply (certainly on a non-Plesk controlled server), but has anybody actually worked this right...

Username: learning_curve TITLE Roundcube 1.4.11 run on Obsidian 18.0.37 #MU 1 STILL defaults to PHP 7.3.* not PHP 7.4.* - Why? PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.37 #MU 1 / RoundCube 1.4.11 / Any OS PROBLEM DESCRIPTION The complete problem is...

Username: learning_curve TITLE The default PHP version specified for webmail use (Roundcube in this caser) is out of date/out if synch with the rest of Plesk Obsidian PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.36 / Plesk Roundcube...

By default, when running Plesk-Roundcube 1.4.11 on Obsidian 18.0.35 it still defaults to PHP 7.3.27, yet, Plesk itself was upgraded from PHP 7.3.27 to PHP 7.4.16, as part of the upgrade from Obsidian 18.034 > Obsisidan 18.0.35... Officially, only Roundcube 1.5.* onwards will run on PHP 7.8.* so...

The question has been asked before by others: Question - fail2ban update because it was last updated, prior to Obsidian being upgraded to General Release status: Change Log for Plesk Obsidian yet there's still no sign or inclination, that this well overdue update, will be arriving anytime...

We're currently running Ubuntu 18.04.5 LTS but can easily upgrade to Ubuntu 20.04.1 LTS via official Ubuntu upgrade packages without any problems - apart from Plesk Obsidian ;) An official Plesk guide to carrying out an Ubuntu 18.04 > 20.04 Dist Upgrade, whilst Obsidian remains active and in...

On one of the many different Plesk pages / articles / forum threads, that discuss Ubuntu OS Dist-Upgrades, Plesk, via this message from Anton Maslov >> Ubuntu 18.04 support in Plesk advised that a "guide" to making a dist-upgrade for Ubuntu OS users, whilst retaining their current Plesk Obsidian...

IPv6 banning within Fail2Ban has been supported in Obsidian since way back HERE but like many people, we didn't upgrade from Onyx, until Obsidian attained General Release status, so we're a little slow posting this question. Now, with an up to date Obsidian install, we have Fail2Ban 10.3.1...

A simple 'hats off' post to Plesk, because for us, this upgrade is without doubt, the best so far. We tried an earlier preview Obsidian release, but there was still a few bugs present back then, plus we were pretty keen to upgrade, only when TLSv1.3 was fully suported within sw-cp-server i.e...