• CentOS
• Debian
• Elastix
• Fedora
• FreeBSD
• Gentoo
• OpenSuSe
• Redhat
• Ubuntu
• XenServer / vSphere / KVM

You must specify if the system is 64-Bit or not during checkout

• cPanel
• Plesk

• Windows Server 2008 R2 Datacenter: 2 TB
• Windows Server 2008 R2 Enterprise: 2 TB
• Windows Server 2008 R2 for IA64: 2 TB
• Windows Server 2008 R2 Foundation: 8 GB
• Windows Server 2008 R2 Standard: 32 GB
• Windows HPC Server 2008 R2: 128 GB
• Windows Web Server 2008 R2: 32 GB

More on: Microsoft Official Page

• Windows Server 2008 All
• Windows Server 2012 All
• Windows Server 2016 All
• MS SQL All versions
• Plesk Control Panel
• cPanel

Install [package name]
> yum install [package name]
> rpm -ivh [software name]
eg:
> yum install mysql 
> rpm -ivh MySQL-client-3.23.57-1.i386.rpm


Remove [package name]
> yum remove [package name]
> rpm -e [software name] 
eg:
> yum remove httpd
> rpm -e httpd
 
Search [package name]
> yum search [package name]
eg:
> yum search httpd

Update [package name]
> yum update [package name] OR yum list updates
 
List installed
> yum list installed
> yum list installed | grep “packagename”
> rpm –ql [packagename]
eg:
> yum list installed | grep “ httpd”
> rpm –ql httpd
 
 
*yum -y install [package name] = install something without asking question/ using default setting
*yum install httpd = install apache
*yum install mysql = install mysql client
*yum install mysql-server 
 
Install pico
> yum -y install nano
> cd /bin/ && ln -s nano pico
 
Use pico instead of vi
> pico /etc/resolv.conf
    

rsync -avurtopg -P 32168 ./abc/ 123.123.123.123:/abc/

Option:

on Source Server:
cd && ssh-keygen -t dsa

on Target Server:
cat source-server:/root/.ssh/id_dsa.pub >> /root/.ssh/authorized_keys
    

crontab -e 
1 1 * * * /home/ispc/cron/kill_httpd.sh

vi /home/ispc/cron/kill_httpd.sh
>> ps aux | grep -ie http | awk '{print $2}' | xargs kill -9


For cron job assignment: reference to : http://en.wikipedia.org/wiki/Cron
    

There are several connection problem types:

1. Local Network Related
2. Server Network Related
3. Power Related
4. Hardware Related

Local Network Related

You are suggested to check if you could visit other websites, such as www.google.com or www.baidu.com to see if you are facing a general network problem occured to your computer, if you can visit the website, you are online, but you still cannot connect to the server, then you are facing a server connection problem. You could use KVM to check if your password or firewall settings to be correct. If you connect to the network, please resolve it before contacting us.

Powered Related

For some/most of our clients, we provide remote control panel for their servers (KVM or iDRAC), before you contacting us, you are suggested to login to your KVM/iDRAC to check if the server power is ON.

Hardware Related

If you find that your server is ON, but still cannot be connected, then you might face hardware problem, such as PDU or harddisk problem.

In some circumstances, you might not be able to connect to your server, please run the following command and print the result to us, by email or via support platform, or by chatting with your account manager:

• Windows: ping -t 123.123.123.123
• Windows: tracert 123.123.123.123
• Linux: ping 123.123.123.123
• Linux: traceroute 123.123.123.123

Change the above IP address to your server IP, get the result, caputre the screen, and send to us (e.g. cs@hkti.net).

Most people or companies face serious threats from attacks from almost everywhere, howerver, knowing the following and do related enhancements, you got much more secure server enviroments:

• Do not use common or default login names
• Stronger passwords, combining Alphabetics, numbers and special characters
• Better user management
• Server Firewall
• Frequeny Server Update & Patching
• Do frequent backups

For more details, please check here: Server Security.