Webdav Proxy error on Apache

Seafile Server
1

hi, since 6.3.7 pro, webdav is not working anymore

On 6.3.8, the issue is the following

Service unavailable

apache error.log says :

    [Tue Dec 11 13:33:31.252685 2018] [proxy:error] [pid 29392] (111)Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:8080 (127.0.0.1) failed
	[Tue Dec 11 13:33:31.252744 2018] [proxy_http:error] [pid 29392] [client 194.254.171.10:20863] AH01114: HTTP: failed to make connection to backend: 127.0.0.1

Apachye HTTS config is

    SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
    ProxyPass /davf http://127.0.0.1:8080/davf
    ProxyPassReverse /davf http://127.0.0.1:8080/davf

Seafdav.conf is

    [WEBDAV]
	enabled = true
	port = 8080
	fastcgi = false
	share_name = /davs

On a 6.3.7 version, i have a timeout and different apache error.log

	[Tue Dec 11 13:27:55.826715 2018] [proxy_http:error] [pid 16676] (70007)The timeout specified has expired: [client 194.254.171.10:59582] AH01102: error reading status line from remote server 127.0.0.1:8080
	[Tue Dec 11 13:27:55.826827 2018] [proxy:error] [pid 16676] [client 194.254.171.10:59582] AH00898: Error reading from remote server returned by /davf

Do we have to enable webdav and webdav_fs modules on apache ?

I did it, but it did ot solves the issue

2

You configure Apache to /davf and WEBDAV share is /davs.

As I recall Apache should redirect to the name of WEBDAV folder. In your case it should be DAVS

3

Hi, thank you but i made a typo error

My Webdav conf is

[WEBDAV]
enabled = true
port = 8080
fastcgi = false
share_name = /davf

the apache log error is

[Tue Dec 11 13:27:55.826827 2018] [proxy:error] [pid 16676] [client 194.254.171.10:59582] AH00898: Error reading from remote server returned by /davf

BTW, there is no process called wsgidav and there is no process listening on port 8080.

@jobenvil, i saw that you find helped someone on a similar problem. Could you help me ?

@daniel.pan, how can i find why wsgidav is not starting on Seafile service startup (i’m not using fastcgi anymore and i’m quite shure it was working on previous version than 6.3.7)

4

There is a bug of pro 6.3.8. We will fix it soon.

You can install the Python library manually to solve the problem now:

sudo pip install pycryptodome==3.7.2
5

When will 6.3.9 be available ? We need the Shibboleth Support for Webdav :slight_smile:

1 Like
6

Hi, thank you, Webdav is Ok now

7

On Red Hat Enterprise Linux 7 (CentOS 7) I did

yum install python2-pycryptodomex.x86_64

But this did not solve the problem.
Any help is highly appreciated.