HM2K.com » cPanel http://www.hm2k.com The research of an internet entrepreneur and IT consultant Thu, 25 Feb 2010 22:02:20 +0000 http://wordpress.org/?v=2.9.2 en hourly 1 Domain example.com has exceeded the max emails per hour (200) allowed. Message discarded. http://www.hm2k.com/posts/domain-example-com-has-exceeded-the-max-emails-per-hour-200-allowed-message-discarded http://www.hm2k.com/posts/domain-example-com-has-exceeded-the-max-emails-per-hour-200-allowed-message-discarded#comments Wed, 15 Jul 2009 15:34:36 +0000 hm2k http://www.hm2k.com/?p=426 Got this error with cpanel?

Domain example.com has exceeded the max emails per hour (200) allowed. Message discarded.

The fix is simple…

echo example.com=10000 >> /var/cpanel/maxemails

The result is this:

root@server [/]# cat /var/cpanel/maxemails
# If you update this file you must run /scripts/build_maxemails_config
example.com=10000

Change “example.com” for your domain and change “10000″ for your max. Don’t forget to run the script.

Enjoy!

]]> Got this error with cpanel?

Domain example.com has exceeded the max emails per hour (200) allowed. Message discarded.

The fix is simple…

echo example.com=10000 >> /var/cpanel/maxemails

The result is this:

root@server [/]# cat /var/cpanel/maxemails
# If you update this file you must run /scripts/build_maxemails_config
example.com=10000

Change “example.com” for your domain and change “10000″ for your max. Don’t forget to run the script.

Enjoy!

]]> http://www.hm2k.com/posts/domain-example-com-has-exceeded-the-max-emails-per-hour-200-allowed-message-discarded/feed 1 suPHP and .phps PHP code highlighting support http://www.hm2k.com/posts/suphp-and-phps http://www.hm2k.com/posts/suphp-and-phps#comments Thu, 17 Jul 2008 12:27:12 +0000 hm2k http://www.hm2k.com/?p=214 Today a user on one of my web servers asked me why .phps files would only download and not show the highlighted PHP code as expected.

This is usually done by adding the following to your “httpd.conf”…

AddType ‘application/x-httpd-php-source’ .phps

We use the cPanel web hosting control panel and to improve security cPanel recommend using suPHP, which allows PHP scripts to run as a user rather than “nobody”.

This means that adding the above line to “httpd.conf” does not work with suPHP.

So what can be done?

The official word is located in the suPHP FAQ, which says:

Does suPHP support code highlighting by using the “.phps” extension?

suPHP itself has no support for code highlighting. The main reason is that PHP-CGI does not support any input parameter to activate code highlighting. However there is a solution based on a small PHP script and some rewrite rules. You can find the discussion at http://forums.macosxhints.com/archive/index.php/t-23595.html.

So I decided to checkout the suggested link.

I noticed that even though the FAQ suggested using rewrite rules, the forum did not provide any kind of working solution.

Using the PHP code supplied, and a bit of rewrite ingenuity we can get this working as expected.

First, create a file called “phpsource.php”, in this file paste the following code:

<?php
if (substr($_GET['file'],strpos($_GET['file'],’.')) == ‘.phps’) {
highlight_file($_GET['file']);
}
?>

Then, in your “.htaccess”, paste the following code:

RewriteRule ^(.+\.phps)$ phpsource.php?file=$1 [L]

Note: If you don’t already have rewrites turned on in your “.htaccess” file, you will also need the line “RewriteEngine On” at the top.

What this will do is pass all “.phps” files through your “phpsource.php” script, and output a highlighted version.

The benefits of this solution is that it’s portable (will work on any server); it won’t(/shouldn’t) break when you upgrade apache or PHP; it’s pretty secure as it’ll only handle .phps files, as expected; it’s quick and effective.

]]> Today a user on one of my web servers asked me why .phps files would only download and not show the highlighted PHP code as expected.

This is usually done by adding the following to your “httpd.conf”…

AddType ‘application/x-httpd-php-source’ .phps

We use the cPanel web hosting control panel and to improve security cPanel recommend using suPHP, which allows PHP scripts to run as a user rather than “nobody”.

This means that adding the above line to “httpd.conf” does not work with suPHP.

So what can be done?

The official word is located in the suPHP FAQ, which says:

Does suPHP support code highlighting by using the “.phps” extension?

suPHP itself has no support for code highlighting. The main reason is that PHP-CGI does not support any input parameter to activate code highlighting. However there is a solution based on a small PHP script and some rewrite rules. You can find the discussion at http://forums.macosxhints.com/archive/index.php/t-23595.html.

So I decided to checkout the suggested link.

I noticed that even though the FAQ suggested using rewrite rules, the forum did not provide any kind of working solution.

Using the PHP code supplied, and a bit of rewrite ingenuity we can get this working as expected.

First, create a file called “phpsource.php”, in this file paste the following code:

<?php
if (substr($_GET['file'],strpos($_GET['file'],’.')) == ‘.phps’) {
highlight_file($_GET['file']);
}
?>

Then, in your “.htaccess”, paste the following code:

RewriteRule ^(.+\.phps)$ phpsource.php?file=$1 [L]

Note: If you don’t already have rewrites turned on in your “.htaccess” file, you will also need the line “RewriteEngine On” at the top.

What this will do is pass all “.phps” files through your “phpsource.php” script, and output a highlighted version.

The benefits of this solution is that it’s portable (will work on any server); it won’t(/shouldn’t) break when you upgrade apache or PHP; it’s pretty secure as it’ll only handle .phps files, as expected; it’s quick and effective.

]]> http://www.hm2k.com/posts/suphp-and-phps/feed 3 Storing mySQL database settings for php and perl in one file http://www.hm2k.com/posts/storing-mysql-database-settings-for-php-and-perl-in-one-file http://www.hm2k.com/posts/storing-mysql-database-settings-for-php-and-perl-in-one-file#comments Fri, 29 Feb 2008 11:36:10 +0000 hm2k http://www.hm2k.com/posts/storing-mysql-database-settings-for-php-and-perl-in-one-file I have a situation where there’s two scripts.

  1. The main core of the code which is PHP based.
  2. A perl script which is called by the mail server for parsing incoming mail.

Both of these scripts require database access to the same database.

Previously the solution would be to have two separate files both containing effectively the same information. This is less than ideal, nobody wants settings in two places.

Some have suggested using SETENV with apache, however although this would work fine for the PHP aspect, it wouldn’t work for the perl script as it’s not called via apache.

Some have suggested using ini files, then using parse_ini_file for php, and the ini parser module in perl. My problem with this was that because ini files read as plain text, it becomes a security problem. It is argued that you could deny access using apache’s “.htaccess”, or put the file outside of the web directory (usually public_html). I didn’t think this was suitable.

After some thought, and a little assistance I propose the following solution:

Create settings.pl:

#!/usr/local/bin/perl

$db_type = ‘mysql’;
$db_host = ‘localhost’;
$db_name = ”;
$db_user = ”;
$db_pass = ”;

Hey presto, we now have 1 settings file that works for both perl and PHP.

Note: If you’re using strict in perl, you’ll need to define the variables before you include the settings file, otherwise it will complain.

The problem is that php won’t evaluate the code, so we need to create another file, that will read the settings and evaluate them for use with PHP.

Create settings.php

<?php

$c = file_get_contents(’settings.pl’);
eval($c);

?>

Problem solved. Enjoy!

Update: After some discussion it was suggested that another way would be to create an ini file, and simply rename it to a file that has a handler in your httpd (such as .pl or .cgi NOT .php as PHP would render it as plain text), then in perl you can use the parser such as Config::INI to read the file and in PHP use parse_ini_file(). The obvious downside to this is the additional overheads that the above method simply does not have. If you have a large amount of settings, it might be worth it.

]]> I have a situation where there’s two scripts.

  1. The main core of the code which is PHP based.
  2. A perl script which is called by the mail server for parsing incoming mail.

Both of these scripts require database access to the same database.

Previously the solution would be to have two separate files both containing effectively the same information. This is less than ideal, nobody wants settings in two places.

Some have suggested using SETENV with apache, however although this would work fine for the PHP aspect, it wouldn’t work for the perl script as it’s not called via apache.

Some have suggested using ini files, then using parse_ini_file for php, and the ini parser module in perl. My problem with this was that because ini files read as plain text, it becomes a security problem. It is argued that you could deny access using apache’s “.htaccess”, or put the file outside of the web directory (usually public_html). I didn’t think this was suitable.

After some thought, and a little assistance I propose the following solution:

Create settings.pl:

#!/usr/local/bin/perl

$db_type = ‘mysql’;
$db_host = ‘localhost’;
$db_name = ”;
$db_user = ”;
$db_pass = ”;

Hey presto, we now have 1 settings file that works for both perl and PHP.

Note: If you’re using strict in perl, you’ll need to define the variables before you include the settings file, otherwise it will complain.

The problem is that php won’t evaluate the code, so we need to create another file, that will read the settings and evaluate them for use with PHP.

Create settings.php

<?php

$c = file_get_contents(’settings.pl’);
eval($c);

?>

Problem solved. Enjoy!

Update: After some discussion it was suggested that another way would be to create an ini file, and simply rename it to a file that has a handler in your httpd (such as .pl or .cgi NOT .php as PHP would render it as plain text), then in perl you can use the parser such as Config::INI to read the file and in PHP use parse_ini_file(). The obvious downside to this is the additional overheads that the above method simply does not have. If you have a large amount of settings, it might be worth it.

]]> http://www.hm2k.com/posts/storing-mysql-database-settings-for-php-and-perl-in-one-file/feed 2 Installing IonCube Loader with cPanel on CentOS http://www.hm2k.com/posts/installing-ioncube-loader-with-cpanel-on-centos http://www.hm2k.com/posts/installing-ioncube-loader-with-cpanel-on-centos#comments Tue, 09 Oct 2007 01:13:46 +0000 hm2k http://www.hm2k.com/posts/installing-ioncube-loader-with-cpanel-on-centos There seems to be limited details of how this is done. It’s fairly simple to be honest, but I felt it could save somebody some time if it was documented.

In case you were wondering IonCube is a PHP encoder, usually used to stop people stealing your PHP code when you distribute it. Consequently to run the encoded PHP you require a “loader”, which will run it correctly.

If your server does not have IonCube loader installed these are the steps you need to take.

  1. Visit the IonCube loader page and choose a download for your operating system.
    • In this case we will be selecting the Linux (x86) “.tar.gz” download for CentOS 4.
  2. Use “cd” to go to your home directory (usually /root).
  3. You need to download the file, issue: wget http://downloads2.ioncube.com/loader_downloads/ioncube_loaders_lin_x86.tar.gz
  4. Next, extract the files from the tarball, issue: tar zxvf ioncube_loaders_lin_x86.tar.gz
  5. We now need to move the directory to the correct path, issue: mv ioncube /usr/local
  6. Next we need to change our active directory, issue: cd /usr/local/ioncube
  7. We now need to find out where the “php.ini” is stored, issue: php ioncube-loader-helper.php page=install-assistant
    • You should see something similar to “<code>/usr/local/Zend/etc/php.ini</code>”.
    • Also take note of the part that says “ioncube_loader_lin_4.4.so” we will use this file later.
  8. Next we need to edit the file, issue: nano /usr/local/Zend/etc/php.ini
    • You can use any editor you like such as nano/pico or vi if you know what you’re doing.
  9. Find (ctrl+w) the “[Zend]” section of the “php.ini”, above the “zend_extension” line, place: zend_extension = /usr/local/ioncube/ioncube_loader_lin_4.4.so (followed by ctrl+x, Y then enter if using pico or nano).
  10. Finally issue: service httpd restart
]]> There seems to be limited details of how this is done. It’s fairly simple to be honest, but I felt it could save somebody some time if it was documented.

In case you were wondering IonCube is a PHP encoder, usually used to stop people stealing your PHP code when you distribute it. Consequently to run the encoded PHP you require a “loader”, which will run it correctly.

If your server does not have IonCube loader installed these are the steps you need to take.

  1. Visit the IonCube loader page and choose a download for your operating system.
    • In this case we will be selecting the Linux (x86) “.tar.gz” download for CentOS 4.
  2. Use “cd” to go to your home directory (usually /root).
  3. You need to download the file, issue: wget http://downloads2.ioncube.com/loader_downloads/ioncube_loaders_lin_x86.tar.gz
  4. Next, extract the files from the tarball, issue: tar zxvf ioncube_loaders_lin_x86.tar.gz
  5. We now need to move the directory to the correct path, issue: mv ioncube /usr/local
  6. Next we need to change our active directory, issue: cd /usr/local/ioncube
  7. We now need to find out where the “php.ini” is stored, issue: php ioncube-loader-helper.php page=install-assistant
    • You should see something similar to “<code>/usr/local/Zend/etc/php.ini</code>”.
    • Also take note of the part that says “ioncube_loader_lin_4.4.so” we will use this file later.
  8. Next we need to edit the file, issue: nano /usr/local/Zend/etc/php.ini
    • You can use any editor you like such as nano/pico or vi if you know what you’re doing.
  9. Find (ctrl+w) the “[Zend]” section of the “php.ini”, above the “zend_extension” line, place: zend_extension = /usr/local/ioncube/ioncube_loader_lin_4.4.so (followed by ctrl+x, Y then enter if using pico or nano).
  10. Finally issue: service httpd restart
]]> http://www.hm2k.com/posts/installing-ioncube-loader-with-cpanel-on-centos/feed 8 The requested URL /cpanel was not found on this server http://www.hm2k.com/posts/the-requested-url-cpanel-was-not-found-on-this-server http://www.hm2k.com/posts/the-requested-url-cpanel-was-not-found-on-this-server#comments Mon, 11 Jun 2007 15:40:43 +0000 hm2k http://www.hm2k.com/posts/the-requested-url-cpanel-was-not-found-on-this-server If you run cPanel servers, then you may at some point experience this issue.

The problem is when you attempt to visit “http://server.example.com/cpanel” and you get the following message or similar:

The requested URL /cpanel was not found on this server.

The requested URL /whm was not found on this server.

To fix this, you must add the following to your httpd.conf (/usr/local/apache/conf/httpd.conf):

ErrorDocument 400 /400.shtml
ErrorDocument 401 /401.shtml
ErrorDocument 403 /403.shtml
ErrorDocument 404 /404.shtml
ErrorDocument 500 /500.shtml
ScriptAlias /cgi-sys/ /usr/local/cpanel/cgi-sys/
Alias /sys_cpanel/ /usr/local/cpanel/sys_cpanel/
Alias /java-sys/ /usr/local/cpanel/java-sys/
Alias /img-sys/ /usr/local/cpanel/img-sys/
Alias /akopia/ /usr/local/cpanel/3rdparty/interchange/share/akopia/
Alias /neo-images/ /usr/local/cpanel/base/neomail/neo-images/
ScriptAliasMatch ^/cpanel/(.*) /usr/local/cpanel/cgi-sys/redirect.cgi
ScriptAlias /cpanel /usr/local/cpanel/cgi-sys/redirect.cgi
ScriptAlias /whm /usr/local/cpanel/cgi-sys/whmredirect.cgi
ScriptAlias /securewhm /usr/local/cpanel/cgi-sys/swhmredirect.cgi
ScriptAlias /webmail /usr/local/cpanel/cgi-sys/wredirect.cgi
ScriptAliasMatch ^/webmail/(.*) /usr/local/cpanel/cgi-sys/wredirect.cgi
ScriptAliasMatch ^/kpanel/(.*) /usr/local/cpanel/cgi-sys/redirect.cgi
ScriptAlias /controlpanel /usr/local/cpanel/cgi-sys/redirect.cgi
ScriptAlias /securecontrolpanel /usr/local/cpanel/cgi-sys/sredirect.cgi
Alias /mailman/archives/ /usr/local/cpanel/3rdparty/mailman/archives/public/
ScriptAlias /mailman/ /usr/local/cpanel/3rdparty/mailman/cgi-bin/
Alias /pipermail/ /usr/local/cpanel/3rdparty/mailman/archives/public/
Alias /interchange/ /usr/local/cpanel/3rdparty/interchange/share/interchange/
Alias /interchange-5/ /usr/local/cpanel/3rdparty/interchange/share/interchange-5/

Add this anywhere in the httpd.conf, outside of any <VirtualHost> tags.

Restart apache (service httpd restart), and bingo!

]]> If you run cPanel servers, then you may at some point experience this issue.

The problem is when you attempt to visit “http://server.example.com/cpanel” and you get the following message or similar:

The requested URL /cpanel was not found on this server.

The requested URL /whm was not found on this server.

To fix this, you must add the following to your httpd.conf (/usr/local/apache/conf/httpd.conf):

ErrorDocument 400 /400.shtml
ErrorDocument 401 /401.shtml
ErrorDocument 403 /403.shtml
ErrorDocument 404 /404.shtml
ErrorDocument 500 /500.shtml
ScriptAlias /cgi-sys/ /usr/local/cpanel/cgi-sys/
Alias /sys_cpanel/ /usr/local/cpanel/sys_cpanel/
Alias /java-sys/ /usr/local/cpanel/java-sys/
Alias /img-sys/ /usr/local/cpanel/img-sys/
Alias /akopia/ /usr/local/cpanel/3rdparty/interchange/share/akopia/
Alias /neo-images/ /usr/local/cpanel/base/neomail/neo-images/
ScriptAliasMatch ^/cpanel/(.*) /usr/local/cpanel/cgi-sys/redirect.cgi
ScriptAlias /cpanel /usr/local/cpanel/cgi-sys/redirect.cgi
ScriptAlias /whm /usr/local/cpanel/cgi-sys/whmredirect.cgi
ScriptAlias /securewhm /usr/local/cpanel/cgi-sys/swhmredirect.cgi
ScriptAlias /webmail /usr/local/cpanel/cgi-sys/wredirect.cgi
ScriptAliasMatch ^/webmail/(.*) /usr/local/cpanel/cgi-sys/wredirect.cgi
ScriptAliasMatch ^/kpanel/(.*) /usr/local/cpanel/cgi-sys/redirect.cgi
ScriptAlias /controlpanel /usr/local/cpanel/cgi-sys/redirect.cgi
ScriptAlias /securecontrolpanel /usr/local/cpanel/cgi-sys/sredirect.cgi
Alias /mailman/archives/ /usr/local/cpanel/3rdparty/mailman/archives/public/
ScriptAlias /mailman/ /usr/local/cpanel/3rdparty/mailman/cgi-bin/
Alias /pipermail/ /usr/local/cpanel/3rdparty/mailman/archives/public/
Alias /interchange/ /usr/local/cpanel/3rdparty/interchange/share/interchange/
Alias /interchange-5/ /usr/local/cpanel/3rdparty/interchange/share/interchange-5/

Add this anywhere in the httpd.conf, outside of any <VirtualHost> tags.

Restart apache (service httpd restart), and bingo!

]]> http://www.hm2k.com/posts/the-requested-url-cpanel-was-not-found-on-this-server/feed 0