You got this error message because you have not registered all your IPs for API Access. You need to check if you have whitelisted your "whmcs domain ip" as well as the hosting server ip (if different)
See KB Article " http://www.posiblehost.com/billing/knowledgebase.php?action=displayarticle&id=172 " to resolve the issue.
Tuesday, April 28, 2015
Monday, January 12, 2015
Enable SMTP Authentication on cpanel
POP before SMTP authentication allows you to send messages via a POP mail server for 30 minutes before you will need to re-authenticate a session through SMTP.
POP before SMTP authentication is disabled in WHM by default. To enable this option, navigate to WHM’s Service Manager (Home >> Service Configuration >> Service Manager) and select the Antirelayd checkbox.
While POP before SMTP authentication is secure but if the customer will be able to check the email from an office, the current public IP belongs to that office IP has been added to email white list and any one from that network can be send email using this smtp server without any authentication for 30 minutes.
To disable the feature “Authenticate POP before SMTP” in WHM/Cpanel server by simply executing the following command.
To Enabling SMTP authentication
/usr/local/cpanel/bin/tailwatchd --disable=Cpanel::TailWatch::Antirelayd
POP before SMTP authentication is disabled in WHM by default. To enable this option, navigate to WHM’s Service Manager (Home >> Service Configuration >> Service Manager) and select the Antirelayd checkbox.
While POP before SMTP authentication is secure but if the customer will be able to check the email from an office, the current public IP belongs to that office IP has been added to email white list and any one from that network can be send email using this smtp server without any authentication for 30 minutes.
To disable the feature “Authenticate POP before SMTP” in WHM/Cpanel server by simply executing the following command.
To Enabling SMTP authentication
/usr/local/cpanel/bin/tailwatchd --disable=Cpanel::TailWatch::Antirelayd
How to install Lighttpd for FLV streaming
Lighttpd is a free web server designed for speed, with all the essential functions of a web server. The low memory footprint (compared to other web servers) small CPU load and speed optimizations make lighttpd suitable for servers that are suffering load problems, or for serving static media separately from dynamic content. You can install lighttpd as reverse proxy with apache webserver.
We can now setup lighttpd as reverse-proxy for apache.
http://pkgs.repoforge.org/lighttpd/
or
yum install lighttpd
vi /etc/lighttpd/lighttpd.conf
change lighttpd port to 81
server.port = 81
server.use-ipv6 = “disable”
server.username = “nobody”
server.groupname = “nobody”
touch /var/log/lighttpd/error.log
touch /var/log/lighttpd/access.log
chown -R nobody.nobody /var/log/lighttpd
/etc/init.d/lighttpd restart
When you get restart error like this errors then check with log file permissions.
Starting lighttpd: (log.c.118) opening errorlog ‘/var/log/lighttpd/error.log’ failed: Permission denied
vi /etc/lighttpd/modules.conf
make sure modules and including these for flv steaming…
include “conf.d/simple_vhost.conf”
include “conf.d/flv_streaming.conf”
include ” conf.d/secdownload.conf”
vi conf.d/simple_vhost.conf
example entry
$HTTP[“host”] =~ “(^|\.)www.lighttpdexample\.com:81$” {
server.document-root = “/home/cpanel/public_html/”
secdownload.secret = “vAfddsv4$%4″
secdownload.document-root = “/home/cpanel/public_html/media/videos”
secdownload.uri-prefix = “/flv/”
secdownload.timeout = 36000
flv-streaming.extensions = ( “.flv” )
h264-streaming.extensions = ( “.mp4″ )
}
or
$HTTP[“host”] != “^(fotoblow.tamilcomedy\.info)$” {
simple-vhost.server-root = “/home/username/public_html/”
simple-vhost.default-host = “fotoblow.tamilcomedy.info”
simple-vhost.document-root = “fotoblow”
}
$HTTP[“host”] =~ “(^|\.)fotoblow.tamilcomedy\.info:81$” {
server.document-root = “/home/username/public_html/fotoblow/”
}
$HTTP[“host”] =~ “(^|\.)www.cpanelkb\.net:81$” {
server.document-root = “/home/username/public_html/fotoblow/”
}
$HTTP[“host”] =~ “(^|\.)tamilcomedy\.info:81$” {
server.document-root = “/home/username/public_html/fotoblow/”
}
Then enable steaming modules.
vi conf.d/flv_streaming.conf
server.modules += ( “mod_flv_streaming”)
flv-streaming.extensions = ( “.flv” )
Normally apache will running on port 80, these entries will redirect .flv extension to port 81. Add the following code in your apache configuration.
vi /etc/httpd/conf/httpd.conf
Add the following entries blow domain config
ProxyPassReverse / http://%{HTTP_HOST}:81/
RewriteEngine on
RewriteCond %{REQUEST_URI} .*\.(gif|png|jpg|flv|mp4|mp3)$
RewriteRule ^/(.*) http://%{HTTP_HOST}:81/$1 [P]
That’s all !!!
Now restart apache webserver and check your lighttpd access logs /var/log/lighttpd/access.log.
We can now setup lighttpd as reverse-proxy for apache.
How to install Lighttpd for FLV streaming
find lighttpd rpm repositoryhttp://pkgs.repoforge.org/lighttpd/
or
yum install lighttpd
vi /etc/lighttpd/lighttpd.conf
change lighttpd port to 81
server.port = 81
server.use-ipv6 = “disable”
server.username = “nobody”
server.groupname = “nobody”
touch /var/log/lighttpd/error.log
touch /var/log/lighttpd/access.log
chown -R nobody.nobody /var/log/lighttpd
/etc/init.d/lighttpd restart
When you get restart error like this errors then check with log file permissions.
Starting lighttpd: (log.c.118) opening errorlog ‘/var/log/lighttpd/error.log’ failed: Permission denied
vi /etc/lighttpd/modules.conf
make sure modules and including these for flv steaming…
include “conf.d/simple_vhost.conf”
include “conf.d/flv_streaming.conf”
include ” conf.d/secdownload.conf”
vi conf.d/simple_vhost.conf
example entry
$HTTP[“host”] =~ “(^|\.)www.lighttpdexample\.com:81$” {
server.document-root = “/home/cpanel/public_html/”
secdownload.secret = “vAfddsv4$%4″
secdownload.document-root = “/home/cpanel/public_html/media/videos”
secdownload.uri-prefix = “/flv/”
secdownload.timeout = 36000
flv-streaming.extensions = ( “.flv” )
h264-streaming.extensions = ( “.mp4″ )
}
or
$HTTP[“host”] != “^(fotoblow.tamilcomedy\.info)$” {
simple-vhost.server-root = “/home/username/public_html/”
simple-vhost.default-host = “fotoblow.tamilcomedy.info”
simple-vhost.document-root = “fotoblow”
}
$HTTP[“host”] =~ “(^|\.)fotoblow.tamilcomedy\.info:81$” {
server.document-root = “/home/username/public_html/fotoblow/”
}
$HTTP[“host”] =~ “(^|\.)www.cpanelkb\.net:81$” {
server.document-root = “/home/username/public_html/fotoblow/”
}
$HTTP[“host”] =~ “(^|\.)tamilcomedy\.info:81$” {
server.document-root = “/home/username/public_html/fotoblow/”
}
Then enable steaming modules.
vi conf.d/flv_streaming.conf
server.modules += ( “mod_flv_streaming”)
flv-streaming.extensions = ( “.flv” )
Normally apache will running on port 80, these entries will redirect .flv extension to port 81. Add the following code in your apache configuration.
vi /etc/httpd/conf/httpd.conf
Add the following entries blow domain config
ProxyPassReverse / http://%{HTTP_HOST}:81/
RewriteEngine on
RewriteCond %{REQUEST_URI} .*\.(gif|png|jpg|flv|mp4|mp3)$
RewriteRule ^/(.*) http://%{HTTP_HOST}:81/$1 [P]
That’s all !!!
Now restart apache webserver and check your lighttpd access logs /var/log/lighttpd/access.log.
Sunday, January 11, 2015
How to reboot cpanel/whm in ssh
to restart the machine via ssh you type
/etc/init.d/cpanel restart
Enjoy!!!
/etc/init.d/cpanel restart
Enjoy!!!
Saturday, November 29, 2014
How to change main domain of a cPanel reseller account with an existing domain name?
Here are some tips on cPanel reseller account modification. It’s quite simple if the new domain you wish to set as primary of your WHM re-seller is not under the same account. It can be simply managed from the “Modify an Account” section. You can simply modify the account information from this location. As it is a re-seller, you must do the following steps after modifying the account.
Make sure that;You do not want the current domain and data. If you need it, please take backups.
Change reseller ownership of all accounts under that reseller to the new username.
Check resellers name-servers, if they are using their own.
Switch reseller priveliges to new user.
And so on.
Here I am listing some steps to changing the reseller main account that I have done few days ago for a client. His actual requirement is:
"Change the cPanel reseller account's main domain to an already existing domain under his reseller account"
Example:
He wants to set up “nextdomain.com” (already existing under his re-seller account) as main domain for his re-seller account. Also, wanted to terminate the current main domain “currentdomain.com”.
Steps:
1, I created a backup of “nextdomain.com” (The domain he actually wants to set as main domain).
2, Terminated that account “nextdomain.com” (To avoid conflict when modifying the existing domain with new).
3, Modified the existing account with new domain name, I didn’t changed the $user name. The user name change will cause problem with all his accounts’ ownership and its little complex.
4, Replaced the “public_html” contents with the data from the backup I created.
5, Also, replaced the “email” folders with new.
6, As it was a WordPress site, created a database and restored it from the backup. (Need to edit the username details in database, makes sure that you have made the necessary changes in Site URL and home in your WordPress database).
That’s it…!!
Make sure that;You do not want the current domain and data. If you need it, please take backups.
Change reseller ownership of all accounts under that reseller to the new username.
Check resellers name-servers, if they are using their own.
Switch reseller priveliges to new user.
And so on.
Here I am listing some steps to changing the reseller main account that I have done few days ago for a client. His actual requirement is:
"Change the cPanel reseller account's main domain to an already existing domain under his reseller account"
Example:
He wants to set up “nextdomain.com” (already existing under his re-seller account) as main domain for his re-seller account. Also, wanted to terminate the current main domain “currentdomain.com”.
Steps:
1, I created a backup of “nextdomain.com” (The domain he actually wants to set as main domain).
2, Terminated that account “nextdomain.com” (To avoid conflict when modifying the existing domain with new).
3, Modified the existing account with new domain name, I didn’t changed the $user name. The user name change will cause problem with all his accounts’ ownership and its little complex.
4, Replaced the “public_html” contents with the data from the backup I created.
5, Also, replaced the “email” folders with new.
6, As it was a WordPress site, created a database and restored it from the backup. (Need to edit the username details in database, makes sure that you have made the necessary changes in Site URL and home in your WordPress database).
That’s it…!!
Unable to establish a PHP session – PHPMyAdmin error
PHPMyAdmin error
Do you ever come across the following error when you access PHPMyAdmin from cPanel.
Access Denied Unable to establish a PHP session. If you believe that this is in error or inadvertent, contact your system administrator and ask them to review your server settings.
Normally, you will get this error when the permission or ownership of the tmp folder for this user is wrong. That is, make sure the ownership of /home/$username/tmp folder has ownership set to $user and permission as 755. If it is not, you will face the same problem.
Solution:
1. SSH into the server as root.
2. Check the permission and ownership of /home/$user/tmp folder. Set ownership as $user.
# chown $user. /home/$user/tmp
3. Set permission of the tmp folder to 755.
#chmod 755 /home/$user/tmp
That’s it!!!
$user can be replaced with your respective username.
Do you ever come across the following error when you access PHPMyAdmin from cPanel.
Access Denied Unable to establish a PHP session. If you believe that this is in error or inadvertent, contact your system administrator and ask them to review your server settings.
Normally, you will get this error when the permission or ownership of the tmp folder for this user is wrong. That is, make sure the ownership of /home/$username/tmp folder has ownership set to $user and permission as 755. If it is not, you will face the same problem.
Solution:
1. SSH into the server as root.
2. Check the permission and ownership of /home/$user/tmp folder. Set ownership as $user.
# chown $user. /home/$user/tmp
3. Set permission of the tmp folder to 755.
#chmod 755 /home/$user/tmp
That’s it!!!
$user can be replaced with your respective username.
Subscribe to:
Posts (Atom)