Cannot access outside my home network

[Mit Majia]

Seafile works great inside my home network. But when I try to connect to the server from outside, it fails.

Here is the configuration at ccnet.conf
SERVICE_URL = http://192.168.1.59:15002
[Network]
PORT = 15001
[Client]
PORT = 15005

This is the configuration at seafile.conf
[database]
type=sqlite
[network]
port=15003
[httpserver]
port=15004

I manually edited this two configure files. I opened the port forward at my router. It works great at home. Outside, I use the dynamic DNS name by DynDNS. I can perfectly log in the seahub web interface.But I cannot download library (stuck in connecting to server...) and cannot upload files (stuck in "Uploaded: Fetching...."). I checked in the ccnet.log at seafile server inside my home network. I did not see records for this two operations, download library and upload files.

Thanks.     

[Mit Majia]

I think I know where the problem is. But I cannot solve it.
When I tried to upload files in the seahub web, I see it tries to connect to my seafile server at the home network IP, i.e. 192.168.1.x. I logged in by using DynDNS name, but the upload still tries to use the LAN ip. Can anybody help to solve it?

[Mit Majia]

I now changed SERVICE_URL = http://192.168.1.59:15002 to SERVICE_URL = http://DynDNSname:15002.   It now works outside my homework. But my seafile client inside home network  also attempts to connect to the sever at DynDNSname, it fails. Is there a way that it works both inside and outside the home network?

On Thursday, July 11, 2013 10:07:38 AM UTC-5, Mit Majia wrote:

[Ben Gray]

I'm trying to find a way around the exact same issue.  One solution I know will work is to get a router that does NAT reflection.  What that'll do is when you're on your LAN and access http://DynDNSname:15002 you'll be reflected back at 192.168.1.x.  Barring that solution I don't know of a way around this issue.  I'll keep looking and will try to remember to report back if I find a solution.

[Mit Majia]

Thanks. I did some research by google search. I figured out the solution. That is to modify your hosts file and map DynDNSname to intranet ip address. It seems the better solution is to set a DNS server, but that sounds like too complicated.

Seafile is really cool system. I like it. I just run it, and hope it can be stable. I will wait to see.

[michif100]

Could you post your /etc/hosts and your ccnet.conf?

I was wondering if I did everything right.

At the moment my ccnet.conf contains the LAN adress 192.168.x.x:8000

Do I still nedd to change this to my.example.com:8000 ?

I am not sure what to add to my hosts file.

Is it like:

 192.168.x.x     my.example.com

Thanks for your help.

[cristhian...@gmail.com]

It is not hard to create a DNS server. It just takes a little patience. Please Install BIND 9 and modify four text files. Nothing difficult is not it? Edit the hosts file brings with it some problems, mainly if it is a laptop that needs to synchronize both inside and outside the network. With a DNS Server you have the ultimate solution. Not only that. This is the ultimate solution for software that has this problem. Clearly with a router that has NAT Reflection thing should look similar but faster. Obviously you would lose the ability to make all the more advanced configurations that sometimes come in handy.

[Andre Aßling]

You need to add this to your local hosts file on your pc, not at the the server:

local server ip

192.168.1.1    your.dyndns.com

At the ccnet.conf you have to change it to your your.dyndns.com:8000 .