server 500 error - 'Internal server error' on Nginx
Finding the issue with a server 500 error
The Nginx error logs are showing too much detail.
Nginx logs and test
There are no errors in the nginx log and sudo nginx -t looks fine
sudo nginx -tResponse
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
Listening to services running that use port 80
Listen in on the ports being used on your server. To do so, run the command
netstat -a | grep tcpIf netstat is not install, then you'll be prompted to run the install script
sudo apt install net-toolsResponse
nginx 13: Permission denied and pread() /etc/nginx/sites-enabled/ckan failed (21: Is a directory)
How to set up password authentication with Nginx on Ubuntu 20.04
Goal: Restrict content access through username and password entry on an Nginx server.
1: Apache Utilities Package
First, update your server’s package index:
sudo apt updateCheck if the utilities package exists in your environment by executing the command
dpkg --get-selections | grep apacheResponse:
How to set up password authentication with Apache or Nginx on Ubuntu
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.
Run Drupal 9 with Composer + Docker-compose + Nginx + MariaDB + PHP8.1
Running Docker
Dangerous word... I'm assuming that Docker is installed. Don't know how to check? Using Terminal (I prefer iTerm2), run the following command
docker -D info
The set-up
Go to your project directory, and create a docker folder and a “docker-compose.yml” file:
Configure Nginx SSL + force HTTP to redirect to https and force non-www to www using Nginx configuration file only
Forcing https and www or non-www is a process that I was a custom to through .htaccess. In fact I had become very strong at managing and working my .htaccess files. However, what I had become strong in one area, I was oblivious to using other methods. My bad.
Nginx: 413 – Request Entity Too Large Error and Solution
Working in Drupal 9.x, I was loading images via the Media module. Below 1 mb no issue. Any thing over - nothing. Nothing as in no response when loading.
An interesting situation, as I had already changed the php.ini file where the following updates occured:
; Maximum allowed size for uploaded files. ; http://php.net/upload-max-filesize upload_max_filesize = 2M
Had changed to