Unable to Upload

Seafile Server
1

Hi,

I’m having some problems with uploading, ever since moving Seafile off the root domain. I am able to successfully see my library, and I can access /seafile/ (for Seahub), /seafhttp/ (blank page), and /seafmedia/ (forbidden). I’m guessing seafmedia is supposed to be forbidden, but if I am wrong please let me know. Here are some of my conigurations:

ccnet.conf

[General]
USER_NAME = Mauris
ID = 1f2baa09a203091c09840cc8da49635ba43161b6
NAME = Mauris
SERVICE_URL = http://mauris.kbnetwork.ca/seafile

[Client]
PORT = 13419

seahub_settings.py

SECRET_KEY = "TRUNCATED"
SERVE_STATIC = False
MEDIA_URL = '/seafmedia/'
COMPRESS_URL = MEDIA_URL
STATIC_URL = MEDIA_URL + 'assets/'
SITE_ROOT = '/seafile/'
LOGIN_URL = '/seafile/accounts/login/'    # NOTE: since version 5.0.4

000-default.conf (Apache config)

<VirtualHost *:80>
ServerName mauris.kbnetwork.ca
# Use "DocumentRoot /var/www/html" for Centos/Fedora
# Use "DocumentRoot /var/www" for Ubuntu/Debian
DocumentRoot /var/www/html
Alias /seafmedia  /home/keith/seafile-server-latest/seahub/media

RewriteEngine On

<Location /seafmedia>
    ProxyPass !
    Require all granted
</Location>

#
# seafile fileserver
#
ProxyPass /seafhttp http://127.0.0.1:8082
ProxyPassReverse /seafhttp http://127.0.0.1:8082
RewriteRule ^/seafhttp - [QSA,L]

#
# seahub
#
SetEnvIf Request_URI . proxy-fcgi-pathinfo=unescape
SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
ProxyPass /seafile fcgi://127.0.0.1:8000/seafile
</VirtualHost>

I’ve uploaded some logs on my Amazon Cloud Drive. I did a quick search in them and I can’t seem to find anything when I search on Google. Here is the link. The only thing that stands out is in seafile.log:

[08/03/2016 05:38:48 PM] ../common/mq-mgr.c(106): [mq mgr] publish to heartbeat mq: seaf_server.heartbeat

Any suggestions? Thanks!

2

Just in case anybody has the same issue I’m having here. I took a quick look into the console on the browser when uploading. I was getting an issue where the browser was blocking mixed content, because while the Seafile WebUI was over HTTPS, Seafile (seafhttp) was not. I corrected this by changing my SERVICE_URL and FILE_SERVER_ROOT to include HTTPs.

2 Likes
3

Thanks that helped.
Changing the normal Config was not enough for me, I had to change it over admin panel.