Warning: file_get_contents(/data/phpspider/zhask/data//catemap/9/ssl/3.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
Ruby on rails 已解决-带有Nginx https配置的Rails web应用程序显示403禁止_Ruby On Rails_Ssl_Nginx_Https_Ubuntu 18.04 - Fatal编程技术网

Ruby on rails 已解决-带有Nginx https配置的Rails web应用程序显示403禁止

Ruby on rails 已解决-带有Nginx https配置的Rails web应用程序显示403禁止,ruby-on-rails,ssl,nginx,https,ubuntu-18.04,Ruby On Rails,Ssl,Nginx,Https,Ubuntu 18.04,我的nginx配置是: “/etc/nginx/sites available/default” 我忘了什么? 我做了一个自签名SSL配置。 我在ubuntu 18.04上 编辑:错误403显然已解决,现在我在尝试保存某些内容时得到: 这是403年工作的实际配置: “/etc/nginx/sites available/default” 我用这个配置解决了上面的错误: 服务器上的ssl块 location @app { proxy_pass http://app;

我的nginx配置是: “/etc/nginx/sites available/default”

我忘了什么? 我做了一个自签名SSL配置。 我在ubuntu 18.04上

编辑:错误403显然已解决,现在我在尝试保存某些内容时得到:

这是403年工作的实际配置: “/etc/nginx/sites available/default”

我用这个配置解决了上面的错误: 服务器上的ssl块

    location @app {
        proxy_pass http://app;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_redirect http://141.221.15.171 https://141.221.15.171;
        proxy_set_header  Host $host;
        proxy_set_header  X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header  X-Forwarded-Proto $scheme;
        proxy_set_header  X-Forwarded-Ssl on;
        proxy_set_header  X-Forwarded-Port $server_port;
        proxy_set_header  X-Forwarded-Host $host;
    }


您没有在处理ssl连接的服务器块上设置
location@app
块或
try\u files@app$uri
语句。请同时添加nginx日志、access.log和errors.log。因此,我们也可以更好地理解错误,
try_files@app$uri将无法按预期工作。您打算使用:
try_files$uri@app好了,伙计们,成功了,不再禁止403了。但我有另一个错误,我不知道这是否相关,你能说些什么吗?如果新错误是无关的,我将在堆栈上创建另一个问题。提前感谢。按照rails生产日志:2019-09-14 10:15:11+0000由TasksController处理的141.221.15.171的“Started POST”/tasks,创建为HTML参数:{…}HTTP源标头()与请求不匹配。基本url()在1ms内完成422个不可处理的实体(ActiveRecord:0.0ms)ActionController::InvalidAuthenticationToken(ActionController::InvalidAuthenticityToken):actionpack(5.2.3)lib/action\u controller/metal/request\u forgery\u protection.rb:211:在“handle\u unverified\u request”中```
upstream app {
    server unix:/home/benhur/servidor/shared/sockets/puma.sock fail_timeout=0;
}
server {
    listen 443 ssl;
    listen [::]:443 ssl;
    include snippets/self-signed.conf;
    include snippets/ssl-params.conf;
    server_name 141.221.15.171;
    root /home/benhur/servidor/public;
    try_files $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;
    }
    index index.html index.htm index.nginx-debian.html;
}
server {
    listen 80;
    listen [::]:80;
    server_name 141.221.15.171;
    return 301 https://$server_name$request_uri;
    root /home/benhur/servidor/public;
    try_files $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;
}
    location @app {
        proxy_pass http://app;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_redirect http://141.221.15.171 https://141.221.15.171;
        proxy_set_header  Host $host;
        proxy_set_header  X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header  X-Forwarded-Proto $scheme;
        proxy_set_header  X-Forwarded-Ssl on;
        proxy_set_header  X-Forwarded-Port $server_port;
        proxy_set_header  X-Forwarded-Host $host;
    }