WebDAV shows only empty folder

1,299 views
Skip to first unread message

TheExoduser

unread,
Oct 25, 2014, 10:12:11 AM10/25/14
to sea...@googlegroups.com
Hey there,

today I configured the webdav interface of seafile.
After a bit of configuration I finally got it working, I can connect to my seafile server over webdav.

But after I've connected via webdav, there isn't any library, folder or file visible. It only shows a empty list (same on google chrome, cyberduck or windows explorer).
Just ask if you need further information.

Anybody here who can help me resolve this problem?


Thanks!

Shuai Lin

unread,
Oct 25, 2014, 11:31:57 AM10/25/14
to sea...@googlegroups.com
Can you post a screenshot of what it looks like when visiting your webdav server from your browser?

--
You received this message because you are subscribed to the Google Groups "seafile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to seafile+u...@googlegroups.com.
To post to this group, send email to sea...@googlegroups.com.
Visit this group at http://groups.google.com/group/seafile.
For more options, visit https://groups.google.com/d/optout.

TheExoduser

unread,
Oct 25, 2014, 12:22:55 PM10/25/14
to sea...@googlegroups.com
Of course, here the screenshot (user censored). That's what I'm getting after entering my credentials via HTTP AUTH.

I configured everything, following the instructions from here http://manual.seafile.com/extension/webdav.html
Unbenannt.PNG

Shuai Lin

unread,
Oct 25, 2014, 12:45:29 PM10/25/14
to sea...@googlegroups.com
Are your libraries encrypted? Seafile WebDAV server won't show encrypted libraries. Also you can check the content of logs/seafdav.log.

TheExoduser

unread,
Oct 25, 2014, 12:54:02 PM10/25/14
to sea...@googlegroups.com
None of my libraries is encrypted, so this cannot be a problem. And the seafdav.log file, doesn't have anything in it, it's a complete empty file :(

Shuai Lin

unread,
Oct 25, 2014, 3:12:02 PM10/25/14
to sea...@googlegroups.com
Can you show me your seafile config files?
Message has been deleted

TheExoduser

unread,
Oct 25, 2014, 3:35:43 PM10/25/14
to sea...@googlegroups.com
Well there you go:

seafdav.conf
[WEBDAV]
enabled = true
port = 8080
fastcgi = true
share_name = /seafdav

ccnet.conf:
[General]
USER_NAME = SynCloud
ID = 141e8e9a08aefb919d79ddcab400702270bd68a1
NAME = SynCloud
SERVICE_URL = ...
[Network]
PORT = 10001
[Client]
PORT = 13418

Any config I've forgotten? Please tell me if it's so,
What I've forgotten to tell is, my complete Seafile (with Seafdav) is running behind an apache webserver.

The things I've written in my apache2.conf (path censored):
FastCGIExternalServer .../seahub.fcgi -host 127.0.0.1:8000
FastCGIExternalServer .../seafdav.fcgi -host 127.0.0.1:8080

and in my virtual hosts file (censored):
LoadModule headers_module modules/mod_headers.so
<VirtualHost *:80>
    ServerName ...
    DocumentRoot ...
    Alias /media  /...

    #Header always set Strict-Transport-Security "max-age=63072000; includeSubDomains"

    Redirect permanent / https://.../
</VirtualHost>
<VirtualHost *:443>
    ServerName ...
    DocumentRoot ...
    Alias /media  /...

    SSLEngine On
    SSLCertificateFile ...
    SSLCertificateKeyFile ...
    SSLCertificateChainFile ...

    Header always set Strict-Transport-Security "max-age=63072000; includeSubDomains"

    RewriteEngine On

    <Location /media>
        Options Indexes FollowSymLinks
AllowOverride None
# New Style (Apache2 2.4+)
# Require all granted

# Old Style
        # Order allow, deny
Allow from all
    </Location>

    #
    # seafile fileserver
    #
    ProxyPass /seafhttp http://127.0.0.1:8082 retry=0 timeout=5
    ProxyPassReverse /seafhttp http://127.0.0.1:8082
    RewriteRule ^/seafhttp - [QSA,L]

    #
    # seafile webdav
    #
    RewriteCond %{HTTP:Authorization} (.+)
    RewriteRule ^(/seafdav.*)$ /seafdav.fcgi$1 [QSA,L,e=HTTP_AUTHORIZATION:%1]
    RewriteRule ^(/seafdav.*)$ /seafdav.fcgi$1 [QSA,L]

    #
    # seahub
    #
    RewriteRule ^/(media.*)$ /$1 [QSA,L,PT]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^(.*)$ /seahub.fcgi$1 [QSA,L,E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
</VirtualHost>

Any idea why it isn't showing me any files/folders ? The web interface and the sync client are both working perfectly :(

TheExoduser

unread,
Oct 25, 2014, 10:34:46 PM10/25/14
to sea...@googlegroups.com
I've just tested it with another user, there all files are showing up :(
Is it a problem that my account has admin rights?

Shuai Lin

unread,
Oct 25, 2014, 10:41:47 PM10/25/14
to sea...@googlegroups.com
Hard to say so. I have tested it with an admin account, but there is no problem. As long as you have created libraries with that account, they should show up.

You can temporarily set the "another user" as admin, and check if the files can still show up normally.

TheExoduser

unread,
Oct 25, 2014, 11:53:21 PM10/25/14
to sea...@googlegroups.com
Nope. If I set the other user account as admin the files are still appearing. 
This problem only occurs on my user account.

The only differences are listed below:

My Account:
Current amount of libraries: 5
Max. Storage: 50GB
Current Storage: ~20GB
Is Admin: true

The test account:
Current amount of libraries: 1 (only standard library)
Max. Storage: 1MB (account isonly for testing purposes)
Current Storage: ~300KB
Is Admin: false (temporarily yes)

Do you have any idea left what can cause this annoying problem :/ ?

TheExoduser

unread,
Oct 26, 2014, 9:31:44 AM10/26/14
to sea...@googlegroups.com
Just tested it with another registered user that has already uploaded content in his libraries.
The same problem occurs here, too.
The only user where I can view the libraries and files (and up-/download) is the "test" user that was newly added.
I've no idea why it's working with the test user, but not with a registered user :/


Am Sonntag, 26. Oktober 2014 03:41:47 UTC+1 schrieb Shuai Lin:

Grigory Shorin

unread,
Nov 1, 2014, 7:13:44 AM11/1/14
to sea...@googlegroups.com
I had the same problem. After some research I opened webdav site in browser using the problem user account and saw the error. Problem was in parsing repositories with the same name. In the bottom of error message was the ID of the duplicate repository
I revoked user rights to this repository  and the problem disappeared

Shuai Lin

unread,
Nov 1, 2014, 7:24:14 AM11/1/14
to sea...@googlegroups.com
Yeah, this problem has been fixed and would be included in the next release.

TheExoduser

unread,
Nov 1, 2014, 1:33:01 PM11/1/14
to sea...@googlegroups.com
All right, thanks!
Reply all
Reply to author
Forward
0 new messages