This is a review of HostUS‘s (affiliate links within this post) unmanaged Virtual Private Servers (VPS) where I have installed the control panel VestaCP.
I have a few VPS’s with HostUS namely because they are international. This blog is hosted on a VPS they provide in England. I have been with them since February 2015. It’s been over a year so I think I’m well informed to provide a review that is of my own opinion.
UPDATE: After almost 2 years of hosting with HostUS I have pulled the plug on 6 servers I had with them. Recently they had terrible slow nodes and very slow response times to support requests (when the nodes were slow). Read more for the in-depth review.
Security is paramount these days and visitors to your website want to know their browsing and transmission of data is 100% safe. How do you test this? At Quality SSL Labs of course! It’s time to secure your NGINX install once-and-for-all.
As of today, my blog is running Let’s Encrypt – the absolutely free SSL Certificate authority and my rating is A+ (I’m OK with that!) at Quality SSL Labs. Before with a default install of NGINX and VestaCP my rating was B.
If you hate those trailing slashes or perhaps you’re just a fan of good SEO practices then you’ll probably want to remove the trailing slashes from your WordPress installation and edit your NGINX configuration to make sure anything WITH a trailing slash is sent permanently (301 redirect) to the page without a slash.
NGINX is becoming more popular every second – and it’s because it’s super fast. In this tutorial I’m going to show you the difference between a 301 and 302 redirect in NGINX and how to implement them. But first, let’s know the difference.
301 redirects are what is known as permanent redirects. This tells search engines that the old page has been moved permanently.