Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Webdav Sharing doesn't work after Server 5 update

Since I updated my Yosemite server to Server 5.0.3 and 5.0.4, Webdav sharing doesn't work.


The most significant information I get is this in /Library/Logs/PasswordService/ApplePasswordServer.Error.log


'algorithm' must be 'md5' or 'md5-sess'


Anybody has a solution for this?

Mac Mini Server (Late 2012), OS X Yosemite (10.10)

Posted on Sep 25, 2015 11:46 AM

Reply
30 replies

Jun 5, 2017 6:35 PM in response to Drizzt

Hello,


I have WebDAV setup on our Mac here, 10.12.5 Server.app version 5.3.1


When I upload files using WebDAV, I do not get the option to rename any duplicates, it will just go over the top. I also can't see any files or folders. Therefore I cannot import files into an app such as 'Pages'.


I also cannot for the life of me work out how to do Directory browsing. This is a feature in IIS on a windows server.


I guess my first question is, can anyone do what I am talking about? Do these features exist for WebDav on MacOS?

Sep 26, 2015 6:54 AM in response to Drizzt

I am seeing the same symptoms (no WebDAV connection can be established) after updating server from 4.x to 5.0.4. However, I do not see *any* errors or messages in /Library/Logs/PasswordService/ApplePasswordServer.Error.log or /Library/Logs/PasswordService/ApplePasswordServer.Server.log.


It seems that WebDAV is completely broken in 5.0.4. How can Apple release such a broken version of OS X Server?


This issue does *not* seem to be fixed in the late server 5.0 beta (5.0.15) [installed on a test machine]. I still see the same issue; no WebDAV connectivity and no errors in any log that I can find...

Sep 27, 2015 12:55 AM in response to michaelhoch

For me neither Transmit on OS X (latest version) nor Transmit on iOS (latest version) is working. Both give 'either your username or password are incorrect or the server does not support WebDAV' but the credentials I am using are correct. Both worked just fine with Server 4.x.


Interestingly, if I use a browser to go to 'https://my-server-fqdn/sharename' I get a 'page not found error'. I would have thought that I should have seen something other than that ion the WebDAV shares were being properly published. SO maybe my issue is not one of authentication but something else?


Does anyone have any ideas how I can troubleshoot this as waiting for Apple to respond to the bug will take months (or longer)?

Sep 27, 2015 1:10 AM in response to michaelhoch

No, they also fail (they used to work fine before) with 'username or password is incorrect'. I can see the connection attempts logged in:


/var/log/apache2/service_proxy_access.log

/var/log/apache2/service_proxy_error.log


but I don't see anything that looks like an error in there.


Every time I try (and fail) to connect I see the following in opendirectoryd.log:


2015-09-27 09:07:37.766163 BST - AID: 0x0000000000000000 - 45934.1079368 - Client: httpd, UID: 70, EUID: 70, GID: 70, EGID: 70

2015-09-27 09:07:37.766163 BST - AID: 0x0000000000000000 - 45934.1079368, Node: /LDAPv3/127.0.0.1, Module: AppleODClientPWS - Parse error

2015-09-27 09:07:37.766187 BST - AID: 0x0000000000000000 - 45934.1079368 - Client: httpd, UID: 70, EUID: 70, GID: 70, EGID: 70

2015-09-27 09:07:37.766187 BST - AID: 0x0000000000000000 - 45934.1079368, Node: /LDAPv3/127.0.0.1, Module: AppleODClientPWS - could not continue SASL client session: generic failure (-1) (5103)

2015-09-27 09:07:37.777753 BST - AID: 0x0000000000000000 - 45934.1079373 - Client: httpd, UID: 70, EUID: 70, GID: 70, EGID: 70

2015-09-27 09:07:37.777753 BST - AID: 0x0000000000000000 - 45934.1079373, Node: /LDAPv3/127.0.0.1, Module: AppleODClientPWS - Parse error

2015-09-27 09:07:37.777773 BST - AID: 0x0000000000000000 - 45934.1079373 - Client: httpd, UID: 70, EUID: 70, GID: 70, EGID: 70

2015-09-27 09:07:37.777773 BST - AID: 0x0000000000000000 - 45934.1079373, Node: /LDAPv3/127.0.0.1, Module: AppleODClientPWS - could not continue SASL client session: generic failure (-1) (5103)


Which looks suspicious. But these same (OD) users are working fine for Mail, Calendar, Contacts, SMB, AFP and even authenticated website access.


I hope that Apple takes notice of this ASAP.

Sep 30, 2015 12:32 PM in response to Drizzt

For me the webdav protocol works (Server 5.0.4), when I enter my servers ip address (aaa.bbb.ccc.ddd) directly instead of entering the servers hostname (host.domain.com). This works for me, whether I access the server from the Finder of OS X of another mac or from iOS apps like Pages from an iPhone or iPad. It appears as if the hostname is somehow not translated into the proper ip address on the server.

Webdav Sharing doesn't work after Server 5 update

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.