Search results

When serving PHP via the fpm handler, it will throw a (404) "file not found" error when the file requested (or it's directoy path) contains any spaces. Is there an easy workaround, except using the FastCGI handler? (or convincing the customer to not use spaces in file or directory names) I know...

ahhh, finally some other people that see this the same way as I do ;) Never understood why this should be usefull in the current implementation where the custom limit for sending emails can only be lowered from the server/default limit, as in 99.9% or all cases you really wan't it the other way...

mod_itk and/or mod_ruid2 do only work in conjunction with mod_php, so it does not work with any additional PHP version you'd like to support on your server. But yeah, FastCGI is a resource hog.... either you let these processes die again very fast, so in total they do not consume that much...

I've just used the Migration and Transfer Manager on PLESK 12 several times to migrate - 3 Resellers ~ 130 Clients ~ 300 Domains/Websites (~160GB diskspace, ~3k mailaccounts, ~300 databases) from an old Plesk 9.5 server. While both systems are virtual servers within the same ESXi serverfarm...

Why? This was never a problem till one of your latest releases. Now the PHP max_execution_time has to be set to at least 300 seconds, or the PleskPanel refuses to update Typo3 installations. It does not make sense for me, to enforce this (imho very! artificial) Typo3 recommendation limit onto...

I'm so grateful, as the current (intransparent) behaviour drove us mad. We're using powerDNS based secondarys for several of our Plesk servers, and whenever the primary DNS in the SOA record is no longer the Plesk server itself, the secondarys stop updating the zone and will even drop it after...

Nope, it's more likely that you guys screwed up and flagged the 11.5.29 release as stable. Yesterday all our Plesk 11.0 servers (running on Ubuntu 12.04) showed the upgrade message, though in the end it did not find a upgrade. (tried web and cli) Today the message is no longer shown, so I...