Almost have it running

Ok… So I’ve ALMOST got it running… But all assets are missing which is a bummer… js, css and svg are coming up with 404 errors. I’m on Ubuntu 21 freshly installed. I followed the manual installation directions found here. I had an issue with nginx pulling in the frappe.conf twice and fixed that. So nginx is now running and happy and I found I needed to issue a “bench start” in another terminal to get the back-end running. I gather that’s a development piece, but don’t know otherwise how to get the daemons running.

Regardless, with bench running and nginx I get a login screen sans any graphics or markup.

One thing I notice is that paths are not mapping which may be perfectly fine and perhaps something that nginx is handling internally. For instance the one erpnext-logo.svg is found at the location below in the file system:

$ find . -name 'erpnext-logo.svg' -print
./apps/erpnext/erpnext/public/images/erpnext-logo.svg

But the webserver is looking for ./assets/erpnext/images/erpnext-logo.svg
Again that may be perfectly fine. I suspect that it’s just an nginx issue with the config (probably not) or something is up with my frappe stuff that is causing things to be located in the wrong places…?

Hi

Has bench build been tried?

Yes… I just did it a 2nd time… it finishes properly without any discernable errors/issues but results in no change with regards to my problem. I will state that I run the “bench build” while another terminal has “bench start” running. I don’t know if that’s the proper way to do it or not.

Hi

You need to force the build like below

bench build --force

And then

bench clear-cache

I’m back at it again today … I’ll give this a shot if I get stuck… Thanks!

I tried your suggestion and it’s basically bringing my raspberry pi 4b to its knees… I’ve got two ssh windows open – one is running “bench start” and the other “bench build --force”… There are still assets that never seem to get loaded as seen in the image below. I’m pretty much stumped… I’m guessing that I should not be running two benches at the same time… Once I kill the “bench build --force” then the RPI is able to act normally responsive again. Ideas??

if I pick one of the missing js files – I find it listed in the frappe-bench directory as shown below:

~/frappe-bench$ find . -name 'bootstrap-4-web.min.js' -print
./sites/assets/js/bootstrap-4-web.min.js

I don’t honestly know enough about frappe to understand the directory structure and why it can’t find files that are plainly present and available. Maybe it’s something with nginx?

Interestingly enough – IF I load the following link it works as expected:

http://192.168.1.100/sites/assets/js/bootstrap-4-web.min.js

I tried putting a symlink in so I could get rid of the “sites” reference but nginx is not going to follow the symlinks even though I added disable_symlinks off; in the config files… thoughts?

ok… I now understand what the issue is – it’s plainly visible after reviewing the nginx error log. All my files are owned by the Frappe user (frappay here :slightly_smiling_face: )… What user is being used to serve this stuff that it’s getting a permission denied?

2022/03/22 17:22:08 [crit] 2848#2848: *3 stat() "/home/frappay/frappe-bench/sites/site1.local/public//" failed (13: Permission denied), client: 192.168.1.229, server: site1.local, request: "GET / HTTP/1.1", host: "192.168.1.100"
2022/03/22 17:22:09 [crit] 2848#2848: *3 stat() "/home/frappay/frappe-bench/sites/assets/frappe/js/lib/jquery/jquery.min.js" failed (13: Permission denied), client: 192.168.1.229, server: site1.local, request: "GET /assets/frappe/js/lib/jquery/jquery.min.js HTTP/1.1", host: "192.168.1.100", referrer: "http://192.168.1.100/"
2022/03/22 17:22:09 [crit] 2848#2848: *4 stat() "/home/frappay/frappe-bench/sites/assets/js/frappe-web.min.js" failed (13: Permission denied), client: 192.168.1.229, server: site1.local, request: "GET /assets/js/frappe-web.min.js?ver=1647992801.0 HTTP/1.1", host: "192.168.1.100", referrer: "http://192.168.1.100/"
2022/03/22 17:22:09 [crit] 2848#2848: *6 stat() "/home/frappay/frappe-bench/sites/assets/css/frappe-web-b4.css" failed (13: Permission denied), client: 192.168.1.229, server: site1.local, request: "GET /assets/css/frappe-web-b4.css?ver=1647992801.0 HTTP/1.1", host: "192.168.1.100", referrer: "http://192.168.1.100/"
2022/03/22 17:22:09 [crit] 2848#2848: *7 stat() "/home/frappay/frappe-bench/sites/assets/css/erpnext-web.css" failed (13: Permission denied), client: 192.168.1.229, server: site1.local, request: "GET /assets/css/erpnext-web.css?ver=1647992801.0 HTTP/1.1", host: "192.168.1.100", referrer: "http://192.168.1.100/"
2022/03/22 17:22:09 [crit] 2849#2849: *8 stat() "/home/frappay/frappe-bench/sites/assets/css/login.css" failed (13: Permission denied), client: 192.168.1.229, server: site1.local, request: "GET /assets/css/login.css?ver=1647992801.0 HTTP/1.1", host: "192.168.1.100", referrer: "http://192.168.1.100/"
2022/03/22 17:22:09 [crit] 2849#2849: *9 stat() "/home/frappay/frappe-bench/sites/assets/js/bootstrap-4-web.min.js" failed (13: Permission denied), client: 192.168.1.229, server: site1.local, request: "GET /assets/js/bootstrap-4-web.min.js HTTP/1.1", host: "192.168.1.100", referrer: "http://192.168.1.100/"
2022/03/22 17:22:09 [crit] 2848#2848: *3 stat() "/home/frappay/frappe-bench/sites/site1.local/public//website_script.js" failed (13: Permission denied), client: 192.168.1.229, server: site1.local, request: "GET /website_script.js?ver=1647992801.0 HTTP/1.1", host: "192.168.1.100", referrer: "http://192.168.1.100/"
2022/03/22 17:22:09 [crit] 2849#2849: *8 stat() "/home/frappay/frappe-bench/sites/assets/js/erpnext-web.min.js" failed (13: Permission denied), client: 192.168.1.229, server: site1.local, request: "GET /assets/js/erpnext-web.min.js?ver=1647992801.0 HTTP/1.1", host: "192.168.1.100", referrer: "http://192.168.1.100/"
2022/03/22 17:22:09 [crit] 2849#2849: *9 stat() "/home/frappay/frappe-bench/sites/assets/erpnext/images/erpnext-logo.svg" failed (13: Permission denied), client: 192.168.1.229, server: site1.local, request: "GET /assets/erpnext/images/erpnext-logo.svg HTTP/1.1", host: "192.168.1.100", referrer: "http://192.168.1.100/"

Of course this isn’t helping!

drwxr-xr-x  6 root    root    4096 Mar 15 15:27 .
drwxr-xr-x 20 root    root    4096 Jan  9 20:08 ..
drwxr-x---  8 frappay frappay 4096 Mar 22 17:16 frappay

Notice the directory is blocking everyone from seeing anything in it… I guess I must have missed the step fixing the directory permissions… Doh!

Now it looks like this!! :100::boom::+1::+1::+1: