In spite of the DNS and Zone records have been filled in correctly, website is still showing the cPanel Default Page. This is usually caused by IP has been wrongly assigned on WHM during setup of the account.
- If you 2 or more IP address on your VPS, check the domain name has been assigned to the correct one that has been used in your DNS Zone records.
- If you have only been assigned with only 1 IP address, verify the IP address beside your domain name in WHM under List Accounts from the side menu. If the IP address is different with your assigned IP, this is likely you have a mis-configured cPanel or the shared IP has not been configured correctly. To correct this, find Basic WHM/ cPanel setup, scroll down to shared IP section [* The IP address (only one address) that will be used for setting up shared IP virtual hosts.], update the IP with the correctly assigned one and save changes. Next, select Change Site’s IP address from side menu and update the IP for the domain accordingly.
Since PLESK 10, I’ve observed that one of the most common mistake made on Plesk is the subscription expiration. This is usually neglected when PLESK is created under service provider view. Any subscription created with default settings has a 12 month validity period and will be automatically suspended by PLESK when it is expired. If you are seeing website returns a 503 page or service unavailable and this is likely the cause.
To verify your settings, sign in as admin, root or administrator to your Plesk Panel. From the menu on left hand side, select Subscription. Now, select the subscription highlighted in “RED” with an exclamation mark and choose “Customize”.
Scroll all the way down, you will find the expiration date section. To rectify, check on unlimited or select a later date and “Update”.
Remember to hit on the “Activate button” if your subscription has been suspended.
At Vastspace, we insist on only SAS Hard Drives or Enterprise SSDs for our servers. It’s because SAS Hard Drives are the most reliable, maintain their performance under more difficult conditions, and perform much better than compares to either Near Line SAS or SATA disks.
In reliability, SAS hard drives are an order of magnitude safer than either Near Line SAS or SATA disks. The metric is measured in bit error rate (BER), or how often bit errors may occur on the media. With SAS hard drives, the BER is generally 1 in 10^16 bits. Read differently, that means you may see one bit error out of every 10,000,000,000,000,000 (known as 10 quadrillion) bits. By comparison, SATA drives have a BER of 1 in 10^15 (1,000,000,000,000,000 or 1 quadrillion). Although this does make it seem that SATA disks are pretty reliable, when it comes to absolute data protection, that factor of 10 can be major.
SAS hard drives are also built to more exacting standards than other kind of hard drives. SAS hard drives have a mean time between failure (MTBF) of 1.4 million hours or higher compared to 1 million hours or lower for most SATA hard drives.
Here’s a good article on Choosing Between SAS vs. SATA Hard Disk for Your Server RAID System from Intel: http://download.intel.com/support/motherboards/server/sb/enterprise_class_versus_desktop_class_hard_drives_.pdf
cPanel & WHM software version 11.42 has now reached End of Life.
In accordance with cPanel EOL policy [http://go.cpanel.net/longtermsupport], 11.42 will continue functioning on servers. The last release of cPanel & WHM 11.42, 184.108.40.206, will remain on cPanel mirrors indefinitely. However, no further updates, such as security fixes and installations, will be provided for 11.42. Older releases of cPanel & WHM 11.42 will be removed from their mirrors.
If your server setup complicates the process of migrating to a newer version of cPanel & WHM (an upgrade blocker list is available at http://go.cpanel.net/blockers), then cPanel is here to help. Simply open a support ticket at https://tickets.cpanel.net/submit so that cPanel knowledgeable support team can provide recommendations, migration assistance, and more.
I prefer to update, install and reinstall patches of PLESK from command line.
to update and install patches
to reinstall patches
1. SSH to your Linux Cloud Server or SSD Cloud Server
yum -y install squid
chkconfig squid on
2. mv /etc/squid/squid.conf /etc/squid/squid.conf.original
3. vi /etc/squid/squid.conf
4. add this into the configuration file
acl manager proto cache_object
acl localhost src 127.0.0.1/32 ::1
acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1
acl localnet src 10.0.0.0/8 # RFC1918 possible internal network
acl localnet src 172.16.0.0/12 # RFC1918 possible internal network
acl localnet src 192.168.0.0/16 # RFC1918 possible internal network
acl localnet src fc00::/7 # RFC 4193 local private network range
acl localnet src fe80::/10 # RFC 4291 link-local (directly plugged) machines
acl SSL_ports port 443
acl Safe_ports port 80 # http
acl Safe_ports port 21 # ftp
acl Safe_ports port 443 # https
acl Safe_ports port 70 # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535 # unregistered ports
acl Safe_ports port 280 # http-mgmt
acl Safe_ports port 488 # gss-http
acl Safe_ports port 591 # filemaker
acl Safe_ports port 777 # multiling http
acl CONNECT method CONNECT
http_access allow manager localhost
http_access deny manager
http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports
http_access allow localnet
http_access allow localhost
hierarchy_stoplist cgi-bin ?
refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern -i (/cgi-bin/|?) 0 0% 0
refresh_pattern . 0 20% 4320
auth_param basic program /usr/lib/squid/ncsa_auth /etc/squid/squid_access # change to lib64 for 64bit Centos
auth_param basic childred 5
auth_param basic realm Squid proxy-caching web server
auth_param basic credentialsttl 2 hours
acl ncsaauth proxy_auth REQUIRED
http_access allow ncsaauth
acl ip1 myip 192.168.0.1
tcp_outgoing_address 192.168.0.1 ip1
acl ip2 myip 192.168.0.2
tcp_outgoing_address 192.168.0.2 ip2
acl ip3 myip 192.168.0.3
tcp_outgoing_address 192.168.0.3 ip3
acl ip4 myip 192.168.0.4
tcp_outgoing_address 192.168.0.4 ip4
acl ip5 myip 192.168.0.5
tcp_outgoing_address 192.168.0.5 ip5
request_header_access Allow allow all
request_header_access Authorization allow all
request_header_access WWW-Authenticate allow all
request_header_access Proxy-Authorization allow all
request_header_access Proxy-Authenticate allow all
request_header_access Cache-Control allow all
request_header_access Content-Encoding allow all
request_header_access Content-Length allow all
request_header_access Content-Type allow all
request_header_access Date allow all
request_header_access Expires allow all
request_header_access Host allow all
request_header_access If-Modified-Since allow all
request_header_access Last-Modified allow all
request_header_access Location allow all
request_header_access Pragma allow all
request_header_access Accept allow all
request_header_access Accept-Charset allow all
request_header_access Accept-Encoding allow all
request_header_access Accept-Language allow all
request_header_access Content-Language allow all
request_header_access Mime-Version allow all
request_header_access Retry-After allow all
request_header_access Title allow all
request_header_access Connection allow all
request_header_access Proxy-Connection allow all
request_header_access User-Agent allow all
request_header_access Cookie allow all
request_header_access All deny all
5. Save squid.conf
6. chkconfig squid on
7. Restart Squid with “service squid restart”
Server Health monitoring is important and effectively provides useful additional perspective when combined with Up-time monitoring; it assists Vastspace in preventing downtime with informative capacity planning, rather than merely able to react to predictive failure or failure events. Common scenarios resulting in a server failure include excessive CPU usage, insufficient RAM and excessive Disk IO operations.
Our Server monitoring team is a dedicated team solely focused on providing service reliability and react to incident in proactive manner. The team utilizes an industry proven set of system level health and service monitoring tools to ensure our servers’ are optimal performance through early detection of problems. In the event that an issue is identified, our Team will respond timely, reducing downtime and fix any issues proactively, before the client is even aware of the problem at most time.
I get phone calls often asking about CloudFlare. What is CloudFlare? The biggest part of CloudFlare, apart from the cool features to protect your website from a range of online threats from spammers to SQL injection to DDOS, it is about getting closer to your clients in global perspective, maybe in terms of online business connectivity.
Not too much of words to describe how your site can get closer to your clients, here’s a comparison on how vastspace.net with and without CloudFlare enabled.
With CloudFlare enabled, your website content are distributed to 28 data centers around the world. CloudFlare CDN automatically caches your static files using their edge nodes so these files are stored closer to your visitors while delivering your dynamic content directly from your web server. CloudFlare then uses a technology called Anycast to route your visitors to the nearest data center. The result is that your website, on average, loads twice as fast for your visitors regardless of where they are located.
You’ll be able to see the exact speed benefits and savings with your personalized CloudFlare analytics report at CloudFlare portal if you are a subscriber. On average, a website on CloudFlare loads twice as fast for its visitors, sees 65% fewer requests and saves 60% of bandwidth.
Most importantly, it costs as little as $15 /month for a site on CloudFlare Pro subscription at Vastspace. In business perspective, it’s bang for the buck.
Not all Cloud SSD VPS are the same, Vastspace SSD VPS server nodes are custom built and optimized RAID for redundancy and high performance. Vastspace SSD VPS server nodes use only Enterprise SSD Drives ensuring fast and consistent command response times as well as protect data loss and corruption.
We have done the read & write tests for our Cloud SSD VPS against a popular SSD VPS,
Our Cloud SSD VPS starts with 2 CPU core, 1Gb memory and 30Gb of disk space. For the tests, we have ordered the closer specification we can get from this provider, 2 CPU core, 2Gb memory and 40Gb of disk space.
Both candidates are based on CentOS 6.5 x64 and hosted in Singapore Data Centers
Here are the results;