DevOps Engineer
fail2Ban is a very handy tool to prevent a lot of unwanted traffic from consuming bandwidth on your servers. It’s a minimal and relatively simple IDS Type Tool that comes with some predefined filters to automatically lockout potentially dangerous or bandwidth-consuming type attacks.
/etc/fail2ban/filter.d/custom.conf
[Definition]
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… Read more
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
yum install -y mod_ssl mod_rewrite
a2enmod rewrite a2enmod ssl
<VirtualHost *:80>
ServerName www.yourdomain.com
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1 [R,L]
</VirtualHost><VirtualHost *:80> ServerName www.yourdomain.com Redirect permanent / https://www.yourdomain.com/ </VirtualHost>
Install and enable apache2 proxy modules
sudo a2enmod proxy sudo a2enmod proxy_http sudo a2enmod proxy_balancer sudo a2enmod lbmethod_byrequests sudo systemctl restart apache2
proxies all requests (“/”) to a single backend:
ProxyPass "/" "http://www.example.com/"
to point to the reverse proxy, instead of back to itself, the ProxyPassReverse directive is most often … Read more
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.
a2enmod rewrite
RewriteEngine on
RewriteCond %{HTTP_HOST} ^www.yoursite.com
RewriteRule