Timeline for Why would graphite-webapp browser not display any body content?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 7, 2017 at 22:31 | comment | added | deniszh |
@fildred13 @james-shewey : yes, sorry, should mention Apache as well - but I have no example of Apache config. Please note that Nginx config above is from working configuration, it's pointing static files exactly to /opt/graphite/static
|
|
| Jul 7, 2017 at 16:16 | comment | added | fildred13 |
That is exactly correct. For those who come after me, the symptom of this problem is precisely what I described (the blank screen but functional header), and also the browser console displayed many 404's - all the js and css that builds the content of the page is static files which were not able to be found.) For some reason, python-whitenoise which I was using for static files was failing silently. Running the command as suggested here worked, of course. BUT - the STATIC_ROOT by default is /opt/graphite/static, so that is what you should point your webserver to (NOT /opt/graphite).
|
|
| Jul 7, 2017 at 16:11 | vote | accept | fildred13 | ||
| Jul 7, 2017 at 14:57 | comment | added | James Shewey | Are you sure they are even using nginx? My understanding is that graphite runs on apache by default | |
| Jul 7, 2017 at 10:44 | review | First posts | |||
| Jul 7, 2017 at 11:26 | |||||
| Jul 7, 2017 at 10:39 | history | answered | deniszh | CC BY-SA 3.0 |