We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
操作步骤: 正常登录后台,进行设置 之后所有页面访问都会出现如上图提示 使用的是nginx反向代理, 启动命令:docker run --name typecho-server -v /var/typecho:/app/usr -p 8081:80 -e TYPECHO_SITE_URL=https://blog.xxxx.com -d joyqi/typecho:nightly-php7.4 nignx配置: server { listen 80; server_name blog.xxxx.com;
rewrite ^(.*)$ https://$host$1 permanent; #charset koi8-r; #access_log logs/host.access.log main; location / { proxy_pass http://127.0.0.1:8081; #root html/public; proxy_set_header Host $http_host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Real-Ip $remote_addr; proxy_set_header X-NginX-Proxy true; proxy_redirect off; #index index.html index.htm; } } server { listen 443 ssl; server_name blog.xxxx.com; ssl_certificate 1_blog.xxxx_bundle.crt; ssl_certificate_key 2_blog.xxxx.com.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; location / { proxy_pass http://127.0.0.1:8081; #index index.html index.htm; proxy_set_header Host $http_host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Real-Ip $remote_addr; proxy_set_header X-NginX-Proxy true; proxy_redirect off; } }
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
操作步骤:
正常登录后台,进行设置
之后所有页面访问都会出现如上图提示
使用的是nginx反向代理,
启动命令:docker run --name typecho-server -v /var/typecho:/app/usr -p 8081:80 -e TYPECHO_SITE_URL=https://blog.xxxx.com -d joyqi/typecho:nightly-php7.4
nignx配置:
server {
listen 80;
server_name blog.xxxx.com;
The text was updated successfully, but these errors were encountered: