365 Hosting support | Server Management Provider

365hostingsupport ultimate source of Server Security, cPanel server management and monitoring. Since 2012 we are offering top class technical support services at lowest prices. We offer 100% Satisfaction with 7 Days Money Back Guarantee.

365 Hosting support |  Server Management Provider - 365hostingsupport ultimate source of Server Security, cPanel server management and monitoring. Since 2012 we are offering top class technical support services at lowest prices. We offer 100% Satisfaction with 7 Days Money Back Guarantee.

Deploy Bulk Email on Linux

Part 1 Install Tools

Deploy Bulk Email on Linux


Install nginx, mysql, php
Step One—Install the Required Repositories

Deploy Bulk Email on Linux

Deploy Bulk Email on Linux

We will be installing all of the required software with Yum. However, because nginx is not available straight from CentOS, we’ll need to install the epel repository.

sudo yum install epel-release


 

Step Two—Install MySQL

The next step is to begin installing the server software on the virtual private server, starting with MySQL and dependencies.

sudo yum install mysql-server

Once the download is complete, restart MySQL:

sudo /etc/init.d/mysqld restart

You can do some configuration of MySQL with this command:

sudo /usr/bin/mysql_secure_installation

The prompt will ask you for your current root password.
Since you just installed MySQL, you most likely won’t have one, so leave it blank by pressing enter.
Enter current password for root (enter for none):
OK, successfully used password, moving on…
Then the prompt will ask you if you want to set a root password. Go ahead and choose Y and follow the instructions.
CentOS automates the process of setting up MySQL, asking you a series of yes or no questions.
It’s easiest just to say Yes to all the options. At the end, MySQL will reload and implement the changes.
By default, a MySQL installation has an anonymous user, allowing anyone
to log into MySQL without having to have a user account created for
them. This is intended only for testing, and to make the installation
go a bit smoother. You should remove them before moving into a
production environment.

Remove anonymous users? [Y/n] y
… Success!

Normally, root should only be allowed to connect from ‘localhost’. This
ensures that someone cannot guess at the root password from the network.

Disallow root login remotely? [Y/n] y
… Success!

By default, MySQL comes with a database named ‘test’ that anyone can
access. This is also intended only for testing, and should be removed
before moving into a production environment.

Remove test database and access to it? [Y/n] y
– Dropping test database…
… Success!
– Removing privileges on test database…
… Success!

Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.

Reload privilege tables now? [Y/n] y
… Success!

Cleaning up…

All done! If you’ve completed all of the above steps, your MySQL
installation should now be secure.

Thanks for using MySQL!


 

Step Three—Install nginx

As with MySQL, we will install nginx on our virtual private server using yum:

sudo yum install nginx

nginx does not start on its own. To get nginx running, type:

sudo /etc/init.d/nginx start

You can confirm that nginx has installed on your virtual private server by directing your browser to your ip address.
You can run the following command to reveal your server’s IP address.

ifconfig eth0 | grep inet | awk ‘{ print $2 }’

Step Four—Install PHP

The php-fpm package is located within the REMI repository, which, at this point, is disabled. The first thing we need to do is enable the REMI repository and install php and php-fpm:

sudo yum install php-fpm php-mysql

Step Five—Configure php

We need to make one small change in the php configuration. Open up php.ini:

sudo vi /etc/php.ini

Find the line, cgi.fix_pathinfo=1, and change the 1 to 0.
cgi.fix_pathinfo=0
If this number is kept as a 1, the php interpreter will do its best to process the file that is as near to the requested file as possible. This is a possible security risk. If this number is set to 0, conversely, the interpreter will only process the exact file path—a much safer alternative. Save and Exit.

Step Six—Configure nginx

Open up the default nginx config file:
sudo vi /etc/nginx/nginx.conf
Raise the number of worker processes to 4 then save and exit that file.
Now we should configure the nginx virtual hosts.
In order to make the default nginx file more concise, the virtual host details are in a different location.

sudo vi /etc/nginx/conf.d/default.conf

The configuration should include the changes below (the details of the changes are under the config information):
#
# The default server
#
server {
listen 8001;
server_name example.com;
location / {
root /usr/share/nginx/html/email-bulk-admin/public/;
index index.php index.html index.htm;
}

error_page 404 /404.html;
location = /404.html {
root /usr/share/nginx/html/email-bulk-admin/public/;
}

error_page 500 502 503 504 /50x.html;
location = /50x.html {
root /usr/share/nginx/html/email-bulk-admin/public/;
}

# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
#
location ~ \.php$ {
root /usr/share/nginx/html/email-bulk-admin/public/;
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
include fastcgi_params;
}
}

Here are the details of the changes:
Add index.php within the index line.
Change the server_name to your domain name or IP address (replace the example.com in the configuration)
Change the root to /usr/share/nginx/html;
Uncomment the section beginning with “location ~ \.php$ {“,
Change the root to access the actual document root, /usr/share/nginx/html;
Change the fastcgi_param line to help the PHP interpreter find the PHP script that we stored in the document root home.
Save and Exit
Open up the php-fpm configuration:

sudo vi /etc/php-fpm.d/www.conf

Replace the apache in the user and group with nginx:
[…]
; Unix user/group of processes
; Note: The user is mandatory. If the group is not set, the default user’s group
; will be used.
; RPM: apache Choosed to be able to access some dir as httpd
user = nginx
; RPM: Keep a group allowed to write in log dir.
group = nginx
[…]
Finish by restarting php-fpm.

sudo service php-fpm restart

Step Seven—RESULTS: Create a php info page

Although LEMP is installed, we can still take a look and see the components online by creating a quick php info page
To set this up, first create a new file:

sudo vi /usr/share/nginx/html/email-bulk-admin/public/info.php

Add in the following line:
<?php
phpinfo();
?>

 

Then Save and Exit.
Restart nginx so that all of the changes take effect:

 

sudo service nginx restart

Finish up by visiting your php info page (make sure you replace the example ip address with your correct one): http://xx.xx.xx.xx/info.php

It should look similar to this.
Step Eight—Set Up Autostart
You are almost done. The last step is to set all of the newly installed programs to automatically begin when the VPS boots.
sudo chkconfig –levels 235 mysqld on
sudo chkconfig –levels 235 nginx on
sudo chkconfig –levels 235 php-fpm on

 

 

We will continue the installation of  Deploy Bulk Email on Linux In next Post.. 

 

 

 

 

 

 

Disable strict mode on MySQL / MariaDB

Disable strict mode on mysql / MariaDB

How do I disable MySQL strict mode on the server?

MySQL strict mode

MySQL strict mode

Error : 

 

“My SQL Error 1048 column description cannot be null”
“mysql error : Incorrect integer value “

These error normally comes when you trying to get some transaction on the database server. This can be fix in multiple ways in some case you will need to have root/admin level of access on database or  phpmyadmin access. Below are more detail steps to fix it in mysql.

Open the “/etc/my.ini” file on database server and look for something like…
# Set the SQL mode to strict
sql-mode=”STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION”

Replace with:

sql-mode=”NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION”

You may able to do it in another method by login into the phpMyAdmin, if you have cpanel you can login into the cpanel > Database section you will find option “phpMyAdmin”. You may be able to run an SQL query within your phpMyAdmin as shown below.

SET @@global.sql_mode= ”;

 

How do I disable Strict mode on MariaDB database server?

 

This example shows how to get a readable list of enabled SQL_MODE flags:

SELECT REPLACE(@@SQL_MODE, ',', '\n');
+-------------------------------------------------------------------------+
| REPLACE(@@SQL_MODE, ',', '\n')                                          |
+-------------------------------------------------------------------------+
| STRICT_TRANS_TABLES
NO_ZERO_IN_DATE
NO_ZERO_DATE
NO_ENGINE_SUBSTITUTION |
+-------------------------------------------------------------------------+

Adding a new flag:

SET @@SQL_MODE = CONCAT(@@SQL_MODE, ',NO_ENGINE_SUBSTITUTION');

If the specified flag is already ON, the above example has no effect but does not produce an error.

How to unset a flag:

SET @@SQL_MODE = REPLACE(@@SQL_MODE, 'NO_ENGINE_SUBSTITUTION', '');

How to check if a flag is set:

SELECT @@SQL_MODE LIKE '%NO_ZERO_DATE%';
+----------------------------------+
| @@SQL_MODE LIKE '%NO_ZERO_DATE%' |
+----------------------------------+
|                                1 |
+----------------------------------+

 

 

Remember one thing this is base on the studies we implement for our customers if this fix does not apply on your issue you can contact us to permanently solve your issue at   http://365hostingSupport.com

 

 

 

 

cPanel Server Management


 

cPanel Server Management

Cpanel Server Management

Cpanel Server Management


 

365HostingSupport Offers the value added extra feature who boost your hosting business with Quality Cpanel Server Management service. With backbone of highly qualified Technical Support team and excellent response time you can find answer to your every query related to your hosting problems.

 

365HostingSupport Provides the outgoing calls to your direct customer on your behalf and make sure that there is no communication gap which generally happens with traditional email communication and avoids the technical misunderstanding between to parties while trying to solve a simple problems.

 
365HostingSupport Provides real 24×7 technical Support with solid base and availability of all level of Admins (Level 1 , Level 2 , Level 3). This make sure that you do not have to wait for the Sr. admin to come in shift and solve your issue.

 

Due to the transparente system you can directly communicate with the technical person over skype / gmail / yahoo / hotmail or any other medium which you would like to. This makes you comfortable and easy to explain your problems.

 

Easy to track down issues, with help of the centralized Ticket board system and billing system you can easily take overview of your current ongoing issues and followup on it.

 

Excellent Cpanel Management service , with Cpanel Certified Team you can always find your self in safe hand and expect quick solution on your issues


Why Sign Up ?

We have highly-trained teams standing by to provide 24×7 support to your clients
Quality Technical Support to Hosting companies and ISPs
Effective low-cost 24/7 support services
7 Days Money Back Guarantee

Experties:


 

Cpanel Experts more than 5 Year of experience.
Cpanel + CloudLinux
Cpanel + AWS
Cpanel + OVH
Cpanel + Cluster
Cpanel + PowerDNS
Thanks,
Server Management Company
http://365hostingsupport.com
Skype: supportteam365


 

Nginx 504 error: Gateway Timeout upstream timed out (110: Connection timed out)

Nginx 504 error: Gateway timeout upstream timed out (110: Connection timed out)

Error :

Nginx 504 Gateway timeout

Nginx 504 Gateway timeout

upstream timed out (110: Connection timed out) while reading response header from upstream
nginx 504 error: Gateway Timeout

 

  • Nginx + plesk
  • Plesk 12.5 for Linux
  • Plesk 12.0 for Linux
  • Plesk 11.0 for Linux
  • Plesk 11.5 for Linux

Plesk Error log path :

“/var/www/vhosts/example.com/logs”

In NGINX plain server it should log to a pre-defined location which is often /var/log or /var/log/nginx

 

2016/03/15 12:32:13 [error] 12499#0: *5045889 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 123.123.123.123, server: my.domain.com, request: “GET /index.php HTTP/1.0”, upstream: “https://123.123.123.123:7081/index.php”, host: “domainname.com”, referrer: “https://domainname.com/client/”

 

This error “nginx 504 error: Gateway Timeout” does often caused due to the issue on the back-end connections which is serving the contents, to fix this we need to figure out what configuration we are using.

 

Fix :

For Nginx as Proxy (php-fpm disabled)

To Fix it for all website hosted on server we will need to change the global settings, check if the file exist on plesk server as “/etc/nginx/conf.d/timeout.conf” if not create it and enter the below values in it.

proxy_connect_timeout       600;
proxy_send_timeout          600;
proxy_read_timeout          600;
send_timeout                600;

If you are not using the Nginx as proxy but Nginx + FastCGI (PHP-FPM enabled) we will need to change the value at “/etc/nginx/nginx.conf” as below

fastcgi_buffers 8 128k;
fastcgi_buffer_size 256k;

Once done Restart ‘php-fpm’, ‘apache’ and ‘nginx’ services.

 

Remember one thing this is base on the studies we implement for our customers if this fix does not apply on your issue you can contact us to permanently solve your issue at   http://365hostingSupport.com

 

PhpMyAdmin authentication failure from cpanel

Error : PhpMyAdmin authentication failure from cpanel

 

phpMyAdmin is not working fine from Cpanel. When visiting Cpanel > MySQL Databases > phpMyAdmin

Entering the logged in user’s username and password, or indeed any valid database username and password combination, fails to get past the login box. Even though tried to change the database users password and also updated the phpmyadmin using below command

 

#/usr/local/cpanel/bin/updatephpmyadmin –force

 

also  tried /scripts/upcp –force but still didnt work,  the same issue occurred for the webmail / horde /RoundCube.

 

Fix :

 

1.    Rename /usr/local/cpanel/base/3rdparty/phpMyAdmin to something else

[~]#mv /usr/local/cpanel/base/3rdparty/phpMyAdmin

/usr/local/cpanel/base/3rdparty/phpMyAdmin_back

 

2.  /usr/local/cpanel/bin/update-roundcube –force 

 

3.   /scripts/upcp –force

 

Remember one thing this is base on the studies we implement for our customers, if this fix does not apply on your issue you can contact us to permanently solve your issue at   http://365hostingSupport.com

 

 

Login not permitted to account with a uid lower than 1000

If you dealing with the disk crash and recovering the accounts from old cpanel disk to new cpanel server you might get this error “Login not permitted to account with a uid lower than xx “  So that does this case and how to solve it.

 

Remember one thing this is base on the studies we implement for our customers if this fix does not apply on your issue you can contact us to permanently solve your issue at   http://365hostingSupport.com

Error :

Login not permitted to account with a uid lower than xx “

dovecot[464249]: auth: Error:
Cpanel::MailAuth: Login not permitted to account with a uid lower than 1000
(883)

Jun 17 08:25:38 servername.com dovecot[464249]: pop3-login:
Disconnected: Inactivity (no auth attempts in 181 secs): user=<>,
rip=119.30.45.117, lip=198.50.154.36, session=<B2rCc3g1cWR3Hi11>
Jun 17 08:25:48 servername.com dovecot[464249]: auth: Debug: client
in: AUTH 1 PLAIN service=imap secured
session=+45jdHg1puUAAAAAAAAAAAAAAAAAAAAB lip=::1 rip=::1
lport=143 rport=58790 resp=<hidden>
Jun 17 08:25:48 servername.com dovecot[464249]: auth: Debug:
checkpassword(test@domainname.com,::1,<+45jdHg1puUAAAAAAAAAAAAAAAAAAAAB>):
execute: /usr/local/cpanel/bin/dovecot-wrap
/usr/libexec/dovecot/checkpassword-reply
Jun 17 08:25:48 servername.com dovecot[464249]: auth: Debug: auth
client connected (pid=490158)
Jun 17 08:25:48 servername.com dovecot[464249]: auth: Error:
Cpanel::MailAuth: Login not permitted to account with a uid lower than 1000
(883)

Reason :

1. Recently copied the Account from old server

2. /etc/passwd and /etc/shadow file touched/tampered

3. The mail server will try to authenticate against system user of the server instead of virtual domains on the server

4. /etc/dovecot/dovecot.conf touched/tampered .

 

Fix :

Check the cpanel user uid and gid by id command

[root@7578445 ]#id cpanelusername

make sure its not below the one which is mentioned in the error log

If yes you can backup and restore the same account which will asign the latest new uid and gid to cpanel user

Also make sure that there is entry of the domain in both /etc/localdomains and /etc/userdomains.

[root@7578445 /etc/dovecot] #egrep valid_uid\|valid_gid dovecot.conf
# be done even if first_valid_uid is set to 0.
first_valid_uid = 201
#last_valid_uid = 0
#first_valid_gid = 1
#last_valid_gid = 0

Change the hostname of the server to something else other than domain name.

For example if your domain is domain.com then you can set the hostname as host.domain.com

 

 

How to enable IPv6 on OVH with SolusVM

How to enable IPv6 on OVH with SolusVM > Though it’s been simple to install IP6 on any Server but when its comes to the Server from OVH standard steps to install and configure IP6 gets failed and ip does not response to ping6.

Sometimes Admins get confused with the custom rather complex structure and rules sets which must be followed by the admin for getting the IP6 online with SolusVM or other Virtual technologies. Know you must be thinking what are they and how to get ride of it.

IPv6 + OVH + SolusVM

IPv6 + OVH + SolusVM

Few simple things you need to keep in mind from start of the installation of Master server to end of configuring the networking on it. If you have missed single settings you going to get headetch for you.

1st You need to get some information on ip6

http://en.wikipedia.org/wiki/IPv6

http://www.olympus-zone.net/page_1033_en_Blue.html

Now lets get prepaid for Getting IPv6 online, make sure the server must be running with a IPv6 kernel. This kernel is available by netboot Netboot.

Find your own IPv6 address in manager v3 Manager.

IP Manager OVH

IP Manager OVH

An IPv6 example

An IPv4:

213.186.35.9/24

IPv6 will be the following:

2001:41d0:1:209::/64

Here are examples from which you can configure IPv6 on your dedicated server:

2001:41d0:1:209::1/64

2001:41d0:1:209:FF:FF:FF:FF/64

2001:41d0:1:209:A::1:1/64

2001:41d0:1:209::1:B:F/64

2001:41d0:1:209:1:1:1:1/64

The following notations are the same:

2001:41d0:1:209::1:B:F/64

2001:41d0:1:209:0:1:B:F/64

2001:41D0:0001:0209:0000:0001:000B:0000F/64

But you can :: place only once.

An example ifconfig

Once you’ve switched the server to IPv6 kernel, after the reboot ifconfig already has IPv6 info:

adr inet6: fe80::2e0:4cff:fe99:88d0/64 Scope:Lien
This shows that IPv6 works on the network.

Now go to your network settings and make below changes (ip6 and other network settings will be according to your own)

[root@cadvz2 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0

ONBOOT=yes

IPV6INIT=yes

IPV6_AUTOCONF=no

BRIDGE=xenbr0

[root@cadvz2 ~]#

 

 

[root@cadvz2 ~]# cat /etc/sysconfig/network-scripts/ifcfg-xenbr0

DEVICE=xenbr0

TYPE=Bridge

BOOTPROTO=static

BROADCAST=xx.xx.xx.255

IPADDR=xx.xx.xx.153

NETMASK=255.255.255.0

NETWORK=xx.xx.xx.0

ONBOOT=yes

IPV6INIT=yes

IPV6ADDR=”2607:5300:60:6E99::/64″

ARPCHECK=”no”

IPV6_AUTOCONF=”no”

[root@cadvz2 ~]#

 

[root@cadvz2 ~]#echo 1 > /proc/sys/net/ipv6/conf/all/forwarding

 

[root@cadvz2 ~]#cat /etc/sysctl.conf

Check below content should be on it

net.ipv6.conf.all.autoconf = 1

net.ipv6.conf.default.autoconf = 1

net.ipv6.conf.eth0.autoconf = 1

net.ipv6.conf.all.accept_ra = 1

net.ipv6.conf.default.accept_ra = 1

net.ipv6.conf.eth0.accept_ra = 1

[root@cadvz2 ~]# route -A inet6

above command should show you the routing available under inet6 routing table.

[root@cadvz2 ~]#/etc/init.d/network restart

Restart the services if everything goes well it should come up fine

Now you have to deal in the SolusVM Panel to make sure you add them correctly.

 SolusVM Panel IPv6

SolusVM Panel IPv6

Route: IPv6 Gateway

The router (default gateway) for each IPv6 is always on IP: v:6:FF:FF:FF:FF:FF

For example:

The IPv6 server: 2001:41D0:1:46e::/64 to 2001:41D0:1:4 + 5x FF.
IPv6 Gateway: 2001:41D0:1:4FF:FF:FF:FF:FF

The IPv6 server: 2001:41d0:1:209::/64 to 2001:41d0:1:2 + 5x FF.
IPv6 Gateway: 2001:41d0:1:2FF:FF:FF:FF:FF

 

And that’s all you can now assign the IP6 from your SolusVM