Followed this tutorial to run a nodejs app on a droplet
running pm2 and can see from the logs that the app.js is running
used curl for localhost:3000 and got the response hello world so pm2 is properly running a node server pointed at that localhost port.
Where I’m confused is basically the configuration. I’m assuming nginx is my server software similar to apache. pm2 is letting node run a local server in the background and nginx is then serving as a proxy that directs external traffic through the firewall to my local files (it would be cool if someone could drop a good primer on how this actually works.) And nginx I assume is somehow not getting the right variables from me about both where my files are stored (default locations) and also what url strings to redirect ( waveballoon.com vs waveballoon.com/index )
my nginx default file looks like this. I have not touched the other nginx.conf file
my node app is in /srv/www/hello/app.js
root /var/www/html;
# Add index.php to the list if you are using PHP
index index.html index.htm index.nginx-debian.html;
server_name waveballoon.com; # managed by Certbot
location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 4>
try_files $uri $uri/ =404;
}
# pass PHP scripts to FastCGI server
#
#location ~ \.php$ {
# include snippets/fastcgi-php.conf;
#
# # With php-fpm (or other unix sockets):
# fastcgi_pass unix:/var/run/php/php7.4-fpm.sock;
# # With php-cgi (or other tcp sockets):
# fastcgi_pass 127.0.0.1:9000;
#}
# deny access to .htaccess files, if Apache's document r>
# concurs with nginx's one
#
#location ~ /\.ht {
# deny all;
#}
listen [::]:443 ssl; # managed by Certbot
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/www.waveballoon.com/fu>
ssl_certificate_key /etc/letsencrypt/live/www.waveballoon.co>
include /etc/letsencrypt/options-ssl-nginx.conf; # managed b>
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by >
}
server {
# SSL configuration
#
# listen 443 ssl default_server;
# listen [::]:443 ssl default_server;
#
# Note: You should disable gzip for SSL traffic.
# See: https://bugs.debian.org/773332
#
# Read up on ssl_ciphers to ensure a secure configuratio>
# See: https://bugs.debian.org/765782
#
# Self signed certs generated by the ssl-cert package
# Don't use them in a production server!
#
# include snippets/snakeoil.conf;
root /var/www/html;
# Add index.php to the list if you are using PHP
index index.html index.htm index.nginx-debian.html;
server_name www.waveballoon.com; # managed by Certbot
location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 4>
try_files $uri $uri/ =404;
}
# pass PHP scripts to FastCGI server
#
#location ~ \.php$ {
# include snippets/fastcgi-php.conf;
#
# # With php-fpm (or other unix sockets):
# fastcgi_pass unix:/var/run/php/php7.4-fpm.sock;
# # With php-cgi (or other tcp sockets):
# fastcgi_pass 127.0.0.1:9000;
#}
# deny access to .htaccess files, if Apache's document r>
# concurs with nginx's one
#
#location ~ /\.ht {
# deny all;
#}
listen [::]:443 ssl ipv6only=on; # managed by Certbot
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/www.waveballoon.com/fu>
ssl_certificate_key /etc/letsencrypt/live/www.waveballoon.co>
include /etc/letsencrypt/options-ssl-nginx.conf; # managed b>
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by >
}
server {
if ($host = www.waveballoon.com) {
return 301 https://$host$request_uri;
} # managed by Certbot
listen 80 ;
listen [::]:80 ;
server_name www.waveballoon.com;
return 404; # managed by Certbot
}
server {
# SSL configuration
#
# listen 443 ssl default_server;
# listen [::]:443 ssl default_server;
#
# Note: You should disable gzip for SSL traffic.
# See: https://bugs.debian.org/773332
#
# Read up on ssl_ciphers to ensure a secure configuratio>
# See: https://bugs.debian.org/765782
#
# Self signed certs generated by the ssl-cert package
# Don't use them in a production server!
#
# include snippets/snakeoil.conf;
root /var/www/html;
# Add index.php to the list if you are using PHP
index index.html index.htm index.nginx-debian.html;
server_name waveballoon.com; # managed by Certbot
location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 4>
try_files $uri $uri/ =404;
}
# pass PHP scripts to FastCGI server
#
#location ~ \.php$ {
# include snippets/fastcgi-php.conf;
#
# # With php-fpm (or other unix sockets):
# fastcgi_pass unix:/var/run/php/php7.4-fpm.sock;
# # With php-cgi (or other tcp sockets):
# fastcgi_pass 127.0.0.1:9000;
#}
# deny access to .htaccess files, if Apache's document r>
# concurs with nginx's one
#
#location ~ /\.ht {
# deny all;
#}
listen [::]:443 ssl; # managed by Certbot
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/www.waveballoon.com/fu>
ssl_certificate_key /etc/letsencrypt/live/www.waveballoon.co>
include /etc/letsencrypt/options-ssl-nginx.conf; # managed b>
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by >
}
server {
if ($host = waveballoon.com) {
return 301 https://$host$request_uri;
} # managed by Certbot
listen 80 ;
listen [::]:80 ;
server_name waveballoon.com;
return 404; # managed by Certbot
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hello,
I can see that you’ve managed to fix the issue and now your site is returning the correct content.
In case that anyone comes across this in the future, what I could suggest is following the instructions from step 5 from this tutorial here on how to configure Nginx:
Best,
Bobby
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.