I am still concerned that something is not quite right with your setup because you are unable to use 127.0.0.1 (local loopback address) in the network settings of the server itself.

Glad to hear you seem to have resolved your issues. Hopefully this will help with the WebDAV issues. Replace the original files in the two locations with the backup copies that you saved. Test the remote WebDAV connections to determine if the fix has resolved the issue. Go back into Server.app and restart the file sharing service. You will need to authenticate as admin when you attempt to replace the files. In Finder - copy the two files that you edited on the desktop and replace the original files in their original locations with the edited versions of the files from the desktop. In Server.app - go to File Sharing service and turn off the service. Look at the line below that for the line that reads 0 and change the 0 to a 1 so that it reads 1 Open the desktop copy of .plist using TextEdit.

Open the desktop copy of http_nf using TextEdit.Р”Р‡ind the line that reads 'AuthType Digest' change it to 'AuthType Basic' Navigate to Server HD/Library/Server/Web/Config/apache2/webapps Make a second copy of this file in a safe location - for backup. Navigate to Server HD/Library/Server/Web/Config/apache2Р”В¬opy it to your desktop (you are going to make changes on the desktop copy of this file). If not - you can easily undo the fix and put it back to the way it was. There is a fix for the WebDAV remote connection issue - and it may or may not solve the WebDAV issue for you. Some people have reported issues with remotely connecting to WebDAV shares. I've got several issues with my services, and - while I believed to have set it up correctly - all signs point to DNS issues.Р”В®verything *looks* right, but I'm having issues left and right with file sharing (WebDAV), user and group management (with and without Open Directory), etc. Very real world and very good best practices thinking. There is more information packed into those 200+ pages than a hundred searches and hours spent online. Stop reading this and buy the book on iTunes and read it straight through. I can't recommend El Capitan Server - Foundation Services by Reid Bundonis highly enough. THEN move on to the secondary services like web, VPN and the like. Getting all of these right first is critical. Then I'd move on to DHCP and finally Open Directory. I've chased problem too often with bad DNS so now if I see a bad DNS config and the server isn't online yet, I typically nuke and pave and get that part right before anything else.

DNS is primary and you have to have it rock solid before you do anything else. A secondary (192.168.1.101) IP turns into your go to for everything else webish. Leave the primary in place for Server so it can do what it needs to for Open Directory and its internal websites. I multihome my servers due to the aggressive way Server app has been holding onto web ports. Deploy the server and get your SSL certs in place. Forward the appropriate ports for the services you plan to host on your server as you open them up so I don't worry about them yet. Typically I would put the modem into bridge mode and then let the airport handle the routing and NAT. If you can't allow access to the entire 17.0.0.Is your modem in bridge mode? What devices are handling NAT, DHCP, DNS? It's best to let your device access these ports on the entire 17.0.0.0/8 address block, which is assigned to Apple. The APNs servers use load balancing, so your devices don't always connect to the same public IP address for notifications. The connection on port 443 uses a proxy as long as the proxy allows the communication to pass through without decrypting. TCP port 443 is used during device activation, and afterwards for fallback if devices can't reach APNs on port 5223. TCP port 443 or 2197 to send notifications to APNs.TCP port 5223 to communicate with APNs.If you use a firewall or private Access Point NameР’В for cellular data, your Apple devices must be able to connect to specific ports on specific hosts:

Apple server ip address