Archive for December, 2007

OSTube Installation Error.

Sunday, December 9th, 2007

OSTube Installation Error : The command line version of PHP could not be found. Please make sure that the cli version is installed, and that mysql.so is also activated for the cli.

Solution :
This error is generally caused due to - OpenBase Dir Enabled.

Login to WHM >> Security Center –
PHP open_basedir Tweak >>

Click the check box in front of domain for which you wish to Exclude Protection.

Then Save it.

PHPMOTION - Fatal error: phpSHIELD Loader - script loader checksum error [17] Encoded script was modified in

Sunday, December 9th, 2007

If you are getting an error with PHPshield or you are getting a “blank screen” read below.

This means you did not upload in Binary mode. The following files must be uploaded in binary

1) All files in the phpshiled folder

2) The file classes/config.php

If you FTP program has a function to set transfer mode, you should set to “binary” when you upload the files mentioned above. The main problem is that while you ftp program may correctly know that the files in the phpshield folder must be uploaded in binary, when it comes to the config.php file, because its a php file you ftp program will most likely upload it in ascii format. While this is ok for all other php files, config.php needs to be uploaded in binary.

Warning: dl() [function.dl]: Not supported in multithreaded Web servers

You need to turn off/disable Thread Safety this is done in your php.ini file on your server. If you dont have access to your server via SSH then ask your web host to do disable it for you.

extension_dir does not exists /usr/lib/php/extensions/no-debug-non-zts-200343.......

Your PHP was not setup correctly. There is a folder missing on your server. All you need to do is create a folder with the same given in your error message on your server. You will need SSH access to do this, or ask your host to do it. This directory ( Extensions directory) needs to actually exist on the server.


Warning: dl(): Dynamically loaded extensions aren't enabled

You need to set the value enable_dl On (i.e.enable_dl On ) in your php.ini file on your server. You need SSH access to change this file. If you don’t have such access, ask your web host to do it for you.

Any other errors you get mean that you are running your PHP in safe_mode On this needs to be set to safe_mode Off in your php.ini file

Warning: dl() has been disabled for security reasons in

The dl() function has been added to the list of disabled function on your server. You need to enable this (by removing it) in your php.ini file on the server.

BLANK SCREEN - when you load the setup or any other page

If you are getting a blank screen then you actually have any one of the problems above but your server is set to not show error notifications so you can see which error you are getting.

Solution:

The following files must be uploaded in binary

1) All files in the phpshiled folder

2) The file classes/config.php

The phpSHIELD loader has not been installed, or is not installed correctly

If you are getting this error and you know you have all the correct files uploaded etc, then you may want to check that your domain name is not setup on your server using capital letters.

Example: PhPMotion.com if this is how your domain name looks like in your control panel or on your server then you will get errors. Linux is case sensitive and domain names (hosting accounts) should not be created using capital letters. So delete the hosting account and recreate it with NO CAPS e.g. phpmotion.com

How to remove and uninstall or disable ModSecurity (mod_security)

Sunday, December 9th, 2007

ModSecurity is an open source embeddable web application firewall, or intrusion detection and prevention engine for web applications. ModSecurity provides protection from a range of attacks against web applications and allows for HTTP traffic monitoring and real-time analysis with no changes to existing infrastructure, by operating as an Apache Web server module mod_security or standalone, and thus increase web application security. However, mis configured or overly strict rule sets, ModSecurity may cause your website to return various errors such as HTTP 403 Forbidden error or access denied error, login problems, or HTTP 412 Precondition Failed error, or HTTP 406 Not Acceptable error and other false positive symptoms.

To make matter worse, the configuration of ModSecurity rules and filters have to be done manually. Although there are free predefined certified rule set which can be used with ModSecurity out of the box, however the rule sets may be not suitable for each and every environment and may interfere with the operation of websites or blogs, and customizing and modifying the rules may be too sophisticated or complicated for some users. And for some websites that hosted on shared hosting service, the mod_security may be enable by default without options. So in this case, the best solution or workaround for mod security related issues is to disable mod_security filtering and rules.

If you’re using Apache web server (which mostly do), mod_security can be disabled by adding a specific in .htaccess file. Locate the .htaccess file in Apache web root directory (public_html or /var/www/ or others), if it does not exist, create a new file named .htaccess, and add in the following code:

SecFilterEngine Off
SecFilterScanPOST Off

The above entries in the .htaccess will disable the ModSecurity (mod_security) module for the domain.

Uninstallation of ModSecurity (mod_security) from Apache module

The easiest way to remove and uninstall mod_security is to comment out or delete the related mod_security entries from httpd.conf Apache configuration file. The lines that should be removed include:

AddModule mod_security.c
LoadModule security_module modules/mod_security.so
Include “/usr/local/apache/conf/modsec.conf” This line may be different depending on what variant of Linux or Unix you used and the installation location

Save the httpd.conf and restart the Apache. ModSecurity will not be loaded and as if uninstalled.

If you’re using WebHost Manager (WHM), uninstallation is even simpler. Just scroll to cPanel section, and click on Addon Modules. Then scroll to module named modsecurity. It should be checked Install and Keep Updated currently. Just click on Uninstall to remove the mod security feature from Apache web server.

Taken from mydigitallife.info