Book Isle after a NAS address or folder change: verify the new route

A router change, NAS move or directory reorganisation can leave familiar shelf titles linked to an obsolete location. Preserve old connection information, test the new route and read a sample before checking records. Book-file access and WebDAV reading-data sync may use different paths; repairing one does not automatically restore the other.

Record what the old connection meant

Before editing, record service type, host, port, share or base path and account name. Keep passwords in your existing secure system rather than public screenshots. Specify whether only a local address changed or whether protocol, domain, folders and accounts changed too. A clear scope makes verification easier.

Retain titles, important chapters, readable note exports and original files. An invalid address does not erase the value of old records, so shelf deletion is unnecessary as a first step. Preserve old configuration where possible and use your installed editing controls without assuming automatic bulk migration exists.

Verify the new server location

On a computer or management tool, establish that the new service works and books occupy the expected paths. SMB share names need not equal disk folder names, and a WebDAV base path may add another level. Moving a book does not make its old URL follow the same filename automatically.

For domains, certificates and reverse proxies, compare new and old access routes. Local addresses and public domains have different reachability conditions; do not mix protocols and ports. Establish one reliable route on the same network before testing remote access, so routing and app configuration are not diagnosed together.

Test the connection with a small sample

Edit or add the connection with the available controls and choose a simple small directory. Browse to a known book and verify edition and location before broad library operations. A successful connection establishes initial reachability; the actual reading subdirectory still needs checking.

Open or download a small EPUB and visit middle and end. If listing works but download fails, check read permissions, acquisition address and file. Use the same account for comparisons: a computer administrator's access does not establish what Book Isle's ordinary account can read.

Check the actual source behind shelf entries

Return to frequently read books once the new route works. Local copies may remain readable, while entries relying on old remote paths may need retrieval through the workflow your version supports. Mixed success does not immediately imply library disorder; separate local files from remote dependencies.

For duplicates after reimport, compare editions and old records before deleting entries for tidiness. Find an old chapter and quotation in the new file. Matching titles do not guarantee identical relationships, particularly when server migration also regenerated metadata or reorganised files.

Verify the reading-data directory separately

Inspect WebDAV sync settings for any host or directory affected by the move. A book folder and a sync folder have different purposes; do not substitute an entire ebook directory as the new sync target. Record the old destination and known valid records before using your existing migration process.

Create an unimportant test note on the main device, finish a clear sync and check it on the other device. A success message needs actual record verification. For a freshly moved destination, retain important records from both devices and establish the baseline before allowing simultaneous uploads to confuse old and new data.

Repeat key checks on the networks you use

If you need access at home and away, test both actual network conditions. Local success does not promise external reachability, and remote success does not prepare a local copy. Use the same sample for browsing, downloading and reading and identify the failing stage rather than comparing only speed or signal.

If home-only access meets your needs, keep it and download books before leaving, then verify offline. An address migration does not require a new complex remote setup. Book Isle cannot automatically complete routing, firewall or domain configuration merely because its saved server address changed.

Retire the old configuration after checking

Once catalogue, files, reading and any needed sync pass, organise the old connection. Read removal prompts and distinguish connection deletion, local-file deletion and reading-record deletion. If unclear, preserve old information and stop writing to the old destination rather than rushing to clear it.

Update your library inventory with the new address, directory, migration date and tested sample, without passwords. It should distinguish book access from data sync for the next device or network change. The goal is a clear usable access relationship, beyond a new connection display name.

Related tutorials and sources

Continue checking your files with local ebook basics and Book Isle multiple-format management. For reading records, see notes and data export.

Checked on October 26, 2026 using Apple's public version information: Book Isle 1.1.3 requires iOS / iPadOS 15.6 or later. Feature scope follows the official App Store listing. This article describes a workflow and checks; it does not claim step-by-step testing on a physical device or private server. Follow the controls in your installed version.