Search results

you need to adjust this a bit more - this should work [ -x /usr/lib64/plesk-9.0/maxlifetime ] && [ -d /var/www/vhosts/[REDACTED]/whmcs-php-temp ] && /usr/lib64/plesk-9.0/php_session_cleaner /var/www/vhosts/[REDACTED]/whmcs-php-temp $(/usr/lib64/plesk-9.0/maxlifetime) there is no need and real...

Cleaning of PHP session is a task that PHP can't do properly itself, so in most cases your OS automatically creates a cronjob for that, if you install PHP on your server. For example on Debian/Ubuntu it's /etc/cron.d/php that cleans up old session every 30 minutes. (automatically checks for...

I see two possibilities: a) your exclusion of this directory does not work, i.e. is not configured properly (having played with excluded directories for the Plesk backup myself in the past, I can tell that this is a big PITA to get it right....and the documentation does not really help) b)...

You sure about that? 70k files can be listed in a matter of 1-2 minute on even the slowest systems/harddisks I know and on faster servers this takes a second or less. For me it all sounds like you have millions of files (possibly all zero or very few byte in size) in at least one subdirectory of...

a) this file does not look like a "default" main.cf configuration file on a Plesk server....or it's already very heavily customized. b) if you don't have a "relayhost =" line in that file, you can simply add it. Best you run "postconf -f | grep relayhost" first, before you make any changes, to...

You need to make these changes manually via SSH See also https://support.plesk.com/hc/en-us/articles/360000947494-Is-it-possible-to-configure-relayhost-in-Plesk-with-Postfix- for some more information regarding this topic As like every MTA, the postfix/qmail service on your Plesk server...

This is not possible as it's not the way "sending email" works What you are looking for is a relayhost configuration - with or without authentication, that depends on the server/smarthost you are using. i.e. something like this in /etc/postfix/main.cf smtp_sasl_auth_enable = yes...

I've changed the following three params in /etc/postfix/main.cf The first two allow all TLS version supported by your postfix/openssl (except SSLv2 and SSLv3) and the third adjusts the available cipher suites. (without them, TLS 1.0 and TLS 1.1 do not work properly)...

Mail data gets backuped incremental as well, I don't know why the notes state otherwise. Maybe this comes from a time when Plesk used the mbox format (but did they really ever do so?) for storing emails on the server?

If it's only for one/few subscription, you could also: 1) disable PHP for all domain/subdomains but one of that subscription in the Plesk panel 2) use the "Additional Apache directives" on the other domain/subdomains to add PHP back and "link" it to the FPM pool of the "primary" domain, i.e...

No, this is not possible. Every domain/subdomain does use it's own fpm pool, regardless of using dedicated PHP-FPM handler or not.

Install the Panel.ini Editor Extension to make these changes. You also need to rebuild the nginx configuration files after "blacklisting" these IPs (you can use the "Webserver Configurations Troubleshooter" Extension for that)

You guys really! overestimate the risk of using older and no longer supported PHP versions. In my opinion, running the Plesk Panel software with an old PHP version poses virtually zero risk factors. I can somewhat get behind the idea of not offering outdated PHP versions for customers/websites...

Did you guys have the xDebug module for PHP active? If yes, does the PHP7.4.33 performance revert back to normal, if you disable it?

1) get a fully featured trial license for migration: https://support.plesk.com/hc/en-us/articles/7931600293266-How-to-get-Plesk-Web-Host-edition-trial-license-for-migration 2) install webalizer component for Plesk or ignore this warning (if you want to use/have AWstats only...like we do) 3)...

Just to document here in case anyone else if ever looking for the possibility to disable the redirect/copy to option in Roundcube. I was looking into that, because these sieve redirects circumvent the SRS filter of Plesk and thus will cause SPF troubles. in...

The web application firewall has nothing to do with your problem. Plesk does also not block outgoing ports (and surely not 25), so I assume that your hosting provider does block it. Most likely it's their default policy to prevent spam outbreaks from poorly maintained servers in their network...

The (default) PHP session lifetime (session.gc_maxlifetime) is 1440 minutes. So you can safely remove all files from within /var/lib/php/session that are older than one day, as older ones are invalid and no longer used by PHP anyway.

you cannot increase the number of inodes on an existing volume, so there are three options 1) delete some files/directories 2a) backup your data 2b) delete disk/volume 2c) create new and bigger (automatically provides more inodes) disk or format partition with appropriate options to support...

For our last server migration I've sent a support request to Plesk licensing and they provided us with a four week full-featured trial license. Yeah, requires a "manual" intervention to get the same result (well, a bit more in our case, as 4 weeks came in quite handy) as we had out the box...