Create an account

Very important

  • To access the important data of the forums, you must be active in each forum and especially in the leaks and database leaks section, send data and after sending the data and activity, data and important content will be opened and visible for you.
  • You will only see chat messages from people who are at or below your level.
  • More than 500,000 database leaks and millions of account leaks are waiting for you, so access and view with more activity.
  • Many important data are inactive and inaccessible for you, so open them with activity. (This will be done automatically)


Thread Rating:
  • 385 Vote(s) - 3.52 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Teething troubles with Grav CMS

#1
I have followed the instructions on installing Grav + Admin on by Ubuntu 16.04 server running Nginx [here][1] and configured + restarted the Nginx server as explained

[To see links please register here]

.

I then browsed to `https://example.com/` where Grav is installed in the root folder. After going through the process of creating the admin user Grav shows me the Admin dashboard but with empty panels for Maintenance, Statistics etc each of which show a spinner. Examining the console log I found a 404 error for

[To see links please register here]


`vendor.min.js` does exist in the said folder and its cousin `admin.min.js?04b9d8febd` is loaded correctly according to the information on the Network tab of my Chrome debugger console.

I had trouble with permissions so I have temporarily recursively `chmod'd` the Grav folder to 777 so I doubt that there is an issue there.

What am I doing wrong here?

________
After examining my `/etc/nginx/sites-available/default` file I have found that it also has the following


location ~ /(\.htaccess|\.git|config|content|content-sample|lib|vendor|CHANGELOG\.md|composer\.(json|lock)){return 404;}

location ~* /(\.git|cache|bin|logs|backup|tests)/.*$ { return 403; }
location ~* /(system|vendor)/.*\.(txt|xml|md|html|yaml|yml|php|pl|py|cgi|twig|sh|bat)$ { return 403; }
location ~* /user/.*\.(txt|md|yaml|yml|php|pl|py|cgi|twig|sh|bat)$ { return 403; }
location ~ /(LICENSE\.txt|composer\.lock|composer\.json|nginx\.conf|web\.config|htaccess\.txt|\.htaccess) { return 403; }

Removing these lines and restarting the server "fixed" the problem but clearly is not a solution. My understanding of nginx configuration directives is rather limited. What do I need to change here so vendor.min.js does not get blocked?

[1]:

[To see links please register here]

Reply



Forum Jump:


Users browsing this thread:
1 Guest(s)

©0Day  2016 - 2023 | All Rights Reserved.  Made with    for the community. Connected through