Nginx + Unicorn無法訪問Rails應用程序

Question

昨天我可以看到像您在這里看到的默認頁面。

但是今天，我修改了nginx的配置，以訪問在獨角獸上運行的Rails應用程序並開始獲取404。

/etc/nginx/nginx.conf

user www-data;
worker_processes 4;
pid /var/run/nginx.pid;

events {
  worker_connections 768;
  # multi_accept on;
}

http {
  ##
  # Basic Settings
  ##

  sendfile on;
  tcp_nopush on;
  tcp_nodelay on;
  keepalive_timeout 65;
  types_hash_max_size 2048;

  include /etc/nginx/mime.types;
  default_type application/octet-stream;

  ##
  # Logging Settings
  ##

  access_log /var/log/nginx/access.log;
  error_log /var/log/nginx/error.log;

  ##
  # Gzip Settings
  ##

  gzip on;
  gzip_disable "msie6";

  ##
  # Virtual Host Configs
  ##

  include /etc/nginx/conf.d/*.conf;
  include /etc/nginx/sites-enabled/*;
}

/ etc / nginx / sites-available / default

upstream unicorn {
  server unix:/tmp/unicorn.integrity_matters.sock fail_timeout=0;
}

server {
  listen 80;
  server_name localhost;
  root /home/ubuntu/integrity_matters/current/public;

  location ~ ^/assets/ {
    gzip_static on;
    expires max;
    add_header Cache-Control public;
  }

  try_files $uri/index.html $uri @unicorn;
  location @unicorn {
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Host $http_host;
    proxy_redirect off;
    proxy_pass http://unicorn;
  }

  error_page 500 502 503 504 /500.html;
  client_max_body_size 20M;
  keepalive_timeout 10;
}

MY_APP_ROOT / config / unicorn.rb

root = "/home/imdeploy/integrity_matters/current"
working_directory root
pid "#{root}/tmp/pids/unicorn.pid"
stderr_path "#{root}/log/unicorn.log"
stdout_path "#{root}/log/unicorn.log"

listen "/tmp/unicorn.integrity_matters.sock"
worker_processes 2
timeout 30

# Force the bundler gemfile environment variable to
# reference the capistrano "current" symlink
before_exec do |_|
  ENV\["BUNDLE_GEMFILE"\] = File.join(root, 'Gemfile')
end][2]

我還驗證了連接到EC2的安全組允許22、80和443端口。 請找到隨附的EC2安全規則。

我多次重啟了nginx和unicorn，並驗證了nginx和unicorn是否正常運行。

我還驗證了nginx的訪問和錯誤日​​志，但是在那里看不到任何活動。

請幫忙，

Answer 1

nginx.conf包含的配置文件路徑是/etc/nginx/sites-enabled/*; 但您的默認配置文件位於/etc/nginx/sites-available/default 。

將sites-enabled sites-available更改sites-enabled sites-available ，然后重試。

Answer 2

最后，我能夠修復它。 問題是AWS希望使nginx SSL感知。

為了使其正常工作，我創建了自簽名證書並修改了Nginx配置。 下面是最終配置。

/ etc / nginx / sites-available / default

upstream integrity_matters_server {
  server unix:/tmp/unicorn.integrity_matters.sock fail_timeout=0;
}

server {
  listen   80;
  server_name ec2-52-10-245-227.us-west-2.compute.amazonaws.com;
  rewrite ^/(.*) https://ec2-52-10-245-227.us-west-2.compute.amazonaws.com permanent;
}

server {
  listen   443;
  server_name ec2-52-10-245-227.us-west-2.compute.amazonaws.com;
  root /home/ubuntu/integrity_matters/current/public;

  ssl on;
  ssl_certificate      /etc/nginx/ssl/nginx_im.crt;
  ssl_certificate_key  /etc/nginx/ssl/nginx_im.key;
  ssl_protocols        SSLv3 TLSv1;
  ssl_prefer_server_ciphers on;

  location ~ ^/assets/ {
    gzip_static on;
    expires max;
    add_header Cache-Control public;
  }

  try_files $uri @integrity_matters;
  location @integrity_matters {
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto https;
    proxy_set_header Host $host;
    proxy_redirect off;
    proxy_pass http://integrity_matters_server;
  }

  error_page 500 502 503 504 /500.html;
  client_max_body_size 20M;
  keepalive_timeout 10;
}

在我們進行SSL配置時，此帖子也很有用。