Question

Nginx dosent redirect url.com/index or url.com/page to url.com/index.php or url.com/page.php

Posted April 4, 2020 303 views
Nginx

I have an Nginx server running on CWP. My site is set up at /public_html/ , whenever I load the url.com it loads the site properly, but when I load url.com/index it won’t load the index.php automatically while manual url.com/index.php works, same with other pages in the root dir like url.com/page gives an error but url.com/page.php works.

I found replacing, adding try_files $uri $uri/ /index.php?$args; in location block of /etc/nginx/conf.d/vhosts/url.com.ssl.conf should fix it

before

    location / {
        location ~.*\.(3gp|gif|jpg|jpeg|png|ico|wmv|avi|asf|asx|mpg|mpeg|mp4|pls|mp3|mid|wav|swf|flv|html|htm|txt|js|css|exe|zip|tar|rar|gz|tgz|bz2|uha|7z|doc|docx|xls|xlsx|pdf|iso|woff|ttf|svg|eot|sh)$ {
            root /home/blitz/public_html;
            expires max;
            try_files $uri @backend;
        }

after

    location / {
        location ~.*\.(3gp|gif|jpg|jpeg|png|ico|wmv|avi|asf|asx|mpg|mpeg|mp4|pls|mp3|mid|wav|swf|flv|html|htm|txt|js|css|exe|zip|tar|rar|gz|tgz|bz2|uha|7z|doc|docx|xls|xlsx|pdf|iso|woff|ttf|svg|eot|sh)$ {
            root /home/blitz/public_html/;                  
            expires max;
            try_files $uri $uri/ /index.php?$args;
        }

Changed this config but still not working. I am I doing this wrong or is it the wrong solution.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
2 answers

Hi there @notKiran,

Usually what I would use to hide the file extensions would be the following rule:

try_files $uri $uri.php $uri/ =404;

Hope that this helps!
Regards,
Bobby

Thanks, @bobbyiliev for saving the day, this actually worked, can you tell whats the meaning of this - tryfiles $uri @backend; and this tryfiles $uri $uri/ /index.php?$args; as I am quite new to this?

  • Hi there @notKiran,

    No problem at all! Happy to hear that it is working!

    The @backend means that the traffic should be passed to your backend service, you probably have a backend instance specified somewhere in the beginning of your Nginx configuration file.

    Hope that this helps!
    Regards,
    Bobby

Submit an Answer