nginx错误：（13：连接到上游时权限被拒绝）]]

Question

我正在使用ubuntu 14.04 LTS在Google计算引擎VM上使用puma，capistrano和nginx运行Rails应用程序。

我在外部IP上运行了nginx。当我访问它时，在日志中出现两个Nginx错误：

2016/02/03 11:58:07 [info] 19754#0: *73 client closed connection while waiting for request, client: ###.##.##.###, server: 0.0.0.0:443 2016/02/03 11:58:07 [crit] 19754#0: *74 connect() to unix:///home/my-user-name/apps/my-web-app/shared/tmp/sockets/my-web-app-puma.sock failed (13: Permission denied) while connecting to upstream, client: ###.##.##.###, server: , request: "GET / HTTP/1.1", upstream: "http://unix:///home/my-user-name/apps/my-web-app/shared/tmp/sockets/my-web-app-puma.sock:/", host: "###.###.###.###"

注意：最后一个###。###。###。###是运行该代码的谷歌计算VM的外部IP。我相信前两个IP是我的家庭IP。

我已经尝试过：setsebool httpd_can_network_connect on，如此处所示：(13: Permission denied) while connecting to upstream:[nginx]它返回：setsebool: SELinux is disabled.但问题仍然存在。

我也看过(13: Permission denied) while connecting to upstream:[nginx]，但uwsgi似乎很特殊

这是我的nginx.conf

upstream puma {
  server unix:///home/my-user-name/apps/my-web-app/shared/tmp/sockets/my-web-app-puma.sock;
}
server {
  listen 80 default_server deferred;
  listen 443 ssl;
  # server_name example.com;
  ssl_certificate /etc/ssl/my-web-app/my-web-app.com.chained.crt;
  ssl_certificate_key /etc/ssl/my-web-app/my-web-app.key;
  root /home/my-web-app/apps/my-web-app/current/public;
  access_log /home/my-user-name/apps/my-web-app/current/log/nginx.access.log;
  error_log /home/my-user-name/apps/my-web-app/current/log/nginx.error.log info;
  location ^~ /assets/ {
    gzip_static on;
    expires max;
    add_header Cache-Control public;
  }
  try_files $uri/index.html $uri @puma;
  location @puma {
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Host $http_host;
    proxy_redirect off;
    proxy_pass http://puma;
  }
  error_page 500 502 503 504 /500.html;
  client_max_body_size 10M;
  keepalive_timeout 10;
}
我用sudo service nginx restart运行nginx然后我用以下命令运行puma：RACK_ENV=production bundle exec puma -p 3000，它返回：

Puma starting in single mode... * Version 2.14.0 (ruby 2.1.7-p400), codename: Fuchsia Friday * Min threads: 0, max threads: 16 * Environment: production * Listening on tcp://0.0.0.0:3000 Use Ctrl-C to stop

编辑1

有人建议我在unix上而不是tcp 3000上运行puma，以便它与nginx相匹配

我已经尝试通过以下命令在UNIX上运行puma：

RACK_ENV=production bundle exec puma -d -b unix:///tmp/my-web-app.sock --pidfile /tmp/puma.pid

给了：

Puma starting in single mode... * Version 2.14.0 (ruby 2.1.7-p400), codename: Fuchsia Friday * Min threads: 0, max threads: 16 * Environment: production * Daemonizing...

它读取了上面的文本，但没有保留，尽管最后出现了“ ...”，命令提示符仍会立即再次出现。

此命令似乎不起作用，因此，如果有人可以建议如何在unix而不是tcp 3000上运行puma，那么我可以完成建议。（尽管我怀疑在配置与puma有关的东西之前可能会发生nginx配置问题）

编辑2

附加puma.rb

#!/usr/bin/env puma directory '/home/my-user-name/apps/my-web-app/current' rackup "/home/my-user-name/apps/my-web-app/current/config.ru" environment 'production' pidfile "/home/my-user-name/apps/my-web-app/shared/tmp/pids/puma.pid" state_path "/home/my-user-name/apps/my-web-app/shared/tmp/pids/puma.state" stdout_redirect '/home/my-user-name/apps/my-web-app/current/log/puma.error.log', '/home/my-user-name/apps/my-web-app/current/log/puma.access.log', true threads 2,8 bind 'unix:///home/my-user-name/apps/my-web-app/shared/tmp/sockets/my-web-app-puma.sock' workers 1 preload_app! on_restart do puts 'Refreshing Gemfile' ENV["BUNDLE_GEMFILE"] = "/home/my-user-name/apps/my-web-app/current/Gemfile" end on_worker_boot do ActiveSupport.on_load(:active_record) do ActiveRecord::Base.establish_connection end end

编辑3

我现在尝试直接在端口80上直接运行Rails服务器。我输入：rvmsudo rails server -p 80，它返回：

=> Booting Puma => Rails 4.2.4 application starting in development on http://localhost:80 => Run `rails server -h` for more startup options => Ctrl-C to shutdown server Puma 2.14.0 starting... * Min threads: 0, max threads: 16 * Environment: development * Listening on tcp://localhost:80 Exiting /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/binder.rb:233:in `initialize': Address already in use - bind(2) for "localhost" port 80 (Errno::EADDRINUSE) from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/binder.rb:233:in `new' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/binder.rb:233:in `add_tcp_listener' from (eval):2:in `add_tcp_listener' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/rack/handler/puma.rb:33:in `run' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/rack-1.6.4/lib/rack/server.rb:286:in `start' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/railties-4.2.4/lib/rails/commands/server.rb:80:in `start' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/railties-4.2.4/lib/rails/commands/commands_tasks.rb:80:in `block in server' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/railties-4.2.4/lib/rails/commands/commands_tasks.rb:75:in `tap' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/railties-4.2.4/lib/rails/commands/commands_tasks.rb:75:in `server' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/railties-4.2.4/lib/rails/commands/commands_tasks.rb:39:in `run_command!' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/railties-4.2.4/lib/rails/commands.rb:17:in `<top (required)>' from bin/rails:4:in `require' from bin/rails:4:in `<main>'

编辑4

如果我运行sudo service nginx stop，然后再次运行rvmsudo rails server -p 80，它将返回：

=> Booting Puma => Rails 4.2.4 application starting in development on http://localhost:80 => Run `rails server -h` for more startup options => Ctrl-C to shutdown server Puma 2.14.0 starting... * Min threads: 0, max threads: 16 * Environment: development * Listening on tcp://localhost:80

这意味着该方法是不正确的，因为当我访问外部IP时没有nginx时，它没有返回The server refused the connection.，而与原始IP相反：

We're sorry, but something went wrong.

If you are the application owner check the logs for more information.

如果有人知道如何防止原始错误，将不胜感激任何建议。

编辑5

原始问题仍然存在，但是谁能告诉我这是https问题还是ssl问题？

编辑6

我曾尝试直接在80上运行puma并在80上遇到权限错误。

我尝试：RACK_ENV=production bundle exec puma -p 80并获得：

Puma starting in single mode... * Version 2.14.0 (ruby 2.1.7-p400), codename: Fuchsia Friday * Min threads: 0, max threads: 16 * Environment: production * Listening on tcp://0.0.0.0:80 /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/binder.rb:233:in `initialize': Permission denied - bind(2) for "0.0.0.0" port 80 (Errno::EACCES) from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/binder.rb:233:in `new' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/binder.rb:233:in `add_tcp_listener' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/binder.rb:98:in `block in parse' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/binder.rb:84:in `each' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/binder.rb:84:in `parse' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/runner.rb:119:in `load_and_bind' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/single.rb:79:in `run' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/cli.rb:215:in `run' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/bin/puma:10:in `<top (required)>' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/bin/puma:23:in `load' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/bin/puma:23:in `<main>'

我相信这是因为端口80具有比其他端口更高的权限。因此，我运行了sudo RACK_ENV=production bundle exec puma -p 80，但返回了：Your Ruby version is 1.9.3, but your Gemfile specified 2.1.7

我正在使用ubuntu 14.04 LTS在Google计算引擎VM上使用puma，capistrano和nginx运行Rails应用程序。我在外部IP上运行了Nginx。当我访问它时，出现两个nginx错误...

Answer 1

我也遇到了同样的错误，我找到了解决方案，但不知道是否正确。更改文件的第一行/etc/nginx/nginx.conf

user www-data;至user root;

Answer 2

0
投票

查看您的应用程序的puma.error.log文件。

nginx错误：（13：连接到上游时权限被拒绝）]]

问题描述投票：5回答：2

2个回答

最新问题

nginx错误：（13：连接到上游时权限被拒绝）]]

问题描述 投票：5回答：2

2个回答

最新问题

问题描述投票：5回答：2