Q: Webdav Sharing doesn't work after Server 5 update

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...

if you use iOS or transmit on OS X webdav sharing works, only finder is the problem. I spend a bug report...

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)?

what about pages or keynote on iOS? That worked for me, also PDFExpert (on iOS) and Windows 7 work

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.

Same issue here- Webdav won't work for Mac, Transmit, or in Pages..

Also, the new IOS (OS X Server Accounts) feature fails to allow authentication-- I'm assuming it's based on Webdav...

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.

It could be different for my configuration/setup. Using the finder, I can only log into a webdav share when I use the short version of the username. The mac then asks me to accept the certificate of the server, then a finder window with the webdav share opens. I have tried only with a local user account, not an OD account.

I think maybe you have a different issue; it still does not work for me even if I use my server's IP address.

I have an AppleCare case open for this issue. I will post any useful info from that as I get it.

I just heard back from Apple Enterprise Support via AppleCare. They analysed the logs from my server and confirmed that this is a  defect in Server 5,.0. Apparently the issue has been escalated with high priority and a fix should be forthcoming in an update to Server, hopefully fairly soon.

Thanks! I haven't heard back from my bug report yet..

Thanks!

I can confirm this worked for me as well.. I've had to do this for servers ACTUALLY  bound to AD before, but don't know why Server 5 would have this issue...

(running on 10.11)