[GH-ISSUE #15] 自己服务器配置https不能正确转发 #10

Closed
opened 2026-03-03 11:55:19 +03:00 by kerem · 6 comments
Owner

Originally created by @macreee on GitHub (Mar 26, 2020).
Original GitHub issue: https://github.com/Finb/bark-server/issues/15

bark server用的是313
我是想把443的转到313上
但是试了很多方法都不成功
web服务器是Nginx
想问下作者是用的什么办法转发请求的

Originally created by @macreee on GitHub (Mar 26, 2020). Original GitHub issue: https://github.com/Finb/bark-server/issues/15 bark server用的是313 我是想把443的转到313上 但是试了很多方法都不成功 web服务器是Nginx 想问下作者是用的什么办法转发请求的
kerem closed this issue 2026-03-03 11:55:19 +03:00
Author
Owner

@Finb commented on GitHub (Mar 26, 2020):

是否有域名证书? nginx 配置文件发来看看

<!-- gh-comment-id:604197881 --> @Finb commented on GitHub (Mar 26, 2020): 是否有域名证书? nginx 配置文件发来看看
Author
Owner

@macreee commented on GitHub (Mar 26, 2020):

是否有域名证书? nginx 配置文件发来看看

server {
listen 443;
server_name bark.macree.cn;
ssl on;
ssl_certificate bark.macree.cn.crt;
ssl_certificate_key bark.macree.cn.key;
ssl_session_timeout 5m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:HIGH:!aNULL:!MD5:!RC4:!DHE;
ssl_prefer_server_ciphers on;
return 301 $scheme://bark.macree.cn:313$request_uri;
}
很奇怪,用http不填端口号也行,用https怎么都不行,我不太会Nginx,所以这里可能描述的不是很清楚

<!-- gh-comment-id:604212414 --> @macreee commented on GitHub (Mar 26, 2020): > 是否有域名证书? nginx 配置文件发来看看 server { listen 443; server_name bark.macree.cn; ssl on; ssl_certificate bark.macree.cn.crt; ssl_certificate_key bark.macree.cn.key; ssl_session_timeout 5m; ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:HIGH:!aNULL:!MD5:!RC4:!DHE; ssl_prefer_server_ciphers on; return 301 $scheme://bark.macree.cn:313$request_uri; } 很奇怪,用http不填端口号也行,用https怎么都不行,我不太会Nginx,所以这里可能描述的不是很清楚
Author
Owner

@Finb commented on GitHub (Mar 26, 2020):

你可以参考下我的配置
https://github.com/Finb/bark-server/issues/5#issuecomment-473141149

<!-- gh-comment-id:604213442 --> @Finb commented on GitHub (Mar 26, 2020): 你可以参考下我的配置 https://github.com/Finb/bark-server/issues/5#issuecomment-473141149
Author
Owner

@macreee commented on GitHub (Mar 26, 2020):

你可以参考下我的配置
#5 (comment)

恩。我在研究一下。谢谢回复。

<!-- gh-comment-id:604213803 --> @macreee commented on GitHub (Mar 26, 2020): > 你可以参考下我的配置 > [#5 (comment)](https://github.com/Finb/bark-server/issues/5#issuecomment-473141149) 恩。我在研究一下。谢谢回复。
Author
Owner

@macreee commented on GitHub (Mar 26, 2020):

把配置放这方便人看

申请好证书,把注释项按照自己需求修改了就好。

server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
    server_name api.day.app ;#填写绑定证书的域名

    add_header Strict-Transport-Security "max-age=31536000; includeSubdomains; preload";

    # certs sent to the client in SERVER HELLO are concatenated in ssl_certificate
    ssl_certificate ssl/day.app/day.app.cer;#证书文件名称默认目录同Nginx.conf
    ssl_certificate_key ssl/day.app/day.app.key;#私钥文件名称默认目录同Nginx.conf
    ssl_session_timeout 1d;
    ssl_session_cache shared:SSL:50m;
    ssl_session_tickets off;

    # modern configuration. tweak to your needs.
    ssl_protocols TLSv1.2;
    ssl_ciphers 'ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256';
    ssl_prefer_server_ciphers on;


    # OCSP Stapling ---
    # fetch OCSP records from URL in ssl_certificate and cache them
    ssl_stapling on;
    ssl_stapling_verify on;

    ## verify chain of trust of OCSP response using Root CA and Intermediate certs
    ssl_trusted_certificate ssl/ca.cer;#可忽略。如果要添加的话,可以使用同ssl_certificate相同的证书文件。

    location / {
       proxy_pass http://127.0.0.1:8081;#要转发的地址
    }

}
<!-- gh-comment-id:604219892 --> @macreee commented on GitHub (Mar 26, 2020): 把配置放这方便人看 申请好证书,把注释项按照自己需求修改了就好。 ``` server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name api.day.app ;#填写绑定证书的域名 add_header Strict-Transport-Security "max-age=31536000; includeSubdomains; preload"; # certs sent to the client in SERVER HELLO are concatenated in ssl_certificate ssl_certificate ssl/day.app/day.app.cer;#证书文件名称默认目录同Nginx.conf ssl_certificate_key ssl/day.app/day.app.key;#私钥文件名称默认目录同Nginx.conf ssl_session_timeout 1d; ssl_session_cache shared:SSL:50m; ssl_session_tickets off; # modern configuration. tweak to your needs. ssl_protocols TLSv1.2; ssl_ciphers 'ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256'; ssl_prefer_server_ciphers on; # OCSP Stapling --- # fetch OCSP records from URL in ssl_certificate and cache them ssl_stapling on; ssl_stapling_verify on; ## verify chain of trust of OCSP response using Root CA and Intermediate certs ssl_trusted_certificate ssl/ca.cer;#可忽略。如果要添加的话,可以使用同ssl_certificate相同的证书文件。 location / { proxy_pass http://127.0.0.1:8081;#要转发的地址 } } ```
Author
Owner

@mritd commented on GitHub (Mar 26, 2020):

最新文档已经更新 https://github.com/Finb/bark-server#nginx-proxy

<!-- gh-comment-id:604252772 --> @mritd commented on GitHub (Mar 26, 2020): 最新文档已经更新 https://github.com/Finb/bark-server#nginx-proxy
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/bark-server#10
No description provided.