apache

Building a resilient web server

Across every industry, the operational risks of cyber threats are escalating. Automated bots, denial-of-service attacks and vulnerability scanners are increasingly common. For businesses operating in Australia and globally, implementing resilient, proactive security measures is essential to ensure business continuity and protect customer trust.

Securing sensitive content is essential for protecting data integrity and user privacy. One effective way to implement security is by restricting access to specific directories or resources using either Apache or Nginx authentication tools. This provides a comprehensive reference for configuring password protection on both Apache and Nginx web servers using the htpasswd utility.

Attempting to load changes in a staging site and the bountiful error page of

Whilst updating nodejs and npm on a Centos 6 or 7 server running Apache, I hit a few walls and as a matter of process found some commands that are handy to run before doing a deep dive in Google.

Cleaning the cache

sudo yum clean all
rm -rf /var/cache/yum/*

To make the cache

sudo yum clean all; sudo yum makecache

If you want to run several commands use semi-colon as noted above.

This page shows a growing list of common commands for viewing and managing your Centos server.

ls syntax
$ ls [options] [file|dir]

ls command main options:

Installing Laravel on an Apache server was going to be a no fuss process said no developer!  Research done.  Documentation looks good and easy to follow.  Time to load Laravel.

The set-up

The install notes on Laravel are easy to follow.  Beginning with checking that your server is able to install Laravel.

I need to set the default php-version of a subscription to php7.3.  The current server php version is PHP 7.1.33 (cli) (built: Oct 25 2019 11:33:58) ( NTS ).

Using a shell program (I used Terminal) from the home directory I ran:

export PATH=/opt/plesk/php/7.3/bin:$PATH;

centos 6 use

service httpd restart

centos 7 use

(104)Connection reset by peer: mod_fcgid: error reading data from FastCGI server

Set up:

• Plesk Obsidian 18.0.28
• Centos 7

Like any error that pops up, the real check is how do you react?

A recent attempt to run an update composer (regular activity for many of us), I had a memory limit issue.  This was surprising because the memory setting via Plesk is set to 2G.  Yet through Terminal it was showing only 128MB.  What gives??  

The error I was seeing: