NAS WebDAV External Access Troubleshooting

This repository contains diagnostic tools and guides to help troubleshoot WebDAV external access issues on NAS systems.

Problem

WebDAV works on intranet but fails from external networks with "Connection refused" error.

Quick Start

Run the diagnostic script on your NAS:
```
sudo ./diagnose_webdav.sh
```
Check port forwarding:
```
./check_port_forwarding.sh
```
Review the troubleshooting guide:
- See TROUBLESHOOTING.md for detailed solutions

Files

diagnose_webdav.sh - Comprehensive diagnostic script to check service binding, firewall, and configuration
check_port_forwarding.sh - Tests port accessibility and provides port forwarding checklist
TROUBLESHOOTING.md - Detailed troubleshooting guide with common issues and solutions

Most Common Issues

Service bound to localhost only - Service listens on 127.0.0.1:5006 instead of 0.0.0.0:5006
Firewall blocking port - Port 5006 not allowed in firewall rules
Router port forwarding not configured - External port 5006 not forwarded to NAS internal IP
Router firewall blocking - Router firewall blocking incoming connections

Quick Fix

The most common fix is ensuring your WebDAV service is bound to all interfaces:

Apache:

Listen 0.0.0.0:5006

Nginx:

listen 0.0.0.0:5006;

Then configure router port forwarding: External 5006 → Internal NAS IP:5006

Usage

All scripts should be run on your NAS system:

# Make scripts executable (already done)
chmod +x *.sh

# Run diagnostics
sudo ./diagnose_webdav.sh

# Check port forwarding
./check_port_forwarding.sh

1.7 KiB Raw Blame History