Search results

It solved the problem. Thx !

Seems to be a problem with paquets source ...

Hello, This last night i have this error while plesk tried to upgrade. Some idea ? Execution failed. Command: autoinstaller Arguments: Array ( [0] => --select-product-id [1] => plesk [2] => --select-release-current [3] => --upgrade-installed-components ) Details: Downloading...

NGINX settings are close to default. nginx -t display that : nginx: [warn] "ssl_stapling" ignored, no OCSP responder URL in the certificate "...

Hello, We have rarely but regularly the same problem on different servers. Suddenly website hosted become unvailable because there is too much redirections (perhaps after SSL certifcate renew). Clearing NGINX cache manually solve the problem imemdiatly ... Although NGINX cache lifetime is 30...

+1 for Franken PHP !

Since last friday it seems config done according these KB dont ork perfectly as before : https://developers.cloudflare.com/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/...

I mean it's easy to send a modified User-agent, harder to change an ip when sending request so it's much more secure to whitelist by ip than by User-agent. Whatever this feature is not really essential so i will perhaps disable it.

Thanks for your answer. The problem is User-Agent is not very reliable ...

Hello, i need to Whitelist Plesk service used to make site thumbnails in Plesk Backoffice ... It is blocked by our Cloudflare settings and i need to know service IP. Thanks to Plesk team to communicate on it ...

Hello, This problem is known for more than 3 months and it seems it's still not fixed in updates ...

Is this bug/problem gonna be fix in next mu ?

Hello, Since some days (perhaps 2 weeks) i have this error on lot of backup tasks : Unable to back up applications packages. Error: ODBC error #28000: [ma-3.1.20]Access denied for user 'apsc'@'127.0.0.1' Is it a bug introduced by new version ? A solution is planned ? Regards.

Yes security is a main concern today so Plesk should add up to date ruleset and specific rules to protect known CMS as Wordpress, Joomla, Drupal, Prestashop, & Magento at min.

Ok it come from that. New rules are much more restrictive. We had to switch to Comodo.

I see there was an Updated OWASP ModSecurity CRS to version 4.2.0 in 18.0.61 ... Perhaps it come from this.

Hello, Today 2 servers had Plesk upgraded to v 18.0.61mu5, and on those 2 servers we started to have lot of 403 errors returned by Modsecurity with Owasp rules. Is there some change about this ? Can it come from Nginx upgrade ? Do you have an idea ... ? We had to switch to Comodo to get back...

It's seems ok now, but i'm not sure it's because sury signing key update. There was a plesk update to 18.0.59u2, perhaps they fixed something ...

If you want to update keys and update + upgrade in one command : apt-key adv --fetch-keys https://packages.sury.org/php/apt.gpg && apt update && apt -y upgrade

Looking at log i see i had a problem with an outdated siging key for sury.org repo. So i executed this command : apt-key adv --fetch-keys https://packages.sury.org/php/apt.gpg I will see tomorrow morning if it solve the problem.