nginx routing problems?

evij

Dear Marc,
I'm trying right now to get automad (1.10.9) running on an nginx. But unfortunatelly only the startpage is working. I already showed my admin the nginx configuration you mention in the docs, and he told me, he changed the routing rules like this way.
I activated the debugging and I can see that every request (/dashboard) gets still resolved to -> /
https://helmutmark.com/dashboard
Do you have any Ideas how to narrow down this problem?

thanks in advance
evgenij

mad

evij Hi, when all requests are resolved to / it means the Nginx is not rewriting at all. It would be great to take a look at the nginx.conf that is actually used. A working example can be found in the official Docker image. That one also uses Nginx.

evij

mad Hi, thank you for your help!

Here is the nginx.conf:

user hmwebspace www-data;
worker_processes auto;
pid /run/nginx.pid;
include /etc/nginx/modules-enabled/*.conf;

events {
	worker_connections 4096;
	# multi_accept on;
}

http {

	##
	# Basic Settings
	##

	sendfile off;
	aio threads;
	directio 8m;
	tcp_nopush on;
	tcp_nodelay on;
	keepalive_timeout 300s;
	types_hash_max_size 2048;
	server_tokens off;

	# server_names_hash_bucket_size 64;
	# server_name_in_redirect off;

	include /etc/nginx/mime.types;
	default_type application/octet-stream;

	# HTTP settings & POST limit
	client_header_buffer_size 8k;
	client_max_body_size 1024M;
	keepalive_disable none;

       # Lingering
       lingering_close on;
       lingering_time 90s;
       lingering_timeout 30s;

	##
	# SSL Settings
	##

	ssl_protocols TLSv1.2 TLSv1.3;
	ssl_prefer_server_ciphers on;
        ssl_ciphers 'TLS_CHACHA20_POLY1305_SHA256:TLS_AES_256_GCM_SHA384:ECDHE-RSA-AES256-GCM-SHA384:TLS_AES_128_GCM_SHA256:ECDHE-RSA-AES128-GCM-SHA256:TLS_AES_128_CCM_8_SHA256:TLS_AES_128_CCM_SHA256';
	ssl_session_cache shared:SSL:32m;
        ssl_session_timeout 5m;
        ssl_stapling on;
        ssl_stapling_verify on;

	##
	# Logging Settings
	##

	access_log /var/log/nginx/access.log;
	error_log /var/log/nginx/error.log;

	##
	# Gzip Settings
	##

	gzip on;

	gzip_vary on;
	gzip_proxied any;
	gzip_comp_level 6;
	gzip_buffers 16 8k;
	gzip_http_version 1.1;
	gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;

	##
	# Virtual Host Configs
	##

	include /etc/nginx/conf.d/*.conf;
	include /etc/nginx/sites-enabled/*;
}

and this is the default-site.conf:

##
# You should look at the following URL's in order to grasp a solid understanding
# of Nginx configuration files in order to fully unleash the power of Nginx.
# https://www.nginx.com/resources/wiki/start/
# https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/
# https://wiki.debian.org/Nginx/DirectoryStructure
#
# In most cases, administrators will remove this file from sites-enabled/ and
# leave it as reference inside of sites-available where it will continue to be
# updated by the nginx packaging team.
#
# This file will automatically load configuration files provided by other
# applications, such as Drupal or Wordpress. These applications will be made
# available underneath a path with that package name, such as /drupal8.
#
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
##

# Default server configuration
#
server {
	listen 80 default_server;
	listen [::]:80 default_server;

	# SSL configuration
	#
	listen 443 ssl http2 default_server;
	listen [::]:443 ssl http2 default_server;

	ssl on;
	ssl_certificate /etc/nginx/www.helmutmark.com_gandi_full.crt;
	ssl_certificate_key /etc/nginx/www.helmutmark.com_gandi.key;
	ssl_dhparam /etc/nginx/dhparams.pem;

	# include snippets/snakeoil.conf;

	root /var/www/html/webspace;

	# Add index.php to the list if you are using PHP
	index index.php index.html;

	server_name _;

	location / {
		try_files $uri $uri/ /index.php$is_args$args;
	}

	# pass PHP scripts to FastCGI server
	#
	location ~ \.php$ {
		include snippets/fastcgi-php.conf;
	
		# With php-fpm (or other unix sockets):
		fastcgi_pass unix:/run/php/php8.1-fpm.sock;
		fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
		# With php-cgi (or other tcp sockets):
		#fastcgi_pass 127.0.0.1:9000;
	}

	# deny access to .htaccess files, if Apache's document root
	# concurs with nginx's one
	#
	location ~ /\.ht {
		deny all;
	}
}

I hope this helps.

thanks!
evij

mad

evij Hi, it looks quite different as the one in the docs. Also it is important to provide the correct PHP environment variables such as the PATH_INFO. Those should be in inside the included file in the PHP block. Maybe you take a look into that file as well.

rpfeiffer

Hei!
PATH_INFO is included in the fastcgi-php.conf. Apart from the nginx web server there is also a reverse proxy in front of the application. The proxy does not alter anything at all. All the rewriting should be done by the try_files directive. Apart from using a Debian default skeleton configuration all the directives of the documentation were added. Is there anything else that should be configured?

Best,
René.

mad

rpfeiffer Hi, the requested page can be determined from either the query string or an environment variable such as PATH_INFO, ORIG_PATH_INFO or REQUEST_URI.

Therefore there are two options that are worth trying:

Rewriting the request to the query string:

location / {
    try_files $uri $uri/ /index.php?$request_uri;
}

Checking whether PATH_INFO is populated correctly. The provided value can sometimes be just an empty string.

I guess the first option is the safest. However the second option should work fine as well. Hope that helps.