NGINX Install

[SeanTurner71]

Running into several issues programming the Pi. The main show stopper is installing NGINX. After running "sudo apt-get install nginx" I get nothing but 404 errors. Any insights?

[rdudhagra]

Hmm, few things to debug/paste the output of here...

1. I assume you followed the tutorial in the build guide...including modifying the config files exactly/etc
2. What version of Raspbian are you running? Buster should be fine
3. Can you try the following:

sudo systemctl restart nginx
sudo systemctl status nginx # paste the output of this here
journalctl -xe # paste the output of this here

This will tell us if nginx is starting correctly.
4. Can you confirm the ports set in .env in the website folder (should be port 3000)?
5. Is your server running? Run ps aux | grep node and see if anything pops up.

Will need more info to debug further, but hopefully this is a good start...let me know if you find the solution though!

[SeanTurner71]

I have a few more things I want to try but here are a few pics. First one is what looks like errors during install. second one is the original 404 errors when trying to nginx part, Third is the output to the commands you asked about. I have tried Pi OS with desktop and recommended software, Pi OS with desktop and lite. I'll update if I find anything new.

[rdudhagra]

Oh, didn’t understand your question at first.
Can you try running sudo apt-get update and reinstalling nginx (if you haven’t already)? Also are you on your home WiFi or on a school/company network that maybe has a more restrictive firewall?

[SeanTurner71]

That did it. I think my Pihole setup might have been causing an issue. The website is not working but I have a nginx splashscreen and I see errors in terminal involving ports so I can work on that. Thanks again. I'll let you know if I run into any other issues.

[rdudhagra]

Sounds good, no problem! Yea feel free to post more logs/screenshots/etc... if you run into anymore issues

[SeanTurner71]

OK. Made it a bit further. It will load a file and print without issue. Can use the website no prob. The problem is that around 50% of the tracks I try to load seem to crash the server. If I just use the ip page I get a 503 error. If I go to IP:3000 I get a network error. I read on another post where that could be due to corrupt tracks. Here are some "ps aux | grep node" shots before and after crash

[rdudhagra]

1. In my experience, only inwards_sunburst has caused me issues, but I haven't made anything on sandify
2. Just avoid really long tracks. Remember that at the end of the day, the server is converting each line of the .thr file into many many gcode commands, and so for a long file the Pi will have to do an insane number of trig calculations. I'm sure there are many optimizations I could make to improve speed/memory efficiency, but I probably won't get around to making them for a while. That being said, feel free to poke around and make a pr if that's something you're interested in!
3. It's very easy. Just install NodeJS for your platform (very easy to google), download the repo somewhere, and npm install and npm start to run. Let me know if you run into problems with this though...there might be some quirks with npm install that I've forgotten about.
4. Probably? If you think the investment of a 4/8 GB Pi 4 is worth it, then yea I think it could make a difference. Although it'll still take forever to process, because of the CPU limitations.

[SeanTurner71]

It turns out I had a pi4 4gig laying around. It ended out giving me a timeout error of some sort. So the memory issue maybe was fixed but then another one pops up. I guess I'll just stay away from that track for the near future. Thanks again for helping me out. Hopefully it all goes smoothy from here on out.
edit: Well on reboot it might have done it. It seems to be printing something

[rdudhagra]

Aha, ok yea the timeout error is what I've seen on my setup. Although, I find it weird that you've run into memory issues and I haven't (I'm using a Pi 3B+).

Based on the screenshot you posted the webserver probably stopped processing half-way through. From the looks of it the gcode has been created, but not the preview images. So if you don't really care about those this should be fine.

No worries, glad I could help. Good luck on your table—would love to see some pictures when you're done!

[SeanTurner71]

Yea I have a Pi 3B+ also so that's weird. I just moved the flash card to the Pi4. No other changes. The timeout was the 1800 seconds in nginx proxy settings I think.

[rdudhagra]

Yea so the way I currently have it the server will only respond once ALL the processing is done. So the NGINX proxy will definitely time out before some of these big .thr files finish. You could try making this timeout something much larger like 86400 (24 hrs) and see if that helps. I'm not sure if closing the website after the file has been uploaded to the server (no easy way to see when this happens, but try the network tab in your browser's "inspect element" panel) will cause the server-side processing to terminate—if it doesn't then you could just put a track to process overnight/etc.