When installing or updating dependencies with Composer it may be possible that you see a PHP fatal error like:
$ composer update
Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 79 bytes) in phar:///usr/local/bin/composer/src/Composer/DependencyResolver/RuleWatchGraph.php on line 100
This problem has been documented in Composer on issue https://github.com/composer/composer/issues/1898 This is common when the memory limit setting of PHP is not enough for Composer needs, something that can happen . . . Read more
The location of the main apache error log is inside /var/log/apache2/error_log. This will show all diagnostic information of your Apache server. You also have access to an error log per domain. Depending on your Operating System, the location of your domain log might change. You can check the location of . . . Read more
If Apache shows the error:
VirtualHost *:80 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results
it means that your VirtualHost sections are not matching the NameVirtualHost directive in your configuration. To fix this follow these steps: Locate the directive NameVirtualHost, by default it should be something like: NameVirtualHost *:80 Look at your VirtualHost declarations, they should match the NameVirtualHost, . . . Read more
If you are using symfony or Zend Framework, most probably you are using a .htaccess file indicating apache to direct all requests for non existing files to the symfony or ZF bootstrapper which is usually index.php in the web root. If you get the above error, it is mostly probably . . . Read more
When you get the following error in the Control Panel: ERROR: PleskFatalException wrong id Additionally, an exception has occurred while trying to report this error: PleskFatalException wrong id 0: UserClient.php:19 UserClient->__construct(NULL null) 1: class.Session.php:208 Session->getUser() 2: index.php:53 Close your browser or delete your cookies and try logging in again.
There is an issue in the MongoDB PHP driver with the way it establishes connections to MongoDB servers. This issue only happens on servers that use more than 1024 file descriptors. This means that on our shared hosting servers it is possible that you may not be able to connect . . . Read more
When the web server encounters a request for a missing file, it will return a file called “not_found.html” located in your website’s “error_docs” directory. You can customize this file to match your site. Any other error you want a customized file for can also be enabled, just request support for . . . Read more
If you are getting this error, please make sure there is no svn (or name that applies to your case) directory inside httpdocs.
If you use PHP in your website, many times you may get a blank page or something does not work properly. In these cases, it helps to look at the errors generated by PHP. On ServerGrove servers, display_errors is turned off for security purposes (so errors are not sent to . . . Read more
PHP Parse error: syntax error, unexpected T_STRING in /path/project/apps/frontend/modules/module/templates/indexSuccess.php on line 1 The path above is an example of a template file on a symfony project. If your files work fine in your development server, and we you upload it to the production server you get this error, it is . . . Read more