# ManYue at home and away: distinguish routes to the same library

Language: en
Canonical: [ManYue at home and away: distinguish routes to the same library](<https://allluckly.cn/en/guides/manyue-home-away-endpoints/>)
中文：[中文 HTML](<https://allluckly.cn/guides/manyue-home-away-endpoints/>)
English: [English HTML](<https://allluckly.cn/en/guides/manyue-home-away-endpoints/>)
Published: 2026-10-26T00:00:00+08:00
Modified: 2026-10-26T11:37:28+08:00
Author: Bison

Verify home and existing remote access routes separately, label connections, and compare accounts, editions and reading records while keeping offline copies distinct.

English translation of the [Chinese original](<https://allluckly.cn/guides/manyue-home-away-endpoints/>), translated on 2026-10-26. Original publication dates, attribution, code and version notes are retained.

A home NAS address and an existing remote endpoint can lead to the same files through different services or accounts. Identical covers do not establish identical entry identities or records. Label and test the routes you already use, keeping network access separate from offline copies.

## List the routes that already exist

Record the home network, connection type and library name, then the remote route already configured by you or the maintainer. Keep actual addresses private. If no remote service exists, downloaded comics can be the travel option; do not create router exposure merely to follow this exercise. This test verifies existing routes rather than designing a new deployment.

## Choose one reference book at home

On the home network, use your normal reader account to inspect a short known book at several positions. Record its source, edition, coverage and current scene, plus download permission if relevant. Resolve instability at home before comparing remote access; a known baseline makes it possible to identify what changes with the network.

## Name connections by their purpose

Use short descriptive names such as home library and remote library where the interface permits. Record privately whether they reach the same service. Names improve recognition but do not merge identities or records. If a particular duplicate-connection arrangement is unsupported, use the available structure and your inventory rather than repeatedly adding connections.

## Verify the route after changing networks

Away from home, verify the intended network or existing access tunnel before opening the remote endpoint. Old covers can remain visible even when a local address is unreachable. Inspect an appropriate uncached position or a fresh chapter request without clearing all cache. If it fails, check remote conditions before changing the known-working home connection.

## Confirm whether both routes reach the same edition

Compare chapter count, edition and a matching scene to rule out a remote copy of an older library. The same file through another service or account may still have a different identity. Verify the actual resume scene rather than a similar percentage. If records are separate, designate a main reading identity and retain manual anchors for the fallback route.

## Treat offline copies as a separate option

For unreliable connectivity, complete an authorised download and inspect it offline through a local entry. Successful remote browsing does not place every file on the device. Record which edition is fully local and its reading anchor. Keep a verified travel copy until the trip is over and postpone cleanup until original backups and deletion scope are understood.

## Check records again on returning home

Back home, open the normal reading identity and compare the travel scene. Let your established sync process complete before inspecting records. If an old position appears, verify entry identity first and sync state next. Retain results for home, away and return; they distinguish reachability, separate identities and delayed records instead of calling every difference lost progress.

## Questions and completion criteria

Why can the same artwork have two progress records? Accounts or services may identify it differently. Does an unreachable home address mean the files vanished? Check the route first. Finish with labelled, tested existing routes, a chosen reading identity, independently verified offline copies and a correct return scene. A reliable local-only travel plan is also complete.

## Related guides and sources

[ManYue multiple servers: distinguish matching titles and personal library scope](<https://allluckly.cn/en/guides/manyue-server-library-scope/>); [Prepare ManYue for offline reading: check the whole comic before leaving](<https://allluckly.cn/en/guides/manyue-offline-preflight/>).

Checked on October 26, 2026: ManYue public version 2.0.3, requiring iOS / iPadOS 15.0 or later. Based on the [official App Store description](<https://apps.apple.com/cn/app/id6753895889>) and [Apple public version lookup](<https://itunes.apple.com/lookup?id=6753895889&country=cn>). This guide describes a checking workflow; controls and permissions depend on the installed version. It does not claim that every step was tested on a physical device.