Nginx 502 when running Rails (Puma) with -d (daemon)

Question

Ruby 2.5.1, Rails 5.2.2.1

I'm trying to make nginx get upstream through puma socket.

When I run rails s -e production all is good.

When I run rails s -e production -d Nginx returns 502 Bad Gateway

config/puma.rb

...
      app_dir = "/home/user/myapp"
      tmp_dir = "#{app_dir}/tmp"
      # Set up socket location
      bind "unix://#{tmp_dir}/sockets/puma.sock"
      # Logging
      stdout_redirect "#{app_dir}/log/puma.stdout.log", "#{app_dir}/log/puma.stderr.log", true
...

etc/nginx/sites-enabled/mydomain.com

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

server {
    listen 80;
    server_name mydomain.com;

    root /home/user/myapp/public;

    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;
}

var/log/nginx/error.log

    2019/07/07 13:45:09 [error] 21609#21609: *11391 connect() to 
unix:/home/user/myapp/tmp/sockets/puma.sock failed (111: Connection 
refused) while connecting to upstream, client: 172.68.11.91, server: 
mydomain.com, request: "GET /pages/one HTTP/1.1", upstream: 
"http://unix:/home/user/myapp/tmp/sockets/puma.sock:/pages/one", host: "mydomain.com"

(P.S. change from original domain to mydomain.com) What difference? How to fix it? Please explain and help

UPDATE

Seems to be running with daemon flag it doesn't create puma.sock in /home/user/myapp/tmp/sockets. Why and where is it?

Николай Агеев Николай Агеев · Accepted Answer · 2019-07-07T11:24:09

Solution

Dont know why, but It works if run puma (not rails server)

RAILS_ENV=production bundle exec puma -C config/puma.rb -d

Nginx 502 when running Rails (Puma) with -d (daemon)

1 Answers