Thank you Francis - the "try" line was key :)by maplesyrupandrew - Nginx Mailing List - English
I'm using the Angular ui-router which uses states to control the routes. Meaning that all request should serve the same index.html file, and the JavaScript worries about loading in appropriate content. The .htaccess rules that control the same thing are below: <ifModule mod_rewrite.c> RewriteEngine On # Required to allow direct-linking of pages so they can be processed by Anguby maplesyrupandrew - Nginx Mailing List - English
Thanks for the response! I made that change, and I think what was really giving the 404 was that I had changed permissions on the `index.html` file, but not on the var/www/ folder, which I needed so that the nginx user group could access it. Thanks!by maplesyrupandrew - Nginx Mailing List - English
I have a pretty standard test nginx configuration file (/etc/nginx/sites-available/default) that was configured to serve a sample html document. Here's the modified portion of the configuration file. upstream auth{ server 127.0.0.1:3000; } server { listen 80 default_server; root /var/www/index.html; # Make site accessible from http://localhost/by maplesyrupandrew - Nginx Mailing List - English
![]() |
![]() |
![]() |
![]() |
![]() |