#namecheap.com

Namecheap is a domain registrar.

I recently started moving my domains into this registrar.

The best I like here, is their 24/7 live chat support.  No need to make phone calls, open tickets, and wait 24 - 48 hours for issues to be resolved.

Plus, they’re really cheaper in most cases compaired to my current registrars!

Cara Beli dan registrasi domain murah di namecheap

Kalau anda terbiasa membeli domain sekaligus di tempat yang sama dengan penyedia hosting. sekali- sekali coba membeli melalui namecheap. buka link namecheap di link ini.

ada beberapa perbedaan, salah satunya dalam pengelolaan dan verifikasi whois. tapi kali ini saya coba berbagi info untuk anda yang belum tahu, gunakan discount coupon untuk pembelian di namecheapcoupons.com

setelah anda memesan

I followed this tutorial to set up my SSL certificate on verysuchmuch.com.

The formatting made it a little difficult to read so I decided to repost and explain the steps myself. In the following comands, replace "example.com" with your domain name.

Generate SSL Key

sudo su

openssl genrsa -des3 -out example.com.key 2048

openssl rsa -in example.com.key -out example.com.key.nopass

openssl req -new -key example.com.key.nopass -out example.com.csr

Here you'll be prompted to enter some information about your site. All questions marked with '[]' are optional, however, 'Common Name' must be the same as your domain name. Also, don't enter a Challenge Password.

cat example.com.csr

Namecheap Steps

Now, navigate to the Your SSL Certificates page of your Namecheap account. Select 'Activate Now' on your certificate.

Select server type: Apache/OpenSSL*

Copy the entire contents of example.com.csr into the text area, this includes the -----BEGIN---- and ----END--- tags.

Enter the additional information Namecheap asks for and submit the form. 

After 30 minutes to a few hours, You'll receive an email with a zip file containing 3 files. Unzip the file, and then open a terminal in the directory where you placed them. 

cat example_com.crt PositiveSSLCA2.crt AddTrustExternalCARoot.crt > example.com.crt

Copy example.com.crt and example.com.key.nopass to a place on your server where nginx can access them. For me, I chose: /usr/local/etc/nginx/ssl/

Nginx Configuration

In your nginx configuration for example.com place:

ssl on; ssl_certificate /usr/local/etc/nginx/ssl/example.com.crt; ssl_certificate_key /usr/local/etc/nginx/ssl/example.com.key.nopass;

in the server {} block.

You should be set to restart nginx and be certified! (sudo service nginx restart)

Further consideration: 

I didn't have https set up prior to purchasing a certificate, so I needed a new server {} block in my configuration listening on port 443 instead of 80. 

server { listen 0.0.0.0:443;

ssl on; ssl_certificate /usr/local/etc/nginx/ssl/example.com.crt; ssl_certificate_key /usr/local/etc/nginx/ssl/example.com.key.nopass;

server_name example.com; access_log /var/log/nginx/example.access.log; location / {  # redacted  }

}

To force people that hit example.com on regular http over port 80:

server { listen 0.0.0.0:80; server_name example.com; access_log /var/log/nginx/example.access.log; return 301 https://example.com;

}

More poor twitter ads.

This isn't ONLY about their previous support of SOPA, a bill that is widely renowned for being a completely dumb idea, a bill that gives corporations and the government way too much power to take down a site. Due to "a spike in domain name transfers"(quote from a GoDaddy email to the press), they finally oppose the bill. The boycott's goal was achieved. Although, the wording of their statements does indicate that the only thing they don't like about the bill is the lack of support from their customers. After all, they helped write the thing.

Now, while it's possible that they're just victims of bad wording(maybe they MEANT "oppose" when they said "no longer support"), and maybe they were just one of many cooks in the kitchen(they were) & the final bill was spoiled by other contributors(they shouldn't continue to support it if that was the case, though), and maybe their arms were twisted by politicians(hey, it's politics, after all)........ they still suck. Their website is cluttered, it feels like I'm managing my website in a store instead of a control panel, and their ads are trashy. No amount of SOPA retribution will be enough to bring me back to their up-sell marathon. Thanks to all the outcry about their support of SOPA, I've found a number of great recommendations for alternatives for both the hosting and domain management! I always thought their domain privacy was overpriced, now I KNOW it is! Namecheap.com (hides your contact info for $2.88(free for first year, 5 domains protected for $7.88/yr) as opposed to GoDaddy's $9.99/yr for a single domain. Looks like I'll finally be making my contact info private!

What I was really happy with, however, was Host Gator's services. Namely: THEY TRANSFERRED MY SITE AUTOMATICALLY! Every other host I looked at would have required me to download all 10 GB of data I have hosted(multiple sites), then re-upload it all to the new server. Host Gator did that for me, including the databases. That's right, they actually HELP their new customers switch to them. What a concept! That 10 GB was what kept me from moving my hosting to somebody else. Another benefit is the SSL certificate pricing. GoDaddy charges $69.99/yr. Host Gator has them ranging from free(uses a different domain) to $50/yr(normal-type) and Namecheap has them ranging from $8.95/yr all the way to... well, there are some rather deluxe options.

Another benefit of Host Gator is their environmental focus. Their servers are 130% wind powered thanks to renewable energy credits(it's complicated to explain). That's just cool.

In full disclosure, yes, I used an affiliate link for Host Gator, but let me tell you something: while I was always able to use Godaddy affiliate codes on my site, I never felt comfortable recommending them for the pre-SOPA reasons I listed. Host Gator actually rocks, judging from my first impression of them and other people's recommendations.

Get excited because I'm about to walk you through the less than intuitive process of giving your blog a custom domain name. I know what you're thinking, and the answer is 'yes', your friends will think you're a hacker from the freaking future.

First, log into the account you purchased your domain from. Your domain provider will be something like, GoDaddy.com or Namecheap.com. We purchased our domain from Namecheap.com and we are using tumblr.com to host our blog. If you've purchased your domain from Namecheap, and you're using tumblr.com this tutorial will be an exact walkthrough. Otherwise, these instructions may not be an exact step-by-step guide, but it should be close.

After you've logged into your account, go to  [MY Account] and click on [Manage Domains]. Select the domain you wish to edit by clicking the checkbox, and then click [Edit Selected].

On the left hand column, click on [All Host Records]. Next, click on the drop down menu for your IP addresses and select [A Record], which stands for address record. There should be two available fields to edit. One for "@" and the second for "www." Copy and paste the IP address: 72.32.231.8 and click on [Save Changes]. This will point your domain to the tumblr site. To ensure that you've done this correctly, use the Custom Domain Test Tool provided by tumblr.

Don't change your facebook status bragging about your latest technological accomplishment just yet. You have one last thing to do.

Log into your tumblr account and click on the blog you wish to edit. Click on the [Settings] button located on the right hand side. Just under your Portrait Photo menu, you'll notice there's a URL menu. Click on the checkbox for [Use a custom domain name]. Now, with a triumphant swagger type in your custom domain name. In our case it's theprojectfilms.com. Scroll to the bottom of the screen and click [Save preferences].

And that's it. You're done! Tumblr will tell you that it may take up to 72 hours to see the changes. This might be true in some cases, but in my experience I've seen the changes take place in less than an hour.

If you've made it this far, thanks for reading and congratulations on giving your blog a custom domain name!

Don't text and drive,