Search results

Your help article (the one linked) still tells people to modify a file which will be rolled back shortly afterwards.

We're seeing the exact same behaviour when using Redis with Joomla. The 7.3.19 to 7.3.20 update results in the exact same temporarily unavailable message the others are experiencing. Switching down to 7.1 or disabling Redis negates the error. The Argon fix above hasn't resolved the problem in...

Then it's highly misleading. The point of synchronizing to a plan is that the subscription's settings are updated / locked to match the service plan.

TITLE: Plesk Doesn't Synchronise Mail Service Status With Service Plan PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE: Plesk 17.0 and 17.8 tested, Linux CentOS 7.6, x86_64. PROBLEM DESCRIPTION: Plesk doesn't appear to synchronise the mail service status of a service plan to the attached...

Just wanted to point out for anyone else finding this thread that UFHH01 is misreading the bug-report table. 2.4.7 in this instance is the version that the bug was logged against, NOT the version that the issue was fixed in. It was actually fixed in 2.4.25.

Relying on broken behaviour is never a good idea though. If you need a list of those sites then the migration manager tells you what they are beforehand.

Plesk Migration Manager doesn't obey the currently configured Plesk PHP-Handlers and will assign domains to handlers which are currently disabled. For example, the migration manager shows: ======================== The PHP handler 5.5 mod_php (id=module) is not available on the destination...

17.0 (17.5 isn't showing up in late adopter yet).

We're seeing this on Plesk 17. No-one's modified the permissions on these folders (as they simply don't have access to them). Can you confirm that this is indeed a Plesk bug and that it'll be fixed in a microupdate?

None of these answers seem to be correct: Current Plesk is adding a line to "/root/.bash_profile" which is what includes the /root/.plesk_banner file, so you'll want to delete that include and then delete the .plesk_banner file as well. Disabling the SSH motd wouldn't make any sense (that just...

Ok, we may confusing a few things here. Ignore anything about php.ini, all we're discussing here is raising "pm.max_children" globally when using PHP-FPM with Plesk's own multi-PHP version setup, for all domains, be they existing domains or domains that may be added in future. Nothing more. Is...

Sorry, ignore my vhost comment, I was referencing the wrong document by accident (I meant the /opt/plesk/php folder, not the vhost PHP override). Anyway... Plesk uses /opt/plesk/php/(PHP Version)/etc/php-fpm.d/(Domain).com.conf for the php.ini overrides (nothing in /etc/php gets used unless...

/etc/php* isn't relevant here as those values aren't used on the "per domain PHP version" type setups. The PHP config file /var/www/vhosts/system/(domain)/conf/php.ini is the one that need to be edited, but these don't exist until someone has created that domain. In short, we know HOW to raise...

So, is there a way to do this globally yet? 5 per domain by default is painfully low and having to manually create one of these files every time someone makes a domain is obviously unreasonable.

That's actually a different issue, that's a race condition between IPv4 and IPv6 on the RedHat bug tracker. The original issue is that the Nginx service doesn't wait for the network to come up and will fail if it's not up when it tries to start, so network.service needs to be...

We've just had a customer experience this issue. The KB (https://kb.plesk.com/en/125971) states that it applies to 11.5 and is fixed by upgrading to Plesk 12, but they're already on 12.5 (although they migrated from hardware running 11.5). Is there some proper "automated fix" once someone is on...

In this instance the user wanted a wildcard SSL certificate in place for multiple different hosting accounts, thus the only way to achieve this was to allocate the certificate to the IP and then the respective subscriptions that will use it, to that same IP.

That doesn't do what we needed to do; We can enable and disable SSL fine and you can change certificates fine. What you can't do is set the certificate to "Not Selected". We need SSL to remain enabled (as there's an SSL at the IP level that should be used) so we need to remove the assigned...

Alright, DB hax seemed to work here. Removed it manually from the DB then went back into Plesk and hit OK on the various hosting pages to make sure it saved the new "no certificate" configuration properly in the various places. Command for reference was: UPDATE hosting SET certificate_id = 0...

We're trying to remove an SSL certificate from a domain but can't. Trying to remove it results in the error that it's currently assigned, which is fine because it is. The problem lies in the fact that it cannot be unassigned. Going to "Website Scripting and Security" shows "Enable SSL Support"...