Key takeaways
- Learn the best port ranges for Synology web access, with DSM 5000 and 5001, Drive, WebDAV, Web Station, Surveillance, VPN, and reverse proxy ports explained.
Best port ranges for Synology web access start with DSM on TCP 5000 for HTTP and TCP 5001 for HTTPS, and the right choice depends on the service you need to reach. This guide lists the ports for DSM, Drive, WebDAV, Web Station, and related services, and shows how to forward only the service you use for safe access.
Quick verdict
Use TCP 5001 for secure DSM web access, use TCP 443 through a reverse proxy when you want a standard web address, and add TCP 6690 only for Synology Drive sync. Do not expose plain HTTP on TCP 5000 to the internet, and do not forward ports for services that are disabled on your NAS.
| Service | Protocol | Port range | Best for | Main limit |
|---|---|---|---|---|
| DSM HTTPS | TCP | 5001 | Secure DSM web access | Exposes the admin login page |
| DSM HTTP | TCP | 5000 | Local DSM web access | Plain HTTP is not safe in public |
| Web Station and Photo Station | TCP | 80 and 443 | Web sites and photo access | Needs a reverse proxy for safety |
| Synology Drive | TCP | 6690, plus 5000 and 5001 for web | File sync and web portal | Client sync needs 6690 alone |
| WebDAV | TCP | 5005 and 5006 | Remote file access by WebDAV | Use 5006 for HTTPS only |
| Surveillance Station | TCP | 9900 and 9901 | Camera viewing in a browser | Needs strong login protection |
| VPN Server | UDP and TCP | OpenVPN 1194 UDP, L2TP 500, 1701, 4500 UDP | Private access without DSM exposure | Needs VPN setup on the client |
| Reverse proxy on 443 | TCP | 443 to internal 5001 | Clean web address for DSM | Needs proxy setup in DSM |
How we selected
We selected ports from the official Synology service port list as shown in a detailed guide, plus a Synology port forwarding guide that lists the common ports by service. Each entry gives the service name, the protocol, and the exact port, so you can match a rule to a service instead of opening a broad range.
Port ranges by Synology service
This section works through the services one at a time, with the port, the protocol, and the practical limits for each one. Read the entry for the service you need first, then check the setup and safety sections before you change any router or firewall setting.
DSM HTTPS on TCP 5001 and the best port ranges for Synology web access
DSM uses TCP 5001 for HTTPS, and this is the port to use when DSM must be reached from outside the home network. Forward external TCP 5001 to internal TCP 5001 on the NAS local address, such as 192.168.1.50, and protect the login with strong authentication and updates.
DSM is the admin interface for the NAS, so exposing it deserves more care than a file service. The guides advise using HTTPS rather than plain HTTP, enabling two factor authentication for admin accounts, disabling unused accounts, using strong unique logins, limiting access by source address when possible, keeping DSM and packages updated, and enabling account protection and auto block features. A different external port can be used, for example external TCP 15001 forwarding to internal TCP 5001, and that change may reduce background scans, but the guides note that changing the port is not a security control by itself. If you only need occasional DSM access, QuickConnect may be enough, and if you want the safest path for admin work, a VPN is often the better design.
- Pros: secure DSM web access from outside, clear single port, and external port can differ from the internal port.
- Cons: exposes the admin login page, and needs strong login protection to stay safe.
- Use it if: you need direct DSM access from outside and can protect the login well.
- Skip it if: you only need occasional access, where QuickConnect or a VPN may be enough.
DSM HTTP on TCP 5000
DSM uses TCP 5000 for HTTP, and this port is best kept for local access inside the home network. The guides list it as the DSM web interface port and warn against exposing plain HTTP, since login details and data travel without the protection that HTTPS provides.
Inside the home network, TCP 5000 is a simple way to reach DSM from a browser, and many other DSM services also use 5000 for HTTP and 5001 for HTTPS, including File Station, Download Station, Note Station, and Moments. That shared use means a rule for 5000 can affect more than DSM alone, so keep the scope clear in your notes. If a service needs web access from outside, use the HTTPS port for that service instead of the HTTP port, and check the DSM firewall so the service is allowed only where you intend it to be allowed. Do not forward 5000 to the internet just because it works locally, since local access and public access carry very different risks.
- Pros: simple local DSM access, and shared by many DSM web services.
- Cons: plain HTTP is not safe in public, and the port is shared by several services.
- Use it if: you need DSM access only inside the home network.
- Skip it if: you need remote access, where TCP 5001 or a VPN fits better.
Web Station and Photo Station on TCP 80 and 443
Photo Station and Web Station use TCP 80 for HTTP and TCP 443 for HTTPS, and Mail Station uses the same two ports. Use 443 for secure web access, keep 80 only when a service needs it, and route web access through a reverse proxy when you can for safety.
Ports 80 and 443 are the standard web ports, so a browser can reach a site without a port number in the address, and that is why they suit Web Station sites and photo access. The same standard status also means they are scanned often, so a direct rule for 80 or 443 should point at a service that is kept updated and protected by a strong login. A reverse proxy can sit in front of DSM and other web services, take traffic on 443, and send it to the right internal service, which keeps the internal ports hidden from the public internet. Check the package settings for each service before you forward 80 or 443, since the required ports can vary with the DSM setup and the packages installed.
- Pros: standard web ports need no port number in the address, and fit Web Station and photo access well.
- Cons: standard ports are scanned often, and a direct rule needs careful protection.
- Use it if: you host a web site or photo service on the NAS and need browser access.
- Skip it if: you need only DSM or Drive access, where 5001 or 6690 fits better.
Synology Drive on TCP 6690
Synology Drive uses TCP 6690 for direct client sync, plus TCP 5000 for HTTP and TCP 5001 for HTTPS for the web portal. Forward TCP 6690 for the Drive client, and use TCP 5001 for browser access to the Drive web portal for secure use. Please read the full section before you change any setting.
Drive is a good example of why one service can need more than one port, since sync and web access use different paths. For direct remote sync, forward TCP 6690 to the NAS local address and check that the service is allowed through the DSM firewall. For web portal access, DSM typically uses HTTPS port 5001, or HTTP port 5000, and the same login protection that applies to DSM applies here. You do not need to expose DSM ports 5000 and 5001 directly to the internet just to use the Drive client, since the client can sync through 6690 alone, and that smaller scope is safer when sync is the only need.
- Pros: sync and web access have separate ports, and the client can sync through 6690 alone.
- Cons: two paths can confuse setup, and the web portal still needs DSM port protection.
- Use it if: you sync files with the Drive client or use the Drive web portal.
- Skip it if: you do not use Synology Drive at all.
WebDAV on TCP 5005 and 5006
WebDAV and CalDAV use TCP 5005 for HTTP and TCP 5006 for HTTPS, and the guides advise preferring HTTPS. Forward TCP 5006 for secure WebDAV connections, and avoid plain HTTP on TCP 5005 for remote access from outside the home. Please read the full section before you change any setting.
WebDAV lets a remote app or system reach files on the NAS through a standard file access protocol, and that use fits well when a client app supports WebDAV but does not support the Drive client. The HTTP port and the HTTPS port are a pair, just like DSM on 5000 and 5001, and the same rule applies: use the HTTPS port for any traffic that leaves the home network. Check that WebDAV is enabled in DSM before you forward anything, since a rule for a disabled service opens a port with no service behind it, and that adds risk without any benefit. Note the port pair in your setup notes, so a later change to one port does not leave the other port open by mistake.
- Pros: standard file access for many apps, and a clear HTTPS port for secure use.
- Cons: plain HTTP port must stay closed in public, and the service must be enabled first.
- Use it if: you need WebDAV file access from a remote app.
- Skip it if: you use Drive or File Station instead of WebDAV.
Surveillance Station on TCP 9900 and 9901
Surveillance Station uses TCP 9900 for HTTP and TCP 9901 for HTTPS, and these ports cover camera viewing in a browser. Use TCP 9901 for secure access, keep the camera login strong, and limit access by source address when you can for safety. Please read the full section before you change any setting.
Camera access is sensitive because it can show the inside or outside of a home, so the HTTPS port is the right choice for any remote viewing. The HTTP port is listed for local use, while the HTTPS port adds the protection that remote access needs, and the same care that applies to DSM applies here: strong unique logins, two factor authentication where the account supports it, updates for DSM and the package, and a review of logs for repeated failed login attempts. If you only view cameras inside the home, keep both ports local and do not forward them at all, since local viewing needs no public rule. If remote viewing is needed, forward only 9901 and check the DSM firewall so the service is allowed only as intended.
- Pros: clear HTTP and HTTPS pair, and remote viewing works through a browser.
- Cons: camera access is sensitive, and the HTTP port must stay local.
- Use it if: you need remote camera viewing through Surveillance Station.
- Skip it if: you view cameras only at home or do not use Surveillance Station.
VPN Server on UDP 1194 and L2TP ports
VPN Server on OpenVPN uses UDP 1194, while L2TP with IPsec uses UDP 500, 1701, and 4500, and PPTP uses TCP 1723. A VPN lets you join the home network first and then reach the NAS in private, which is often safer than exposing DSM directly to the internet.
A VPN changes the access model from opening each service to the internet to opening one VPN port and then reaching services through the private tunnel. That model fits admin access well, since DSM, File Station, and Drive can all be reached after the VPN connects, without a public rule for each one. The protocol matters here: OpenVPN needs UDP 1194, L2TP needs the three UDP ports listed, and PPTP needs TCP 1723, so check which VPN type you set up in DSM before you create a rule. The guides list the VPN as the better design for safe remote admin access, and they note that QuickConnect may be enough for occasional access, while a VPN fits regular remote work.
- Pros: one VPN port can cover many services, and admin access stays private.
- Cons: needs VPN setup on the client, and the wrong protocol will not connect.
- Use it if: you need regular remote admin access and want the safest path.
- Skip it if: you need only occasional access, where QuickConnect may be enough.
Reverse proxy on TCP 443 to internal 5001
A reverse proxy can take web traffic on TCP 443 and send it to DSM on internal TCP 5001, so the browser address stays clean and the internal DSM port stays hidden. Forward only TCP 443 on the router to the proxy, and set the proxy rule in DSM to point at the right service.
The reverse proxy is the recommended route in the guides for web access, because it ends the secure connection on the standard port, handles the web address, and hides the internal ports from the public internet. In DSM, the proxy can be set up so that a web address maps to a local service, and the router then needs only the 443 rule, rather than a separate public rule for each internal port. That smaller public surface is easier to review and easier to keep updated, and it also makes the address easier to remember than a hostname with a port number. Check the proxy setup after any DSM change, since a wrong proxy target can send traffic to the wrong service or to no service at all.
- Pros: clean web address, hidden internal ports, and only one public port to guard.
- Cons: needs proxy setup in DSM, and a wrong target breaks access.
- Use it if: you want web access through a standard address without exposing DSM ports.
- Skip it if: you use a VPN or QuickConnect and need no public web access.
Buying guide for Synology port ranges
This guide is not about buying a product, so treat it as a setup guide instead. Work in order, give the NAS a stable address first, choose one service at a time, add the router rule and the DSM firewall rule, and test from outside the home network before you move on.
Give the NAS a stable local address in the best port ranges for synology web access
Port forwarding points at an internal address, and if the NAS gets a different address later, the rule can break. Use a DHCP reservation on the router for the NAS, or assign a static address in DSM network settings, and write the address down first. Please read the full section before you change any setting.
Use a DHCP reservation on the router for the NAS, or assign a static address in DSM network settings, and use an address such as 192.168.1.50 with a gateway of 192.168.1.1 as shown in the guides. Write the address down before you create any rule, and check it again after a restart, since a changed address is one of the most common reasons a rule stops working.
Choose one service before you open anything
Decide what remote users need to reach before you open a port, since each service has its own port and its own risk. Need DSM admin access, consider a VPN or QuickConnect before forwarding DSM, and need file sync, forward only the Drive port. Please read the full section before you change any setting.
Need DSM admin access, consider a VPN or QuickConnect before forwarding DSM. Need file sync, forward only the Drive port required by the client. Need WebDAV, prefer HTTPS WebDAV, not plain HTTP WebDAV. A common mistake is forwarding many ports just in case, and that makes troubleshooting harder while it also increases the number of services exposed to the internet.
Create the router rule and the DSM firewall rule
Port forwarding is set up mainly on the router, while the DSM firewall is a separate layer that must be set up on its own when it is enabled. Log in to the router, find the forwarding section, and create a rule to the NAS local address. Please read the full section before you change any setting.
Log in to the router, find the port forwarding, NAT, virtual server, or applications section, and create a rule that forwards the public port to the NAS local address. Then check Control Panel, Security, and Firewall in DSM, and add a rule that allows the service or port you want to expose, with source address limits when you only connect from known addresses.
Use DDNS when the public address changes
Many home internet connections have dynamic public addresses, so a DDNS hostname can map a stable name to the current public address. In DSM, DDNS is commonly set up under Control Panel, External Access, and DDNS for easy access. Please read the full section before you change any setting.
In DSM, DDNS is commonly set up under Control Panel, External Access, and DDNS, and after it is set up, you can connect with a hostname instead of an address, such as a Synology DDNS name with the port at the end. If you use a different public router port, use that port in the address, and check the DDNS entry after any internet change, since an old address in the hostname will point at the wrong place.
Test from outside and fix common failures
Do not rely only on a test from inside the home Wi-Fi network, since some routers support NAT loopback and some do not, so local testing can give confusing results. Use an external port test with your public address or DDNS hostname. Please read the full section before you change any setting.
Use an external port test with your public address or DDNS hostname, and if the port is open, the router and NAS are reachable on that port. If the port is closed, check the NAS address, the router rule, the DSM firewall, the protocol, the service state, double NAT, and CGNAT, since those are the common causes listed in the guides.
FAQ
These questions cover the points that cause the most confusion, from which DSM port to use to why a rule still looks closed after it is saved. Read the answer that matches your problem before you add more ports, since the fix is often the address, the firewall, or the protocol.
What port should I forward for Synology DSM, 5000 or 5001?
DSM commonly uses TCP 5000 for HTTP and TCP 5001 for HTTPS, and if DSM must be exposed, prefer HTTPS on 5001 and protect it with strong authentication, updates, and access limits. Use 5000 only for local access inside the home. Please read the full section before you change any setting.
Use 5000 only for local access inside the home network, since plain HTTP is not safe for public admin access, and consider a VPN or QuickConnect before you expose DSM at all.
Do I need port forwarding if I use QuickConnect?
QuickConnect can help remote clients reach supported Synology services without manual router rules, and it may use a relay when a direct connection is not possible. Direct forwarding may still improve speed or be required for some services. Please read the full section before you change any setting.
QuickConnect can help remote clients reach supported Synology services without manual router rules, and it may use a relay when a direct connection is not possible. Direct port forwarding may still improve speed or be required for services that do not use QuickConnect, so use QuickConnect first for occasional access and add forwarding only when a specific service needs a direct path.
Why does my Synology port forwarding not work?
The most common reasons are a wrong NAS address, DSM firewall rules, an incorrect protocol, a disabled service, double NAT, CGNAT, or testing from inside the same network. Check each cause in order, starting with the NAS address and the router rule. Please read the full section before you change any setting.
Check each cause in order, starting with the NAS address and the router rule, then the DSM firewall, then the protocol, and then ask your provider about CGNAT if the router has no public address.
Can Synology port 5001 be opened?
It can be made safer, but it still exposes the DSM login interface, so use HTTPS, two factor authentication, updates, source address limits, and account protection. For admin work, VPN access is often a better option, since it keeps the login page off the public internet while still giving you full access after you connect to the home network.
Can I forward a different external port to Synology 5001?
Yes, many routers allow external port translation, so external TCP 15001 can forward to internal TCP 5001 on the NAS. This may reduce background scans, but it does not replace real security controls, so keep strong logins, two factor authentication, and updates in place even when the external port is not the default one.
Conclusion
Use TCP 5001 for secure DSM access, TCP 6690 for Drive sync, TCP 5006 for WebDAV, and TCP 443 through a reverse proxy for clean web access. Keep plain HTTP local, forward only the service you use, and test from outside the network before you call the setup done. Review the rules often and remove any rule you no longer need.
Write Your Review
No reviews yet. Be the first to share your experience!