After a few hours of mupx (meteor up) debugging, I finally managed to get my website deployed on an Ubuntu 14.04 server-- success! according to mupx. But now when I navigate to my site (nodingbat.com) the site refuses to connect.
Any advice for how I can debug a situation like this? Looking for the files on the server but no luck… I ping the domain and the correct IP is showing. Anyone have any experience with mup? Any help would be appreciated!
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!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
By default Meteor may only be listening on localhost or you may have a firewall enabled on your droplet which is preventing it from listening on port 3000 which means that the droplet itself should be able to reach it but nobody outside the droplet will get a response on port 3000. Depending on your needs there are a couple ways around this:
1.) Set up a reverse proxy using Nginx
You can install nginx on your droplet using
apt-get update; apt-get install nginx
and configure it to listen on port 80 (http) and relay requests for your meteor service on port 3000. Something like this in your/etc/nginx/sites-enabled/default
file will do the trick:2.) You could reconfigure your meteor app to listen on your public IP or
0.0.0.0
(all interfaces)