Until now, I did not find out any solution for this problem. This means, that seahub is still trying to connect to the "old" upload service, which of course does not work anymore. All is great, and the performance is great, but Im used to be able to point my file managers to. Upgrade seafile-server AUR from the Arch User Repository. I am installing Seafile on my unRAID server via docker. This request has been blocked the content must be served over HTTPS. First, stop each of your seafile server instances (e.g. So now, when I delete my old seahub_settings.pyc, start seahub (in fastcgi mode, of course), point the browser to my library and try to upload something, I get the following error message in the F12 developer console: :215 Mixed Content: The page at '' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint ''. Root /home/cloud/seafile-server-latest/seahub Ssl_certificate_key /etc/letsencrypt/live//privkey.pem įastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name įastcgi_param PATH_INFO $fastcgi_script_name įastcgi_param SERVER_PROTOCOL $server_protocol įastcgi_param QUERY_STRING $query_string įastcgi_param REQUEST_METHOD $request_method įastcgi_param CONTENT_TYPE $content_type įastcgi_param CONTENT_LENGTH $content_length Īccess_log /var/log/nginx/ Įrror_log /var/log/nginx/ Ssl_certificate /etc/letsencrypt/live//cert.pem 'init_command': 'SET storage_engine=INNODB', My seahub_settings.py looks like this: HTTP_SERVER_ROOT = '' - I added this to try it Seafile and Seahub (in fastcgi mode) both running on their default ports.I'm trying to get Seafile running behind a nginx reversed proxy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |