Namsahaz now accepts Credit Card payment through 2Checkout.com!
- Posted by Namsahaz Team on July 13th, 2008 filed in Updates
- Comment now »
Namsahaz have always accepted credit card payment through PayPal before. However, there are a few limitations of using PayPal as our credit card payment gateway. The first problem is that PayPal requires the buyer to register with PayPal in order to make the payment. This is usually frowned upon those who just want to make quick payments using their credit card numbers. The second problem is that PayPal only support few countries. Therefore, customers from Egypt, for instance, is not able to transfer funds by using credit card through PayPal, as they are not able to register themselves for PayPal because PayPal doesn’t support Egypt. There are also some other countries where PayPal could not be used.
In order to overcome this problem, we are now introducing another alternative payment options for those wanting to make payment through credit card –> 2CheckOut.com. We now accept most major credit card transfers in a hassle-free environment.
Why 2CheckOut.com?
1) Users can make credit card payment without needing to do any registration! Simply fill in your personal particulars and credit card information in the payment page, and payment will be sent directly to us!
2) 2CheckOut is not limited to certain countries only. Anyone from all over the world can purchase services from us!
Hopefully the introduction of this new alternative payment method is going to smoothen up transactions for those who wants to purchase our services by using credit card transfers 
Disallow hotlinking by using .htaccess
- Posted by Namsahaz Team on July 12th, 2008 filed in Tutorial, DIY
- Comment now »
The .htaccess file located in your /public_html/ directory is a very useful file to configure how your website behave. A lot of people use the .htaccess file to do URL redirection. For example, they want users to access their site without ‘www’, so they will insert the redirection codes inside the .htaccess file so that any users who access their site with ‘www’ will be redirected to their domain without ‘www’.
By taking advantage of the URL redirection with .htaccess, you can actually do more useful stuffs, such as disallowing external users to hotlink your images from their site.
What is image hotlinking?
Hotlinking is a method of linking images directly from your website into their own website. This method is usually referred to as ’stealing’, because doing hotlinking will take up your website’s bandwidth instead of theirs.
Let’s say your domain is yourdomain.com. Another user found an interesting image that you posted in your website, so he/she decided to ’steal’that image by doing hotlinking in their own website’s HTML, such as below:
<img src=”http://www.yourdomain.com/images/myimage.gif” />
By inserting the code above into their own website, the image “myimage.gif” from your website will be displayed in their own website. Because of this, everytime that person’s website is visited, the image will load in their website but it is your bandwidth which is actually being used - therefore, the term “bandwidth stealing” was invented 
How to avoid hotlinking?
All you need to do is edit your .htaccess file and add the following codes:
====
RewriteEngine on
RewriteCond %{HTTP_REFERER} !^$
RewriteRule .(jpg|jpeg|png|gif)$ http://img371.imageshack.us/img371/6905/bandwidthzn9.jpg [NC,R,L]
====
Now when people hotlink your image into their website, the image will not show up. Instead, it will be replaced with the “Stop Stealing Bandwidth” image, or any other image you specify in your .htaccess configuration.
You may change the imageshack URL to display any other image you want when external people hotlink to your image. It is best that you host that image on some other external image hosting service, such as ImageShack, or else it beats the whole idea of disallowing hotlinking.
That’s basically it! 
Bypass firewall filters to access your cPanel!
- Posted by Namsahaz Team on July 1st, 2008 filed in DIY
- Comment now »
In many corporate networks (such as in your office), the system admin uses firewall to secure the network by allowing access to the Internet only through common ports such as TCP port 80 for the web access (HTTP), TCP port 25 for email (SMTP) and so on. cPanel, the award-winning webhosting manager that we use for all Namsahaz users actually use TCP port 2083 by default. Due to the reason that port 2083 is not a common port, it is usually blocked by firewalls that’s being setup in your office. Therefore, many users will experience “Page not found” or “Proxy error” when trying to access to their cPanel interface from their office because the firewall is denying access to it ; either through http://yourdomain.com/cpanel OR https://yourdomain.com:2083.
In order to solve this issue, we install cPanel proxy in every accounts that we create in our server. The cPanel proxy files are placed inside your /public_html/cpanel/ directory (please refrain from deleting these files). In other words, all accounts in our webhosting package have this cPanel proxy so that you can bypass firewall filters to access the cPanel. However, it is not enabled by default.
How to enable Cpanel Proxy in your account?
If you want to enable the cPanel proxy, you need to create a subdomain by the name “cpanel” as the prefix, such as “cpanel.yourdomain.com”. Once you have created this subdomain, you can access to your cPanel even though you are behind a corporate firewall by pointing your browser to the subdomain’s URL –> http://cpanel.yourdomain.com.
Easy, right? But then again be reminded that you need to be able to access your cPanel in the first place before you can create the subdomain. So we recommend that you create the subdomain when you’re at a place where the firewall is not blocking access to your cPanel, such as at your home. If you are at your office and urgently need access to your cPanel, you can send us an e-mail at support [at] namsahaz [dot] com and we will quickly help you to create the subdomain for you, thus enabling access to your cPanel through the cPanel proxy.
Similar to the cPanel, you can also access to your Webmail’s interface behind firewall by creating a subdomain like “webmail.yourdomain.com”.
The only drawback to using this feature is that you will not be accessing your cPanel through a secure channel. You will be accessing it through HTTP instead of the usual HTTPS connection. Because of this, please be extra careful when logging into your cPanel as the connection is not encrypted, giving more exposure of your login credentials to proxies or any other man-in-the-middle attacks.
For users who doesn’t have cPanel proxy installed and would like to install themselves, feel free to download the script at the following URL: http://cpanelproxy.net
Cheers ~ 
Regarding server downtime yesterday
- Posted by Namsahaz Team on June 18th, 2008 filed in Updates
- 8 Comments »
At about 4PM yesterday, 18th June 2008, one of our most populated server has gone down for the longest period we have ever experienced. The server went down from 4PM until 11PM. It was brought back online 7 hours later since it first lost access to the Internet. We are very sorry for the trouble that has been brought during this long downtime but the problem yesterday was unavoidable and took much of our time to be restored.
What happened was there was initially a slight problem in the datacenter networks which required the datacenter team to temporarily unplug the servers in one of their section. And unfortunately, our server is affected and our cable plug was being disconnected. The real problem happened when they plugged back our server few minutes later and rebooted our server, by which the server returned the following error during the restart:
——————————
Cheking root filesystem
/dev/md1 contains a file system with errors, check forced
/dev/md1 : ===
——————————
The server was rebooted/restarted many times to no avail, the same error message keep on showing and the reboot keeps on failing. Apparently, the filesystem was corrupted, possibly due to the sudden reboot. Therefore, we decided to travel to the datacenter at 6 o’clock which is located in Cyberjaya and spent the next several exhausting hours trying to fix and restore the filesystem.
At 11PM, we managed to bring back the server online.
For those who are deeply affected by yesterday’s downtime, we would like to extend our sincere apology for the unexpected downtime which has also affected us ourselves. We have did our best to bring back the server online even though it took us a few hours to fully restore the server.
Affiliates will get recurring commissions
- Posted by Namsahaz Team on June 7th, 2008 filed in Affiliates
- 5 Comments »
We’ve been asked this question a lot of times by our affiliates - “Will affiliates get recurring commissions whenever those accounts they referred to has made renewal payment for the next year cycle?”.
The answer is YES, affiliates WILL get recurring payments in that situation.
Consider the following scenario: Say, an affiliate has referred someone to Namsahaz.com and that person bought a webhosting account with us, the affiliate will then get the appropriate commission for that purchase. But it doesn’t just stop there… the affiliate ID will also stick to that account for as long as the person renews their web account in the following years. This means that everytime the webhsoting account is being renewed, the affiliate will keep on receiving commissions on the renewal fees too. So be rest assured that if you as an affiliate has made a lot of sales this year, there’s a high chance that you will still get good recurring payments on the next following years without needing to do anything!
So we hoped that this post will clear off the question of whether or not any affiliate sales will recur on the next payment cycles. They will. So keep up the good work fellow affiliates!
Not yet an affiliate? Register now or simply purchase a new webhosting account with us to be entitled with a higher percentage of affiliate commission.
