Related

502 Bad Gateway on one-click Ruby Rails app Question Question
Filezilla uploaded files to rails via sftp won't show up Question Question

Question

Run rails app on IP instead of port.

Posted March 3, 2017 3k views
Ruby on RailsUbuntu 16.04

Hello, I deployed my rails app on my droplet using this tutorial: https://www.digitalocean.com/community/tutorials/how-to-deploy-a-rails-app-with-git-hooks-on-ubuntu-14-04 -> with git hooks, puma and nginx.

But when my app is running I can only access it using http://my_ip_address:3000, when 3000 is app’s localhost port.

How to configure app in order to get it under http://my_ip_address?

Thank you in advance for your help.

Add a comment
todoardo
By:
todoardo
Add a comment

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.

×
2 answers
Woet March 3, 2017

Read the “Install and Configure Nginx” part of the tutorial you linked.

Reply Report
  • todoardo March 3, 2017

    Already read and done. Her is my nginx config:

    upstream myapp {
    # Path to Puma SOCK file, as defined previously
    server unix:/home/me/myapp/shared/sockets/puma.sock fail_timeout=0;
    }

    server {
    listen 80;
    server_name http://46.101.198.190/;

    root /home/me/todoardo/myapp;

try_files $uri/index.html $uri @app;

location @app {
    proxy_pass http://app;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Host $http_host;
    proxy_redirect off;
}

error_page 500 502 503 504 /500.html;
client_max_body_size 4G;
keepalive_timeout 10;

    }

    Reply Report
jtittle1 March 3, 2017

@todoardo

You’ll need to change server_name in your server block as what you have now will most likely cause NGINX to fail when attempting to start/restart/reload.

This:

server_name http://46.101.198.190/;

Should be (as per the tutorial):

server_name localhost;

Other such valid configuration would be:

server_name domain.com www.domain.com;

or

server_name domain.com *.domain.com;

or

server_name hostname.domain.com www.hostname.domain.com;

ect.

…

After changes have been made and saved, you’ll need to reload NGINX using:

systemctl reload nginx

or

service nginx reload
Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help