PufferPanel UI displaying in HTML after altering URL settings #78
Replies: 4 comments
-
LordRalex wrote at Jan 16 2016 19:32:25 UTC: Can you open your browser's javascript console and report what URLs it is trying to load those resources from, and if you can access them from that machine? |
Beta Was this translation helpful? Give feedback.
-
LordRalex wrote at Jan 16 2016 19:32:25 UTC: Can you open your browser's javascript console and report what URLs it is trying to load those resources from, and if you can access them from that machine? |
Beta Was this translation helpful? Give feedback.
-
TNSPredator wrote at Jan 16 2016 19:32:25 UTC: The console's output provides me with a 404 error. When trying to retrieve assets from the following URLs: GET http://192.168.1.82/assets/css/bootstrap.css [HTTP/1.1 404 Not Found 0ms] GET http://192.168.1.82/assets/css/pufferpanel.css [HTTP/1.1 404 Not Found 0ms] GET http://192.168.1.82/assets/javascript/admin.min.js [HTTP/1.1 404 Not Found 0ms] GET http://192.168.1.82/assets/javascript/bootstrap-notify.min.js [HTTP/1.1 404 Not Found 0ms] GET http://192.168.1.82/assets/javascript/admin.min.js [HTTP/1.1 404 Not Found 0ms] GET http://192.168.1.82/assets/javascript/bootstrap-notify.min.js [HTTP/1.1 404 Not Found 0ms] Here is a full log: http://hastebin.com/ajaforanuq.vhdl |
Beta Was this translation helpful? Give feedback.
-
TNSPredator wrote at Jan 16 2016 19:32:25 UTC: Solution: After pinpointing the problem (404 error) I figured that my Nginx "pufferpanel" config was invalid. The error was due to the fact that in the "location /assets" block I had the following: "try_files /app/&uri =404;" instead of "try_files /app/$uri =404;". After changing the & to $ and then reloading Nginx everything worked as intended. |
Beta Was this translation helpful? Give feedback.
-
TNSPredator wrote at Jan 16 2016 19:32:25 UTC:
Hello
I have recently installed PufferPanel on a VirtualBox machine using a bridged network configuration. The machine currently has the following internal address assigned to it: 192.168.1.82. Upon installing PufferPanel the UI is displayed in HTML when navigating to 192.168.1.82 via my web browser (Iceweasel). I know this is normal if the URL settings are invalid which they were to begin with. I altered these settings to the following:
http://picpaste.com/pics/Screenshot_from_2016-01-16_18_15_16-N21lLF3C.1452968254.png
However upon clicking "Update" the PufferPanel web pages still display in HTML.
Note: When using another virtual machine running on NAT configuration (which has PufferPanel installed) whenever I run nginx and then connect to 192.168.1.82 with Iceweasel I am able to view the UI with no issues.
Beta Was this translation helpful? Give feedback.
All reactions