Deploy Seafile behind NAT¶
A lot of people want to deploy a seafile server in their LAN, and access it from the WAN.
To achieve this, you need:
- A router which supports port forwarding
- Use a dynamic DNS Service
- Modify your seafile server configuration
Table of Contents¶
- Setup the server
- Setup port forwarding in your router
- Use a dynamic dns serivce
- Modify your seafile configuration
Setup the server¶
First, you should follow the guide on Download and Setup Seafile Server to setup your Seafile server.
Before you continue, make sure:
- You can visit your seahub website
- You can download/sync a library through your seafile client
Setup Port Forwarding in Your Router¶
Ensure Your Router Supports Port Forwarding¶
First, ensure your router supports port forwarding.
Login to the web adminstration page of your router. If you don't know how to do this, you should find the instructions on the manual of the router. If you have no maunal, just google "XXX router administration page" where
XXXis your router's brand.
Navigate around in the adminstration page, and check if there is a tag which contains a word such as "forward", "advanced". If your router supports it, chances are that you can find the port forwarding related settings there.
Setup Port Forwarding Rules¶
Seafile server is composed of several components. If you deployed Seafile behind Apache/Nginx you need to configure port forward for all the components listed below.
- If you're not using the default ports, you should adjust the table according to your own customiztion.
How to test if your port forwarding is working¶
After you have set the port forwarding rules on your router, you can check whether it works by:
- Open a command line prompt
- Get your WAN IP. A convenient way to get your WAN ip is to visit
http://who.is, which would show you your WAN IP.
- Try to connect your Seafile server
telnet <Your WAN IP> 80
If your port forwarding is working, the command above should succeed. Otherwise, you may get a message saying something like connection refused or connection timeout.
If your port forwarding is not working, the reasons may be:
- You have configured a wrong port forwarding
- Your router may need a restart
- You network may be down
ccnet.conf is used to generate the download/upload link for files when you browse files online. Set it using your WAN IP.
SERVICE_URL = https://<Your WAN IP>
Most routers support NAT loopback. When your access Seafile web from intranet, file download/upload still works even when external IP is used.
Use a Dynamic DNS Serivce¶
Why use a Dynamic DNS(DDNS) Service?¶
Having done all the steps above, you should be able to visit your seahub server outside your LAN by your WAN IP. But for most people, the WAN IP address is likey to change regularly by their ISP(Internet Serice Provider), which makes this approach impratical.
You can use a dynamic DNS(DDNS) Service to overcome this problem. By using a dynamic DNS service, you can visit your seahub by domain name (instead of by IP), and the domain name will always be mapped to your WAN IP address, even if it changes regularly.
There are a dozen of dynmaic DNS service providers on the internet. If you don't know what service to choose We recommend using www.noip.com since it performs well in our testing.
The detailed process is beyond the scope of this wiki. But basically, you should:
- Choose a DDNS service provider
- Register an account on the DDNS service provider's website
- Download a client from your DDNS service provider to keep your domain name always mapped to your WAN IP
Modify your seafile configuration¶
After you have setup your DDNS service, you need to modify the
SERVICE_URL = https://<Your dynamic DNS domain>
Restart your seafile server after this.