The site seeded with tor=always isn't downloded to another peer with tor=always

I created a blog on one Arch linux with tor=always, and no open 15441 port. Another instance of ZN running on another similar Arch setup always fails to download content.json.

The original instance also shows this message:

```
Your network connection is restricted. Please, open 15441 port
on your router to make your site accessible for everyone.
```

I think this message is completely wrong for tor=always because incoming connections should come from tor HS, and not from the port open on the router. It should work on tor.

The debug log on the downloading peer shows a timeout:

```
[18:55:03] WorkerManager:1HDT1a..wn9Z Timeout, Skipping: {'optional_hash_id': None, 'site': , 'done': False, 'size': 0, 'inner_path': 'content.json', 'peers': None, 'time_started': 1465264443.315883, 'time_action': None, 'priority': 9999, 'failed': [, , ], 'workers_num': 0, 'time_added': 1465264443.303915, 'evt': }
[19:04:34] WorkerManager:1HDT1a..wn9Z Timeout, Skipping: {'optional_hash_id': None, 'site': , 'done': False, 'size': 0, 'inner_path': 'content.json', 'peers': None, 'time_started': 1465265000.060174, 'time_action': None, 'priority': 9999, 'failed': [, ], 'workers_num': 0, 'time_added': 1465265000.058588, 'evt': }
[19:05:35] WorkerManager:1HDT1a..wn9Z Timeout, Skipping: {'optional_hash_id': None, 'site': , 'done': False, 'size': 0, 'inner_path': 'content.json', 'peers': None, 'time_started': 1465265074.553957, 'time_action': None, 'priority': 9999, 'failed': [, ], 'workers_num': 0, 'time_added': 1465265074.541852, 'evt': }
...
out:[19:23:51] FileServer FileRequest: Conn#92 ill4ijostvqk4h7e.onion [v2] pex 1HDT1a{...}wn9Z None
out:[19:23:56] WorkerManager:1HDT1a..wn9Z Timeout, Skipping: {'optional_hash_id': None, 'site': , 'done': False, 'size': 0, 'inner_path': 'content.json', 'peers': None, 'time_started': 1465266175.363997, 'time_action': None, 'priority': 9999, 'failed': [, , ], 'workers_num': 0, 'time_added': 1465266175.36015, 'evt': }
```

Is ZN supposed to succeed seeing site hosted on tor-only peer from another tor-only peer? I think this should work, but it doesn't work for me.

When the site is seeded on tor-only peer it can only be visible to the clearnet ZN peers through the peers that are in both tor and clearnet.

Start by reproducing the transfer between the two tor=always peers and compare the downloader's timeout entries with the seeder's FileServer request for content.json. Trace the peer-connection path involved in those log entries and verify whether the site can be fetched through the onion peers without opening port 15441. Done means tor-only peers exchange content.json successfully and the restricted-network message is accurate for this setup.

由索引模型根据 Issue 内容生成。