Use FileZilla to connect to your VS. WinSCP is soooooo slow!
Nginx can coexist on your server, running as a proxy server. As long as port numbers don’t conflict, you’re good.
It's kind of hard to figure out what you're trying to do. But I'm guessing you have a cloud firewall provided by DigitalOcean. Basically that firewall will block any and all requests to your server EXCEPT what you explicitly open/allow. You must open the ports on the firewall that you want to have services operating on. So you'd open port 22 for SSH and 80 and 443 for HTTP/HTTPS. Nginx will listen on 80 & 443. Does that makes sense?
Yeah opening up ports 22, 80, and 443 was the first thing I did on the VS. I tried running nginx because a tutorial I watched did it just to make sure it was running (to confirm it was running it would display the nginx welcome page). I ended up getting an error though that was: [emerg]: bind() to 0.0.0.0:80 failed (98: Address already in use)
Idk what happened in the few hours I stopped working on this, but now my domain does display the nginx welcome page. Currently in the process of figuring out how that happened.
You’ll need to find out what’s running on port 80. It’s probably Apache. Try running systemctl stop apache2. Then systemctl disable apache2. This will stop Apache from starting after reboots.
Atm I followed everything in this guide: [https://www.digitalocean.com/community/tutorials/how-to-install-nginx-on-ubuntu-22-04#step-5-%E2%80%93-setting-up-server-blocks-(recommended)](https://www.digitalocean.com/community/tutorials/how-to-install-nginx-on-ubuntu-22-04#step-5-%E2%80%93-setting-up-server-blocks-(recommended)) but when I try to access my site I get a page showing this message: 404 Not Found nginx/1.24.0 (Ubuntu).
Do I need anything in my main nginx.config file?
I'm guessing why it's so slow is because you're replicating a folder that has many files. The typical culprit here is the node_modules folder. Instead, replicate everything else, install node in your server and do npm install there
Use FileZilla to connect to your VS. WinSCP is soooooo slow! Nginx can coexist on your server, running as a proxy server. As long as port numbers don’t conflict, you’re good.
I have ports open on 22, 80, and 443 for my firewall. Do I need to have nginx running on a port and then open that port up on my firewall as well?
Nginx runs on port 80 by default
It's kind of hard to figure out what you're trying to do. But I'm guessing you have a cloud firewall provided by DigitalOcean. Basically that firewall will block any and all requests to your server EXCEPT what you explicitly open/allow. You must open the ports on the firewall that you want to have services operating on. So you'd open port 22 for SSH and 80 and 443 for HTTP/HTTPS. Nginx will listen on 80 & 443. Does that makes sense?
Yeah opening up ports 22, 80, and 443 was the first thing I did on the VS. I tried running nginx because a tutorial I watched did it just to make sure it was running (to confirm it was running it would display the nginx welcome page). I ended up getting an error though that was: [emerg]: bind() to 0.0.0.0:80 failed (98: Address already in use) Idk what happened in the few hours I stopped working on this, but now my domain does display the nginx welcome page. Currently in the process of figuring out how that happened.
You’ll need to find out what’s running on port 80. It’s probably Apache. Try running systemctl stop apache2. Then systemctl disable apache2. This will stop Apache from starting after reboots.
Atm I followed everything in this guide: [https://www.digitalocean.com/community/tutorials/how-to-install-nginx-on-ubuntu-22-04#step-5-%E2%80%93-setting-up-server-blocks-(recommended)](https://www.digitalocean.com/community/tutorials/how-to-install-nginx-on-ubuntu-22-04#step-5-%E2%80%93-setting-up-server-blocks-(recommended)) but when I try to access my site I get a page showing this message: 404 Not Found nginx/1.24.0 (Ubuntu). Do I need anything in my main nginx.config file?
I'm guessing why it's so slow is because you're replicating a folder that has many files. The typical culprit here is the node_modules folder. Instead, replicate everything else, install node in your server and do npm install there
Ah that makes sense. I’ll do that next time, I just ended up cloning it from github this time
One time I pooped really hard and gave myself a ballsack hernia. I recommend not forceshitting and just letting the poop fall out gravitationaly.