DevOps Engineer
Uncomment the required php version.
yum install -y http://rpms.remirepo.net/enterprise/remi-release-7.rpm yum install -y yum-utils # yum-config-manager --enable remi-php70 # yum-config-manager --enable remi-php71 # yum-config-manager --enable remi-php72 yum-config-manager --enable remi-php73 yum -y install php # php-mcrypt php-cli php-gd php-curl php-mysql php-ldap php-zip php-fileinfo php -v
You can restrict access to your website or some parts of it by implementing a username/password authentication. Usernames and passwords are taken from a file created and populated by a password file creation tool, for example, apache2-utils.
sudo htpasswd -c /etc/httpd/.htpasswd admin or sudo htpasswd -c /etc/nginx/.htpasswd admin
Create additional user-password pairs. Omit the -c flag because the file already exists
server {
...
auth_basic "Administrator’s Area";
auth_basic_user_file /etc/nginx/.htpasswd;
location /public/ {
auth_basic off;
}
}<VirtualHost *:80>
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
<Directory "/var/www/html">
AuthType Basic
AuthName "Restricted Content"
AuthUserFile /etc/httpd/.htpasswd
Require valid-user
</Directory>
</VirtualHost><VirtualHost *:80>
ServerAdmin webmaster@localhost
ProxyPass / http://localhost:990/
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
<Location />
AuthType Basic
AuthName "Restricted Content"
AuthUserFile /etc/httpd/.htpasswd
Require valid-user
</Location>
</VirtualHost>You can restrict access to certain parts of your website using Nginx’s inbuilt authentication and authorization mechanism based either on your client’s I.P, by prompting for a login prompt or both.
location /private/ {
allow 192.168.1.1/24;
allow 172.16.0.1/16;
allow 127.0.0.1;
deny all;
}A reverse proxy is a server that sits between internal applications and external clients, forwarding client requests to the appropriate server. While many common applications, such as Node.js, are able to function as servers on their own, NGINX has a number of advanced load balancing, security, and acceleration features that most specialized applications lack. Using NGINX as a reverse proxy enables you to add these features to any application.
server {
listen 80;
listen [::]:80;
server_name example.com;
location / {
proxy_pass http://localhost:3000/;
proxy_buffering off; # optional
proxy_set_header X-Real-IP $remote_addr; # optional
proxy_set_header Host $host; # optional
}
}sudo nginx -t sudo nginx -s reload
This tutorial will show you how to redirect a www URL to non-www, e.g. www.example.com to example.com, with Nginx. We will also show you how to redirect in the other direction, from a non-www URL to www.
In order to set up the desired redirect, www.example.com to example.com or vice versa, you must have an A record for each name.
server {
server_name www.example.com;
return 301 $scheme://example.com$request_uri;
}sudo systemctl restart nginx
server {
server_name example.com;
return 301 $scheme://www.example.com$request_uri;
}sudo systemctl restart nginx
All login credentials transferred over plain HTTP can easily be sniffed by a MITM attacker, but it is not enough to encrypt the login forms. If you are visiting plain HTTP pages while logged in, your session can be hijacked, and not even two-factor authentication will protect you. To protect all info sent between your visitors – which includes you – and your web server, we will redirect all requests that are coming over plain HTTP to the HTTPS equivalent.
server {
listen 80 default_server;
server_name _;
return 301 https://$host$request_uri;
}server {
listen 80;
server_name foo.com;
return 301 https://foo.com$request_uri;
}server {
listen 443 ssl default_server;
server_name foo.com;
}
server {
listen 443 ssl;
server_name bar.com;
}
# and so on...The Require provides a variety of different ways to allow or deny access to resources. In conjunction with the RequireAll, RequireAny, and RequireNone directives, these requirements may be combined in arbitrarily complex ways, to enforce whatever your access policy happens to be.
example:
<VirtualHost *:80>
ServerName example.net
Documentroot /var/www/html/
<Location />
Require ip 192.168.0.0/24 10.0.0.2
</Location>
</VirtualHost>