Create Private PPTP VPN for personal use in Linode Cloud Hosting.

Nowadays many things are getting blocked by the government, and sometimes without even a valid reason. When something like this happen to you, you probably looking for some way to bypass these restrictions, and most of the times we look for free or cheap VPNs.

In today’s world, nothing is actually free, there is always something we are giving in return to those so called free providers and most of the time we are doing this unknowingly. User data is the most valuable asset in today’s business, and we are always sharing that info even without our knowledge.

And also, when we are using those free VPNs, we really don’t have any control over the data that we are accessing using it, as there could be some tacking configured or may be configured with a man-in-the-middle attack (MITM)..

So, I strongly suggest not to trust those providers blindly, as you could easily setup your own PPTP VPN from with 1TB data transfer every month with just 5$ a month fee. For this you have create a account in Linode. Here you will get a dedicated VM with 1 GB RAM, 1 Core CPU, 25 GB SSD, 1 TB Data transfer with 40 Gbps network In and 1000 Mbps Network Out and one dedicate IPV4 & IPV6 IPAddress.

Please follow the guide bellow to host your own private high speed PPTP VPN Server.


  • Open Linode Web for creating one account : Chick Here
  • Register your account with a credit card and Use promo code DOCS10 for $10 credit on a new account.
    (You need your credit cad for minimum $5 top-up, and you will get total $15 in your account)
  • Logon to your account.
  • You can select Nanode 1GB.
  • Select your preferred region and click Add this Linode!

Continue reading

Re-enabling Network Adapter in Azure VM (Resource Manager)

It is very common that sometimes we disabled the network adapter from VM to trouble shoot some network related issue, and after doing so we suddenly realize that we made a big mistake, especially if we do it on Azure VMs. Suddenly we lost all the communication to the VM, no RDP, no PowerShell, and VM got completely isolated from the network. If AWS, we could fix this very easily by adding one additional network adapter (ENI), but in Azure, it will be little bit tricky, coz currently Azure VM does NOT support adding or removing NICs after a VM is created, Multi-NIC can only be applied when a VM is created. So, fixing this will be bit trickier for Azure VMs. If you search “Disabled network card on Azure VM“, you will get multiple solution, but unfortunately those are not working with newer Azure VM (Resource Manager).

To fix this issue, you have to follow the steps bellow, and you will be able to re-enable the adapter.

  • Select VM from
  • Select Network interfaces
  • Select IP configurations
  • Change the Static IP to Dynamic and Save the settings
  • Wait till configuration gets updated.
  • Now again change it from Dynamic to Static and also change the IP Address to a new one for the same VNET and Save.
  • This will reboot the instance and after some time you will get the ping response from the new IP.
  • Now you have to follow the exact same steps to change the IP back to old one.
  • And finally you will able to get the VM with old IP.
  • If you wish, buy me a cup of coffee.