我将nginx配置为使用SSL证书(从sslforfree.com获取),但之后发生了一种奇怪的行为。网站运行正常,但我无法做任何设计行动,例如如果有人在使用SSL之前登录,则无法注销,其他人无法登录/注册。
我在Digital-Ocean一键式导轨液滴上进行配置。以下观察可能有所帮助
Nginx.error.log
1 - SSL握手时客户端关闭连接
2 - SSL_do_handshake()失败(SSL:错误:1408F10B:SSL例程:ssl3_get_record:错误的版本号) - 我研究并发现它由于SSL配置中的问题而发生,我尝试使用Mozilla生成的但没有成功。
Rails服务器日志
1 - 422不可处理的实体
2 - ActionController :: InvalidAuthenticityToken(ActionController :: InvalidAuthenticityToken)
nginx.conf
upstream puma {
server unix:///home/rails/apps/calwinkle/shared/tmp/sockets/calwinkle-puma.sock;
}
server {
listen 80 default_server;
listen [::]:80 default_server;
server_name calwinkle.com www.calwinkle.com;
# Redirect all HTTP requests to HTTPS with a 301 Moved Permanently response.
return 301 https://$host$request_uri;
}
server {
# listen 80;
listen 443 ssl default_server;
listen [::]:443 ssl default_server;
server_name calwinkle.com www.calwinkle.com;
ssl_certificate /etc/nginx/ssl/nginx.crt;
ssl_certificate_key /etc/nginx/ssl/nginx.key;
# intermediate configuration. tweak to your needs.
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers 'ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:ECDHE-ECDSA-DES-CBC3-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:!DSS';
ssl_prefer_server_ciphers on;
root /home/rails/apps/calwinkle/current/public;
access_log /home/rails/apps/calwinkle/current/log/nginx.access.log;
error_log /home/rails/apps/calwinkle/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;
}
我的想法是,我的设计控制器仍然试图使用http访问,我已经将所有http请求重定向到https 301,这导致真实性令牌过期。
我试图删除重定向并接受http和https,但这导致nginx配置错误。
鉴于您的情况,您似乎设置了错误的标题。所以cookie /会话正在http上保存。您可以尝试在/etc/nginx/sites-available/*
和/etc/nginx/sites-enabled/*
中添加以下两行
proxy_set_header Host $http_host;
proxy_set_header X-Forwarded-Proto https;
完成后:
sudo service nginx restart
此外,在浏览器中清除会话和cookie。
如果您的站点与用户一起使用(我认为不应该没有https),您可能需要销毁现有的用户会话。
希望能帮助到你。