Nginx Seafile文件上传不起作用,即使在设置了;文件“U服务器”根目录;变量
我正试图让Seafile在nginx反向代理后运行。我跟着这个:还有这个: 我的配置如下:Nginx Seafile文件上传不起作用,即使在设置了;文件“U服务器”根目录;变量,nginx,reverse-proxy,seafile-server,Nginx,Reverse Proxy,Seafile Server,我正试图让Seafile在nginx反向代理后运行。我跟着这个:还有这个: 我的配置如下: 运行vhost“cloud.mydomain.tld”的Nginx Seafile和Seahub(在fastcgi模式下)均在其默认端口上运行 我的seahub_settings.py如下所示: HTTP_SERVER_ROOT = 'https://cloud.mydomain.tld/seafhttp' -- I added this to try it FILE_SERVER_ROOT = 'ht
- 运行vhost“cloud.mydomain.tld”的Nginx
- Seafile和Seahub(在fastcgi模式下)均在其默认端口上运行
- 我的seahub_settings.py如下所示:
HTTP_SERVER_ROOT = 'https://cloud.mydomain.tld/seafhttp' -- I added this to try it FILE_SERVER_ROOT = 'https://cloud.mydomain.tld/seafhttp' SECRET_KEY = "12345678-1234-1234-1234-1234567890123456" DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', 'NAME': 'seahub-db', 'USER': 'seafile', 'PASSWORD': 'mypassword', 'HOST': '127.0.0.1', 'PORT': '3306', 'OPTIONS': { 'init_command': 'SET storage_engine=INNODB', } } }
- 我的nginx配置:
### Cloud ### # No-SSL redirect server { listen 80; server_name cloud.mydomain.tld; return 301 https://$server_name$request_uri; } # SSL server { listen 443 ssl; server_name cloud.mydomain.tld; ssl_certificate /etc/letsencrypt/live/cloud.mydomain.tld/cert.pem; ssl_certificate_key /etc/letsencrypt/live/cloud.mydomain.tld/privkey.pem; location / { fastcgi_pass 127.0.0.1:8000; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_param PATH_INFO $fastcgi_script_name; fastcgi_param SERVER_PROTOCOL $server_protocol; fastcgi_param QUERY_STRING $query_string; fastcgi_param REQUEST_METHOD $request_method; fastcgi_param CONTENT_TYPE $content_type; fastcgi_param CONTENT_LENGTH $content_length; fastcgi_param SERVER_ADDR $server_addr; fastcgi_param SERVER_PORT $server_port; fastcgi_param SERVER_NAME $server_name; fastcgi_param REMOTE_ADDR $remote_addr; access_log /var/log/nginx/seahub.access.log; error_log /var/log/nginx/seahub.error.log; fastcgi_read_timeout 36000; } location /seafhttp { rewrite ^/seafhttp(.*)$ $1 break; proxy_pass http://127.0.0.1:8082; client_max_body_size 0; proxy_connect_timeout 36000s; proxy_read_timeout 36000s; proxy_send_timeout 36000s; send_timeout 36000s; } location /media { root /home/cloud/seafile-server-latest/seahub; } }
- 这应该是最重要的
main.ad03aea1e16e.js:215 Mixed Content: The page at 'https://cloud.mydomain.tld/#my-libs/lib/12345678-1234-1234-1234-123456789012' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://cloud.mydomain.tld:8082/upload-aj/12345678-1234-1234-1234-123456789012'. This request has been blocked; the content must be served over HTTPS.
send @ main.ad03aea1e16e.js:215
这意味着,seahub仍在尝试连接到“旧”上传服务,这当然不再有效。直到现在,我还没有找到这个问题的任何解决方案。我只是通过同样的问题找到了你的问题 这很简单:seahub db中有一个constance_配置(使用MySQL,与sqlite应用相同的东西),它记录配置并覆盖普通配置文件 可以从管理控制台(右上角)修改此配置,也可以简单地截断此表以重新生成它 这是从5.0.0()开始的新“功能” 问候,,
朱利安谢谢你!这真的很奇怪。。。为什么他们会提供一个配置文件,然后用一些数据库设置覆盖它?谢谢!我只需看一下你问题的标题就解决了我的问题!:)