What is OpenLiteSpeed?

OpenLiteSpeed ​​is the open-source version of LiteSpeed ​​WebServer Enterprise. It has all the necessary features found in LiteSpeed ​​WebServer including LScache.

This is the version for high-traffic websites. However, it does not integrate into any server administrator like DirectAdmin or cPanel.

The advantage of OpenLiteSpeed ​​is that it helps to reduce bandwidth usage, extremely fast technology, good support for external applications, SSL/Security Control support, etc.

What is Apache?

Apache (or Apache HTTP Server) is also open source web server software, developed and operated by the Apache Software Foundation. It can be said that Apache is one of the oldest web servers and is trusted by many users.

The advantage of Apache is that it is a stable free and open-source software. Apache also regularly updates security patches, the configuration is user-friendly, cross-platform, and has a large user community so it can support you at any time.

What is NGINX?

Similar to Apache, Nginx is also a famous and extremely popular open-source web server software. Although Nginx was originally used to serve HTTP web pages, it is now used as a reverse proxy, HTTP load balancer, and email proxy.

The advantage of Nginx is that it can handle more than 10,000 connections with low memory at the same time. In addition, you can use Cache to speed up Reverse Proxy, Apache also has flexible configuration and the ability to save query logs.

OpenLiteSpeed ​​– Apache – NGINX – which is the best web server?

This is a question many people ask when choosing to use these web servers. So between OpenLiteSpeed, Apache, NGINX, which webserver should you choose?

The answer to this question is not an easy one. There is no one-size-fits-all solution to choose Nginx over Apache or LiteSpeed ​​over Nginx. If you find yourself in a position where you might choose one over the other, you’ll really want to do your research and dig into how your users will use the sites running on the server and technology. that those sites are using, as that will help you come to a decision.

Apache is a great choice for Admins and Hosts who might want something very customizable as it has a rich collection of precompiled modules that can be added. These modules range from anything from authentication schemes to package-specific support for PHP, TCL, Python, Ruby, and more.

Apache is also reliable, stable, and considered beginner-friendly when setting it up for the first time. Because Apache is so widely used, it receives regular security and feature updates and has a large base to support.

Also, one important thing to remember – Apache runs applications that use CGI very well. For example, while Nginx technically supports CGI scripts, setting it up isn’t easy.

One feature of Apache that many criticize is its use of the .htaccess file to control things like rewrites and search engine indexing. Once these files are enabled, Apache must navigate the entire directory leading back to the parent directory and execute the commands listed in each of these .htaccess files. As you can imagine, this increases load times and consumes server resources.

On the other hand, Nginx can act as a reverse proxy in front of Apache or as its own web server, and there is no equivalent feature for .htaccess files. Applications written in Python and Ruby are known to be highly performant when running on the Nginx web server. With a load balancer, some optimizations, and Nginx, you can have a super performant setup. Nginx is also notoriously difficult to set up compared to contemporary Apache.

Please try to set up a test environment for the 3 web servers above.

As you all know about WordPress, caching is very important. So we have to make sure to use a suitable caching solution for each server in this test.

All of our tests were done with Keep-Alive enabled as well as pairing each server with a suitable cache option. And the result we got was that OpenLiteSpeed ​​outperformed NGINX and Apache in all tests.

The post Openlitespeed vs Nginx vs Apache, which is the best web server? appeared first on King Host Coupon.

One of the common tasks for running the Nginx Web Server is transferring the data stream from the HTTP protocol over the HTTPS (more secure version) of the website.

Unlike HTTP, all requests and responses are sent in unencrypted plain text. HTTPS uses TLS/SSL to encrypt the transmission between the client and the server.

This article will help you know how to configure HTTP to HTTPS redirect using Nginx.

To configure redirects, you must modify the Nginx configuration file, which is usually located in /etc/nginx/nginx.conf or /etc/nginx/sites-available, /usr/local/nginx/conf and /usr/local/ etc/nginx.

Once you have finished editing the configuration file, you must save your edits and exit. Then you reload the Nginx service by command below:

systemctl reload nginx

Redirect a website

You have multiple websites and only want some to redirect to HTTPS. Open the Nginx configuration file and insert the following code:

server {
listen 80 default_server;
server_name domain.com www.domain.com;
return 301 https://$host$request_uri;
}

Meaning of each line:

• listen 80 – block server will receive incoming data at Port 80
• server_name domain.com www.domain.com – the domain name of the server (you change this information to match your domain name)
• return 301 https://$host$request_uri – redirect traffic to the HTTPS version of the site

Redirect all websites on the server

If all the websites hosted on the server use HTTPS and you don’t want to create separate server blocks for each site, you can create a master server block to redirect all HTTP requests to HTTPS.

Create the main server block in the Nginx configuration file:

server {
listen 80 default_server;
server_name _;
return 301 https://$host$request_uri;
}

Parameter server_name _; will take any website’s hostname.

Only receive SSL Certificates connections

Add the following code to make the server accept only SSL connections on Port 443:

server {
listen 443 ssl default_server;
server_name my_website.com;
}

Note:

• You can add a new server block for another website.

Redirect Domain

This happens when you want to change the domain name extension (like .net or .org, info) to all .com domains or you want to redirect from the old domain to the new domain.

server {
listen 80;
listen 443 ssl;
server_name www.old_domain.com;
return 301 $scheme://www.new_domain.com$request_uri;
}

Redirect from www to non-www

When you want the website link to not appear www, enter the following code:

server {
server_name www.domain.com;
return 301 $scheme://domain.com$request_uri;
}

It works as well as a website redirects.

When the configuration is complete, all traffic from HTTP will automatically switch to HTTPS. Checking the site will return an HTTP status code “301 redirect”. You use the curl tool to check, type the command:

curl -I http://domain.com/

If you see “HTTP/1.1 301 Moved Permanently” and “Location: https://domain.com” then you are successful.

Good luck to you!

The post How to Redirect HTTP to HTTPS with Nginx Web Server? appeared first on King Host Coupon.

What are the benefits of installing SSL on NGINX?

If you are still wondering about the benefits of installing SSL, you can refer to the following benefits:

• More trusted by search engines ( Google, Bing..)
• Websites with a more secure HTTPS connection
• Your website becomes more professional in the eyes of visitors
• Minimize network security problems that are extremely unpredictable

Install SSL on NGINX for free with Let’s Encrypt

If you have forgotten how to SSH into the server with Putty, you can review this article.

Step 1: Remove the previous Certbot installation packages

yum remove -y certbot

Step 2: Install Certbot

Currently, the best way to install is through the EPEL repository.

Enable access to the EPEL repository on your server by typing

yum install -y epel-release

Use the following command to download the certbot-nginx package:

yum install -y certbot-nginx

Step 3: Open the firewall port

If you are running a firewall, make sure that ports 80 and 443 are open

firewall-cmd --zone=public --add-port={80,443}/tcp --permanent

firewall-cmd --reload

Type the following command to check

firewall-cmd --list-port

Step 4: Get an SSL certificate

Install the certificate automatically with the following command:

certbot --nginx -d example.com -d www.example.com

It will run certbot with the –nginx plugin to reconfigure Nginx, use -d to determine the valid name of the certificate

Step 5: Auto-renew

By default, LetsEncrypt certificates are only valid for 90 days, so we encourage you to set up automatic renewal of your SSL certificates.

Try before executing the command (create, renew…) for real, can add the option –dry-run at the end of the command. Such as

certbot renew --dry-run

If sure, type the command

certbot renew

Note: If you type the command with LetsEncrypt incorrectly, the error is too much, it will block you from working for about 1 hour.

The automatic renewal command applied to Certbot is located in one of the following files and paths:

/etc/crontab

/etc/cron.*/*

systemctl list-timers

Set up cron jobs to auto-renew

crontab -e 0 0 15 * * /usr/bin/certbot renew --post-hook "systemctl restart nginx" >> /var/log/certbot-renew.log

This line will run the renewal command at 24 hours on the 15th of each month, then save the log to the file /var/log/certbot-renew.log for easy to viewing.

Step 6: Check Certbot working

Once done, open a browser to access the domain name you just installed SSL, if you see the image below, it has been successfully installed. Congratulation!

Through this article KingHostCoupon has helped you know how to install the free Let’s Encrypt SSL for Nginx on CentOS 7. If you have any suggestions, you can leave a comment below.

You can find more information in the articles at:

• http://nginx.org/en/linux_packages.html#RHEL-CentOS
• https://www.nginx.com/resources/wiki/start/

The post How to Install Let’s Encrypt SSL for NginX on CentOS 7 appeared first on King Host Coupon.