node js app issues after AWS Instance snapshot Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Come Celebrate our 10 Year Anniversary!Node app crashes after a while on micro EC2 instance even with supervisoramazon aws instance blocks outbound http requestsAws snapshot managementSetting up Node App along with nginx serverAWS Elastic Beanstalk - Node not found after creating NodeJS instanceAWS Elastick Beanstalk + Node JS + HTTPS = Connection RefusedEC2 AWS Instance not building bcrypt dependencynginx + node app + vuejs appHow to get node app running on Amazon EC2 instance to start on reboot?issues configuring nginx with node.js app

Why are vacuum tubes still used in amateur radios?

What does 丫 mean? 丫是什么意思?

Random body shuffle every night—can we still function?

Tips to organize LaTeX presentations for a semester

Why weren't discrete x86 CPUs ever used in game hardware?

Caught masturbating at work

White walkers, cemeteries and wights

Did pre-Columbian Americans know the spherical shape of the Earth?

A proverb that is used to imply that you have unexpectedly faced a big problem

AppleTVs create a chatty alternate WiFi network

Co-worker has annoying ringtone

Why not send Voyager 3 and 4 following up the paths taken by Voyager 1 and 2 to re-transmit signals of later as they fly away from Earth?

How to align enumerate environment inside description environment

I can't produce songs

Relating to the President and obstruction, were Mueller's conclusions preordained?

How do living politicians protect their readily obtainable signatures from misuse?

Was Kant an Intuitionist about mathematical objects?

What does it mean that physics no longer uses mechanical models to describe phenomena?

what is the log of the PDF for a Normal Distribution?

Weaponising the Grasp-at-a-Distance spell

How to ask rejected full-time candidates to apply to teach individual courses?

Why is a lens darker than other ones when applying the same settings?

How can a team of shapeshifters communicate?

What is the origin of 落第?



node js app issues after AWS Instance snapshot



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
Come Celebrate our 10 Year Anniversary!Node app crashes after a while on micro EC2 instance even with supervisoramazon aws instance blocks outbound http requestsAws snapshot managementSetting up Node App along with nginx serverAWS Elastic Beanstalk - Node not found after creating NodeJS instanceAWS Elastick Beanstalk + Node JS + HTTPS = Connection RefusedEC2 AWS Instance not building bcrypt dependencynginx + node app + vuejs appHow to get node app running on Amazon EC2 instance to start on reboot?issues configuring nginx with node.js app



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








3















I had a node.js app with nginx running totally fine on a domain i purchased. It was run on an ubuntu server and all was well. I accidentally clicked "create image" on the aws site and ever since then the site doesn't work. The local ip address through port 3000 is working as expected, but the domain is not. It is loading the first html file but cannot GET the stylesheets or javascripts that go with it and none of the css or javascript files are being loaded, rather they are all returning 404. I uninstalled/reinstalled nginx and such but have not had any luck. any ideas? I don't want to change any code or such if possible, as it was working TOTALLY as expected/desired before this. I would like to express again that literally nothing other than clicking one button on aws has caused this issue



here is a config file for nginx



#
server
listen 80;
listen [::]:80;
server_name example.org www.example.org;
return 301 https://$server_name$request_uri;


server
listen 443 ssl http2 default_server;
listen [::]:443 ssl http2 default_server;
server_name example.org www.example.org;

location /
proxy_pass http://localhost:3000/login.html;

ssl_certificate /etc/letsencrypt/live/example.org/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/example.org/privkey.pem; # managed by Certbot
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_prefer_server_ciphers on;
ssl_ciphers EECDH+CHACHA20:EECDH+AES128:RSA+AES128:EECDH+AES256:RSA+AES256:EECDH+3DES:RSA+3DES:!MD5;

ssl_session_cache shared:SSL:5m;
ssl_session_timeout 1h;
add_header Strict-Transport-Security “max-age=15768000” always;



#


also, here is what was working for my app.js
this may be a good time to ask if i'm doing everything ok, im sure it can be improved as I am still just learning



var createError = require('http-errors');
var express = require('express');
var path = require('path');
var cookieParser = require('cookie-parser');
var bodyParser = require('body-parser')
var logger = require('morgan');
var User = require("./models/user");
var db = require('./db.js');

var indexRouter = require('./routes/index');
var usersRouter = require('./routes/users');
var devicesRouter = require('./routes/devices')

var app = express();

// view engine setup
app.set('views', path.join(__dirname, 'views'));
app.set('view engine', 'pug');

app.use(logger('dev'));
app.use(express.json());
app.use(cookieParser());
app.use(bodyParser.urlencoded( extended: false ));
app.use(bodyParser.json());
app.use(express.static(path.join(__dirname, 'public')));

app.use('/', indexRouter);
app.use('/users', usersRouter);
app.use('/devices', devicesRouter);

// catch 404 and forward to error handler
app.use(function(req, res, next)
next(createError(404));
);

// error handler
app.use(function(err, req, res, next) );

module.exports = app;


Here is what the server responds when I use it (the first one is me on local host port 3000 and the second one is where it gets all funky, it looks like its trying to access /login.htmlstylesheets/login.css instead of /stylesheets/login/css










share|improve this question









New contributor




helpimlost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.















  • 1





    Tell us about the other changes you made. Show us the nginx configuration and the error log entries.

    – Michael Hampton
    Apr 15 at 6:22












  • Michael, i have attempted to clear up any issues you may have had. what bothers me is that i literally did not change anything other than clicking one button accidentally on a web interface

    – helpimlost
    Apr 15 at 15:05











  • The "create snapshot" reboots your server, so if you'd set up a Node process to run manually instead of having it fire up as a service, that'd probably cause issues.

    – ceejayoz
    Apr 15 at 15:12

















3















I had a node.js app with nginx running totally fine on a domain i purchased. It was run on an ubuntu server and all was well. I accidentally clicked "create image" on the aws site and ever since then the site doesn't work. The local ip address through port 3000 is working as expected, but the domain is not. It is loading the first html file but cannot GET the stylesheets or javascripts that go with it and none of the css or javascript files are being loaded, rather they are all returning 404. I uninstalled/reinstalled nginx and such but have not had any luck. any ideas? I don't want to change any code or such if possible, as it was working TOTALLY as expected/desired before this. I would like to express again that literally nothing other than clicking one button on aws has caused this issue



here is a config file for nginx



#
server
listen 80;
listen [::]:80;
server_name example.org www.example.org;
return 301 https://$server_name$request_uri;


server
listen 443 ssl http2 default_server;
listen [::]:443 ssl http2 default_server;
server_name example.org www.example.org;

location /
proxy_pass http://localhost:3000/login.html;

ssl_certificate /etc/letsencrypt/live/example.org/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/example.org/privkey.pem; # managed by Certbot
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_prefer_server_ciphers on;
ssl_ciphers EECDH+CHACHA20:EECDH+AES128:RSA+AES128:EECDH+AES256:RSA+AES256:EECDH+3DES:RSA+3DES:!MD5;

ssl_session_cache shared:SSL:5m;
ssl_session_timeout 1h;
add_header Strict-Transport-Security “max-age=15768000” always;



#


also, here is what was working for my app.js
this may be a good time to ask if i'm doing everything ok, im sure it can be improved as I am still just learning



var createError = require('http-errors');
var express = require('express');
var path = require('path');
var cookieParser = require('cookie-parser');
var bodyParser = require('body-parser')
var logger = require('morgan');
var User = require("./models/user");
var db = require('./db.js');

var indexRouter = require('./routes/index');
var usersRouter = require('./routes/users');
var devicesRouter = require('./routes/devices')

var app = express();

// view engine setup
app.set('views', path.join(__dirname, 'views'));
app.set('view engine', 'pug');

app.use(logger('dev'));
app.use(express.json());
app.use(cookieParser());
app.use(bodyParser.urlencoded( extended: false ));
app.use(bodyParser.json());
app.use(express.static(path.join(__dirname, 'public')));

app.use('/', indexRouter);
app.use('/users', usersRouter);
app.use('/devices', devicesRouter);

// catch 404 and forward to error handler
app.use(function(req, res, next)
next(createError(404));
);

// error handler
app.use(function(err, req, res, next) );

module.exports = app;


Here is what the server responds when I use it (the first one is me on local host port 3000 and the second one is where it gets all funky, it looks like its trying to access /login.htmlstylesheets/login.css instead of /stylesheets/login/css










share|improve this question









New contributor




helpimlost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.















  • 1





    Tell us about the other changes you made. Show us the nginx configuration and the error log entries.

    – Michael Hampton
    Apr 15 at 6:22












  • Michael, i have attempted to clear up any issues you may have had. what bothers me is that i literally did not change anything other than clicking one button accidentally on a web interface

    – helpimlost
    Apr 15 at 15:05











  • The "create snapshot" reboots your server, so if you'd set up a Node process to run manually instead of having it fire up as a service, that'd probably cause issues.

    – ceejayoz
    Apr 15 at 15:12













3












3








3








I had a node.js app with nginx running totally fine on a domain i purchased. It was run on an ubuntu server and all was well. I accidentally clicked "create image" on the aws site and ever since then the site doesn't work. The local ip address through port 3000 is working as expected, but the domain is not. It is loading the first html file but cannot GET the stylesheets or javascripts that go with it and none of the css or javascript files are being loaded, rather they are all returning 404. I uninstalled/reinstalled nginx and such but have not had any luck. any ideas? I don't want to change any code or such if possible, as it was working TOTALLY as expected/desired before this. I would like to express again that literally nothing other than clicking one button on aws has caused this issue



here is a config file for nginx



#
server
listen 80;
listen [::]:80;
server_name example.org www.example.org;
return 301 https://$server_name$request_uri;


server
listen 443 ssl http2 default_server;
listen [::]:443 ssl http2 default_server;
server_name example.org www.example.org;

location /
proxy_pass http://localhost:3000/login.html;

ssl_certificate /etc/letsencrypt/live/example.org/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/example.org/privkey.pem; # managed by Certbot
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_prefer_server_ciphers on;
ssl_ciphers EECDH+CHACHA20:EECDH+AES128:RSA+AES128:EECDH+AES256:RSA+AES256:EECDH+3DES:RSA+3DES:!MD5;

ssl_session_cache shared:SSL:5m;
ssl_session_timeout 1h;
add_header Strict-Transport-Security “max-age=15768000” always;



#


also, here is what was working for my app.js
this may be a good time to ask if i'm doing everything ok, im sure it can be improved as I am still just learning



var createError = require('http-errors');
var express = require('express');
var path = require('path');
var cookieParser = require('cookie-parser');
var bodyParser = require('body-parser')
var logger = require('morgan');
var User = require("./models/user");
var db = require('./db.js');

var indexRouter = require('./routes/index');
var usersRouter = require('./routes/users');
var devicesRouter = require('./routes/devices')

var app = express();

// view engine setup
app.set('views', path.join(__dirname, 'views'));
app.set('view engine', 'pug');

app.use(logger('dev'));
app.use(express.json());
app.use(cookieParser());
app.use(bodyParser.urlencoded( extended: false ));
app.use(bodyParser.json());
app.use(express.static(path.join(__dirname, 'public')));

app.use('/', indexRouter);
app.use('/users', usersRouter);
app.use('/devices', devicesRouter);

// catch 404 and forward to error handler
app.use(function(req, res, next)
next(createError(404));
);

// error handler
app.use(function(err, req, res, next) );

module.exports = app;


Here is what the server responds when I use it (the first one is me on local host port 3000 and the second one is where it gets all funky, it looks like its trying to access /login.htmlstylesheets/login.css instead of /stylesheets/login/css










share|improve this question









New contributor




helpimlost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












I had a node.js app with nginx running totally fine on a domain i purchased. It was run on an ubuntu server and all was well. I accidentally clicked "create image" on the aws site and ever since then the site doesn't work. The local ip address through port 3000 is working as expected, but the domain is not. It is loading the first html file but cannot GET the stylesheets or javascripts that go with it and none of the css or javascript files are being loaded, rather they are all returning 404. I uninstalled/reinstalled nginx and such but have not had any luck. any ideas? I don't want to change any code or such if possible, as it was working TOTALLY as expected/desired before this. I would like to express again that literally nothing other than clicking one button on aws has caused this issue



here is a config file for nginx



#
server
listen 80;
listen [::]:80;
server_name example.org www.example.org;
return 301 https://$server_name$request_uri;


server
listen 443 ssl http2 default_server;
listen [::]:443 ssl http2 default_server;
server_name example.org www.example.org;

location /
proxy_pass http://localhost:3000/login.html;

ssl_certificate /etc/letsencrypt/live/example.org/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/example.org/privkey.pem; # managed by Certbot
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_prefer_server_ciphers on;
ssl_ciphers EECDH+CHACHA20:EECDH+AES128:RSA+AES128:EECDH+AES256:RSA+AES256:EECDH+3DES:RSA+3DES:!MD5;

ssl_session_cache shared:SSL:5m;
ssl_session_timeout 1h;
add_header Strict-Transport-Security “max-age=15768000” always;



#


also, here is what was working for my app.js
this may be a good time to ask if i'm doing everything ok, im sure it can be improved as I am still just learning



var createError = require('http-errors');
var express = require('express');
var path = require('path');
var cookieParser = require('cookie-parser');
var bodyParser = require('body-parser')
var logger = require('morgan');
var User = require("./models/user");
var db = require('./db.js');

var indexRouter = require('./routes/index');
var usersRouter = require('./routes/users');
var devicesRouter = require('./routes/devices')

var app = express();

// view engine setup
app.set('views', path.join(__dirname, 'views'));
app.set('view engine', 'pug');

app.use(logger('dev'));
app.use(express.json());
app.use(cookieParser());
app.use(bodyParser.urlencoded( extended: false ));
app.use(bodyParser.json());
app.use(express.static(path.join(__dirname, 'public')));

app.use('/', indexRouter);
app.use('/users', usersRouter);
app.use('/devices', devicesRouter);

// catch 404 and forward to error handler
app.use(function(req, res, next)
next(createError(404));
);

// error handler
app.use(function(err, req, res, next) );

module.exports = app;


Here is what the server responds when I use it (the first one is me on local host port 3000 and the second one is where it gets all funky, it looks like its trying to access /login.htmlstylesheets/login.css instead of /stylesheets/login/css







ubuntu nginx amazon-web-services node.js web-applications






share|improve this question









New contributor




helpimlost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




helpimlost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited Apr 15 at 15:04







helpimlost













New contributor




helpimlost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked Apr 15 at 5:17









helpimlosthelpimlost

162




162




New contributor




helpimlost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





helpimlost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






helpimlost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.







  • 1





    Tell us about the other changes you made. Show us the nginx configuration and the error log entries.

    – Michael Hampton
    Apr 15 at 6:22












  • Michael, i have attempted to clear up any issues you may have had. what bothers me is that i literally did not change anything other than clicking one button accidentally on a web interface

    – helpimlost
    Apr 15 at 15:05











  • The "create snapshot" reboots your server, so if you'd set up a Node process to run manually instead of having it fire up as a service, that'd probably cause issues.

    – ceejayoz
    Apr 15 at 15:12












  • 1





    Tell us about the other changes you made. Show us the nginx configuration and the error log entries.

    – Michael Hampton
    Apr 15 at 6:22












  • Michael, i have attempted to clear up any issues you may have had. what bothers me is that i literally did not change anything other than clicking one button accidentally on a web interface

    – helpimlost
    Apr 15 at 15:05











  • The "create snapshot" reboots your server, so if you'd set up a Node process to run manually instead of having it fire up as a service, that'd probably cause issues.

    – ceejayoz
    Apr 15 at 15:12







1




1





Tell us about the other changes you made. Show us the nginx configuration and the error log entries.

– Michael Hampton
Apr 15 at 6:22






Tell us about the other changes you made. Show us the nginx configuration and the error log entries.

– Michael Hampton
Apr 15 at 6:22














Michael, i have attempted to clear up any issues you may have had. what bothers me is that i literally did not change anything other than clicking one button accidentally on a web interface

– helpimlost
Apr 15 at 15:05





Michael, i have attempted to clear up any issues you may have had. what bothers me is that i literally did not change anything other than clicking one button accidentally on a web interface

– helpimlost
Apr 15 at 15:05













The "create snapshot" reboots your server, so if you'd set up a Node process to run manually instead of having it fire up as a service, that'd probably cause issues.

– ceejayoz
Apr 15 at 15:12





The "create snapshot" reboots your server, so if you'd set up a Node process to run manually instead of having it fire up as a service, that'd probably cause issues.

– ceejayoz
Apr 15 at 15:12










1 Answer
1






active

oldest

votes


















2














Well, the problem is pretty obvious here:



location / 
proxy_pass http://localhost:3000/login.html;



So every time nginx passes a request up to your Node app, /login.html is prepended to the URI path.



My guess is you or someone else made this change days, weeks, or even months ago but never reloaded nginx with it, and it was finally loaded when your server was restarted.



You should instead be passing to http://127.0.0.1:3000, with no trailing path.



location / 
proxy_pass http://localhost:3000;



You also should set the document root to the directory containing the root of your static files, and use a try_files to ensure that nginx serves the static files instead of Node. A better configuration would look like:



server 
....
root /srv/www/myapp/public;
location /
try_files $uri @node;


location @node
proxy_pass http://127.0.0.1:3000;







share|improve this answer

























  • this fixed it. I appreciate the help greatly Michael, it saved me lots of hours of frustration.

    – helpimlost
    Apr 15 at 16:57











  • @helpimlost If it solved your problem, you can mark it as solved by clicking the outline of the tick mark so that it turns solid green. Welcome to Server Fault!

    – Michael Hampton
    Apr 16 at 1:32











Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);






helpimlost is a new contributor. Be nice, and check out our Code of Conduct.









draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f963059%2fnode-js-app-issues-after-aws-instance-snapshot%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









2














Well, the problem is pretty obvious here:



location / 
proxy_pass http://localhost:3000/login.html;



So every time nginx passes a request up to your Node app, /login.html is prepended to the URI path.



My guess is you or someone else made this change days, weeks, or even months ago but never reloaded nginx with it, and it was finally loaded when your server was restarted.



You should instead be passing to http://127.0.0.1:3000, with no trailing path.



location / 
proxy_pass http://localhost:3000;



You also should set the document root to the directory containing the root of your static files, and use a try_files to ensure that nginx serves the static files instead of Node. A better configuration would look like:



server 
....
root /srv/www/myapp/public;
location /
try_files $uri @node;


location @node
proxy_pass http://127.0.0.1:3000;







share|improve this answer

























  • this fixed it. I appreciate the help greatly Michael, it saved me lots of hours of frustration.

    – helpimlost
    Apr 15 at 16:57











  • @helpimlost If it solved your problem, you can mark it as solved by clicking the outline of the tick mark so that it turns solid green. Welcome to Server Fault!

    – Michael Hampton
    Apr 16 at 1:32















2














Well, the problem is pretty obvious here:



location / 
proxy_pass http://localhost:3000/login.html;



So every time nginx passes a request up to your Node app, /login.html is prepended to the URI path.



My guess is you or someone else made this change days, weeks, or even months ago but never reloaded nginx with it, and it was finally loaded when your server was restarted.



You should instead be passing to http://127.0.0.1:3000, with no trailing path.



location / 
proxy_pass http://localhost:3000;



You also should set the document root to the directory containing the root of your static files, and use a try_files to ensure that nginx serves the static files instead of Node. A better configuration would look like:



server 
....
root /srv/www/myapp/public;
location /
try_files $uri @node;


location @node
proxy_pass http://127.0.0.1:3000;







share|improve this answer

























  • this fixed it. I appreciate the help greatly Michael, it saved me lots of hours of frustration.

    – helpimlost
    Apr 15 at 16:57











  • @helpimlost If it solved your problem, you can mark it as solved by clicking the outline of the tick mark so that it turns solid green. Welcome to Server Fault!

    – Michael Hampton
    Apr 16 at 1:32













2












2








2







Well, the problem is pretty obvious here:



location / 
proxy_pass http://localhost:3000/login.html;



So every time nginx passes a request up to your Node app, /login.html is prepended to the URI path.



My guess is you or someone else made this change days, weeks, or even months ago but never reloaded nginx with it, and it was finally loaded when your server was restarted.



You should instead be passing to http://127.0.0.1:3000, with no trailing path.



location / 
proxy_pass http://localhost:3000;



You also should set the document root to the directory containing the root of your static files, and use a try_files to ensure that nginx serves the static files instead of Node. A better configuration would look like:



server 
....
root /srv/www/myapp/public;
location /
try_files $uri @node;


location @node
proxy_pass http://127.0.0.1:3000;







share|improve this answer















Well, the problem is pretty obvious here:



location / 
proxy_pass http://localhost:3000/login.html;



So every time nginx passes a request up to your Node app, /login.html is prepended to the URI path.



My guess is you or someone else made this change days, weeks, or even months ago but never reloaded nginx with it, and it was finally loaded when your server was restarted.



You should instead be passing to http://127.0.0.1:3000, with no trailing path.



location / 
proxy_pass http://localhost:3000;



You also should set the document root to the directory containing the root of your static files, and use a try_files to ensure that nginx serves the static files instead of Node. A better configuration would look like:



server 
....
root /srv/www/myapp/public;
location /
try_files $uri @node;


location @node
proxy_pass http://127.0.0.1:3000;








share|improve this answer














share|improve this answer



share|improve this answer








edited Apr 15 at 15:46

























answered Apr 15 at 15:16









Michael HamptonMichael Hampton

175k27321651




175k27321651












  • this fixed it. I appreciate the help greatly Michael, it saved me lots of hours of frustration.

    – helpimlost
    Apr 15 at 16:57











  • @helpimlost If it solved your problem, you can mark it as solved by clicking the outline of the tick mark so that it turns solid green. Welcome to Server Fault!

    – Michael Hampton
    Apr 16 at 1:32

















  • this fixed it. I appreciate the help greatly Michael, it saved me lots of hours of frustration.

    – helpimlost
    Apr 15 at 16:57











  • @helpimlost If it solved your problem, you can mark it as solved by clicking the outline of the tick mark so that it turns solid green. Welcome to Server Fault!

    – Michael Hampton
    Apr 16 at 1:32
















this fixed it. I appreciate the help greatly Michael, it saved me lots of hours of frustration.

– helpimlost
Apr 15 at 16:57





this fixed it. I appreciate the help greatly Michael, it saved me lots of hours of frustration.

– helpimlost
Apr 15 at 16:57













@helpimlost If it solved your problem, you can mark it as solved by clicking the outline of the tick mark so that it turns solid green. Welcome to Server Fault!

– Michael Hampton
Apr 16 at 1:32





@helpimlost If it solved your problem, you can mark it as solved by clicking the outline of the tick mark so that it turns solid green. Welcome to Server Fault!

– Michael Hampton
Apr 16 at 1:32










helpimlost is a new contributor. Be nice, and check out our Code of Conduct.









draft saved

draft discarded


















helpimlost is a new contributor. Be nice, and check out our Code of Conduct.












helpimlost is a new contributor. Be nice, and check out our Code of Conduct.











helpimlost is a new contributor. Be nice, and check out our Code of Conduct.














Thanks for contributing an answer to Server Fault!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f963059%2fnode-js-app-issues-after-aws-instance-snapshot%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Wikipedia:Vital articles Мазмуну Biography - Өмүр баян Philosophy and psychology - Философия жана психология Religion - Дин Social sciences - Коомдук илимдер Language and literature - Тил жана адабият Science - Илим Technology - Технология Arts and recreation - Искусство жана эс алуу History and geography - Тарых жана география Навигация менюсу

Club Baloncesto Breogán Índice Historia | Pavillón | Nome | O Breogán na cultura popular | Xogadores | Adestradores | Presidentes | Palmarés | Historial | Líderes | Notas | Véxase tamén | Menú de navegacióncbbreogan.galCadroGuía oficial da ACB 2009-10, páxina 201Guía oficial ACB 1992, páxina 183. Editorial DB.É de 6.500 espectadores sentados axeitándose á última normativa"Estudiantes Junior, entre as mellores canteiras"o orixinalHemeroteca El Mundo Deportivo, 16 setembro de 1970, páxina 12Historia do BreogánAlfredo Pérez, o último canoneiroHistoria C.B. BreogánHemeroteca de El Mundo DeportivoJimmy Wright, norteamericano do Breogán deixará Lugo por ameazas de morteResultados de Breogán en 1986-87Resultados de Breogán en 1990-91Ficha de Velimir Perasović en acb.comResultados de Breogán en 1994-95Breogán arrasa al Barça. "El Mundo Deportivo", 27 de setembro de 1999, páxina 58CB Breogán - FC BarcelonaA FEB invita a participar nunha nova Liga EuropeaCharlie Bell na prensa estatalMáximos anotadores 2005Tempada 2005-06 : Tódolos Xogadores da Xornada""Non quero pensar nunha man negra, mais pregúntome que está a pasar""o orixinalRaúl López, orgulloso dos xogadores, presume da boa saúde económica do BreogánJulio González confirma que cesa como presidente del BreogánHomenaxe a Lisardo GómezA tempada do rexurdimento celesteEntrevista a Lisardo GómezEl COB dinamita el Pazo para forzar el quinto (69-73)Cafés Candelas, patrocinador del CB Breogán"Suso Lázare, novo presidente do Breogán"o orixinalCafés Candelas Breogán firma el mayor triunfo de la historiaEl Breogán realizará 17 homenajes por su cincuenta aniversario"O Breogán honra ao seu fundador e primeiro presidente"o orixinalMiguel Giao recibiu a homenaxe do PazoHomenaxe aos primeiros gladiadores celestesO home que nos amosa como ver o Breo co corazónTita Franco será homenaxeada polos #50anosdeBreoJulio Vila recibirá unha homenaxe in memoriam polos #50anosdeBreo"O Breogán homenaxeará aos seus aboados máis veteráns"Pechada ovación a «Capi» Sanmartín e Ricardo «Corazón de González»Homenaxe por décadas de informaciónPaco García volve ao Pazo con motivo do 50 aniversario"Resultados y clasificaciones""O Cafés Candelas Breogán, campión da Copa Princesa""O Cafés Candelas Breogán, equipo ACB"C.B. Breogán"Proxecto social"o orixinal"Centros asociados"o orixinalFicha en imdb.comMario Camus trata la recuperación del amor en 'La vieja música', su última película"Páxina web oficial""Club Baloncesto Breogán""C. B. Breogán S.A.D."eehttp://www.fegaba.com

What should I write in an apology letter, since I have decided not to join a company after accepting an offer letterShould I keep looking after accepting a job offer?What should I do when I've been verbally told I would get an offer letter, but still haven't gotten one after 4 weeks?Do I accept an offer from a company that I am not likely to join?New job hasn't confirmed starting date and I want to give current employer as much notice as possibleHow should I address my manager in my resignation letter?HR delayed background verification, now jobless as resignedNo email communication after accepting a formal written offer. How should I phrase the call?What should I do if after receiving a verbal offer letter I am informed that my written job offer is put on hold due to some internal issues?Should I inform the current employer that I am about to resign within 1-2 weeks since I have signed the offer letter and waiting for visa?What company will do, if I send their offer letter to another company