Get your domain name and setup SSL with CloudFlare

Get your domain name and setup SSL with Cloudflare

Few weeks ago I explained how to setup a static page and host it on Github for free using github pages. Have a look at it if you missed it https://kimsereyblog.blogspot.co.uk/2016/07/from-idea-to-product-with-websharper-in.html.

I also explain how we could get a custom domain name for people to access our website easily. For example I’ve setup a github page with my own name domain https://kimsereylam.com and got it served via HTTP.

The problem with setting your own domain name is that your page will not be served with HTTPS. Now for the example website, it is hosted on GitHub and it’s just static data therefore communication encryption isn’t really important. But the issue is that if you share this website to others without specifying the protocol, Chrome will try to open it with HTTPS. And when it does, if you do not serve HTTPS, an ugly error page will show on the browser. This will definitely look bad and more importantly, it makes it look like your site is down. It’s pretty bad.

So today I will share with you how you can serve your website hosted on GitHub via HTTPS for free using CloudFlare. We will see how we can purchase a domain and then setup CloudFlare to protect and accelerate your website. All this steps are important as well if you wish to build a website accessible for everyone on the internet.

This post will be composed by five steps:

  1. What is CloudFlare
  2. Get a domain name
  3. Create a CloudFlare account
  4. Configure the DNS
  5. Setup the SSL

1. What is CloudFlare

Official ClouFlare site: https://www.cloudflare.com/

CloudFlare is a service which can be used to proxy all connection to your website. It provides a DNS service to re-route your calls, a CDN service to deliver your resources faster, a free SSL support and many other options.

Let’s assume that you have a GitHub page or another website already hosted somewhere. To make it more accessible, the first thing we would need to do is purchase a domain name.

So let’s start by getting a domain name.

2. Get a domain name

A domain name is the website name, for example kimsereylam.com is a domain name. A domain name is given by registrars. Different registrar propose domain names at different price so it is worth it to compare between registrars.

I usually get mine from Namecheap https://www.namecheap.com/ as so far I’ve got the best price from there. There’s also GoDaddy https://uk.godaddy.com/ even Google is now starting on the registrar business https://domains.google.com.

domains

Anyway choose the cheapest, they mostly differs in the services provided like hosting or guaranty… But I never used one of their services so I won’t be able to give opinions on that I just go where it is the cheapest.

domain

Now once you see your domain under the dashboard, head over to CloudFlare and create an account.

3. CloudFlare account

https://www.cloudflare.com/

When you first create your account with CloudFlare, the service scans your DNS records for the first time to detect what settings you already have. You just click next until you reach the main page.

The DNS - Domain name system - links request and resources. When someone try to access kimsereylam.com, I actually want to direct them to my GitHub page kimserey.github.io. That’s what a DNS is for. A DNS record is used to configure the DNS and indicate what maps to what. We will see later how to configure the DNS.

Now once you created your account and scan your DNS records for your domain name, the overview page will show a Pending status. This is because you need to use CloudFlare DNS servers for your domain. Go to the DNS configuration page by clicking on the icon.

icon

And find the server names:

server_name

rihana.ns.cloudflare.com
todd.ns.cloudflare.com

Those were attributed by CloudFlare. If not I would have written rihanna with 2 ‘n’. Ha just kidding.

Ok once you got the name go back to your domain registrar and find the DNS page. For me with Namecheap it is directly in Domain List.

servername registrar

Once you’ve done this modification just wait for a while and go back to CloudFlare, your status should be changed to Active!

active

4. Configure the DNS and setup the SSL

Now that registrar is configured to use CloudFlare DNS, we can setup the records for the DNS.

There are multiple type of records, for us what we need is to setup a A record and a CNAME record. A A record is a record which matches the address with an IPv4. An AAAA record matches with an IPv6. To get the IP of your domain, you can ping [your-domain] and you should get the IP.

PING kimsereylam.com (104.28.26.6): 56 data bytes
64 bytes from 104.28.26.6: icmp_seq=0 ttl=58 time=9.880 ms
64 bytes from 104.28.26.6: icmp_seq=1 ttl=58 time=37.381 ms
64 bytes from 104.28.26.6: icmp_seq=2 ttl=58 time=21.492 ms

You can then setup your A record to direct the root (you can use @ as the name to specify that you want to map the root - naked domain) to the IP. For example for me it would be:

a_record

This will mean that when someone navigates to kimsereylam.com, they will be visiting 104.28.26.6 which is what I want. Now sometime people navigate to www.kimsereylam.com. In order to handle that we need to configure a CNAME. A CNAME is an alias, in this case www will be the alias of kimsereylam.com the root. It can be configured this way:

cname

Great that’s it, once you are done with that, just wait a while. The process can take up to 24 hours to take effect. For me it took an hour.

Make sure all the status are orange and not grey - grey means inactive.

active

After an hour you should be able to navigate to kimsereylam.com and www.kimsereylam.com.

5. Setup the SSL

Reminder on SSL

SSL is protocol which provides privacy and data integrity between client and server. It also provides a way to verify that the server is genuine. The privary and data integrity is achieve via encryption. There are two encryption keys involved in the process, a symmetric key and a asymmetric key (private held by the server and public key distributated in SSL). The client uses the public key (the one in the SSL cert) to encrypt a symmetric key which is then decrypted by the server (using its private key) and from then on, client and server uses the symmetric key to encrypt all message in the communication. This is interesting because even the message containing the symmetric key can then be intercepted but since it is encrypted using the public key from the SSL, only the server can decrypt it.

Setup the SSL

Now that you can navigate to your website using your domain name, you will realise that this is not on HTTPS. So go to the crypto section and select SSL => FULL. Full SSL means that your connection is encrypted between visitor and CloudFlare. And it will also verify that the server has a SSL - but it does not perform validity check.

ssl

Next you need to make your users who visit your HTTP pages be redirected to your HTTPS pages. To do that go to the page rules. Click on Create Page Rule and add an Always use HTTPS page rule for your domain name with a wildcard to capture any url.

pagerule_icon

pagerule

Just wait a while and you should be able to visit your site under SSL!

Conclusion

When it is the first time buying a domain and setting up DNS records, it can be very tedious but if you understand every step and why are this step necessary, the process is easier to remember since you know that every step is mandatory. Today I showed how you can buy a domain name from a registrar and serve it over SSL for free with CloudFlare. CloudFlare also proposes lot more services like minification of CSS/JS and also a CDN. As always if you have any question leave it here or hit me on Twitter @Kimserey_Lam. See you next time!

Other post you will like!

Comments

Post a Comment

Popular posts from this blog

Microsoft Orleans logs warnings and errors

Microsoft Orleans logs warnings and errors Microsoft Orleans is a framework which helps building distributed system by implementing the actor model together with the concept of virtual actors, taking care of availability and concurrency. If you are unfamiliar with Microsoft Orleans, you can look at my previous blog post explaining the benefits of Microsoft Orleans . Even though Orleans promises to abstract the distributed system problems, there are instances where errors arise without us being able to understand what is going on. Lucky us, the logs are well documented… but only for those who can decrypt them. Today I will go through some of the errors and warnings which can be seen from silo and client so that you too can undestand what is going on. Enjoy! The code used to produce those errors can be found on my GitHub https://github.com/Kimserey/orleans-cluster-consul . 1. Client logs Logs on client appears with address {ip}:0 . 1.1. Can’t find implementation of interface An un...
Keep reading

A complete SignalR with ASP Net Core example with WSS, Authentication, Nginx

SignalR with ASP Net Core SignalR is a framework from ASP NET Core allowing us to establish a two way communication between client and server. This two way communication allows the client to send messages to the server but more importantly allows the server to push messages to the client. SignalR makes use of Websocket when available else it falls back to SSE or pulling. Today we will focus on how to setup SignalR to work with WSS, Websocket secure and how we can authenticate the user requesting to connect to our SignalR hub via Webscoket. Getting started with SignalR SSL encryption for Websocket Secure WSS Websocket Authentication with Identity Server 4 SignalR behind Nginx 1. Getting started with SignalR The Hubs are the main components of SignalR. It is an abstraction of a two way communication available for both client and server. Public functions from the hub can be called from the server code and can be called from the client. The frontend NPM package @aspnet/signalr ...
Keep reading

SDK-Style project and project.assets.json

SDK-Style project and project.assets.json Last week I encountered an issue with MSBuild while trying to run it from command line. The issue did not appear when using VisualStudio right click + build but only appeared when using msbuild.exe CLI directly with a clean project. Assets file 'C:\[...]\obj\project.assets.json' not found. Run a NuGet package restore to generate this file. When I first saw the error, few questions came to my mind which I will share today in 3 points: Overview of project.assets.json Slim SDK-Style project Mixing SDK-Style project and old projects Special shoutout to @enricosada who provided me with all the answers regarding the SDK-Style project. 1. Overview of project.assets.json project.assets.json lists all the dependencies of the project. It is created in the /obj folder when using dotnet restore or dotnet build as it implicitly calls restore before build, or msbuid.exe /t:restore with msbuild CLI. To simulate dotnet build (re...
Keep reading