# After a WebDAV credential change in ManYue: recheck the same comic library and actual reading

Language: en
Canonical: [After a WebDAV credential change in ManYue: recheck the same comic library and actual reading](<https://allluckly.cn/en/guides/manyue-webdav-credential-changed-same-library-recheck/>)
中文：[中文 HTML](<https://allluckly.cn/guides/manyue-webdav-credential-changed-same-library-recheck/>)
English: [English HTML](<https://allluckly.cn/en/guides/manyue-webdav-credential-changed-same-library-recheck/>)
Published: 2026-11-20T00:00:00+08:00
Modified: 2026-11-20T11:50:49+08:00
Author: Bison

When a credential has already changed, preserve local copies and check account, directory, authentication entry and comic pages in layers.

English translation of the [Chinese original](<https://allluckly.cn/guides/manyue-webdav-credential-changed-same-library-recheck/>), translated on 2026-11-20. Original publication dates, attribution, code and version notes are retained.

When a credential has already changed, preserve local copies and check account, directory, authentication entry and comic pages in layers.

## Preserve the readable copy and connection identity

This exercise checks a private WebDAV comic library after the user has already changed or revoked its access credential; it does not require changing a password for a test. Record the old connection name, service type and redacted host and comic-directory identity. Choose one short authorized comic and note its title, chapter and recognizable first and last pages. Preserve any offline copy, favorites and progress, and confirm a recoverable original in your own storage. Do not record actual passwords, tokens or full private URLs, or delete the existing connection before diagnosis.

## Identify which credential actually changed

Ask yourself or the server maintainer whether the changed item was the main account password, an app-specific password, a share password or another authorization; these need not change together. For example, Nextcloud documents separately revocable app passwords for third-party WebDAV clients, which does not imply every WebDAV service works alike. Record change time, account identity and whether a valid new access method has been obtained. Do not send old passwords, verification codes or unredacted error screenshots. Without usable new credentials, leave subsequent connection checks pending.

## Check the same account and directory on the server

Through the server’s normal management or file entry and an authorized access method, verify whether the actual account can see the intended comic directory; record the sample work and directory identity. Web login, WebDAV client login and share links may use different authorizations. Successful web access establishes that web session only, not a valid WebDAV credential. If the provider specifies an app password, check its instructions and the authorization already obtained rather than using a website password for every service. If the server itself is inaccessible, retain the message instead of repeatedly guessing passwords in ManYue.

## Identify the ManYue service and address

Return to the existing ManYue connection and check that it is the WebDAV comic-file entry, not the WebDAV data-sync destination, and that host, port, subpath and intended account match the previous step. Even on the same server these are different data purposes; opening a comic does not require clearing the sync directory. If both address and credential changed, record them separately and obtain the current WebDAV entry from the provider rather than inferring it from a browser’s comic-detail page. Mark any setting the interface does not show as unconfirmed.

## Use the obtained credential only through an actual entry

If the current connection interface actually offers editing authentication or signing in again, follow its prompt on-device using the valid credential you are authorized to use. Do not capture, copy or share the password. If no editing entry is evident, a connection scope must be chosen first or the prompt’s effect is unclear, stop and consult the current app instructions or maintainer; do not assume deletion and recreation is the only route. Record actual feedback and time. Closing a dialog, clicking a button or an existing web session alone does not prove ManYue reconnected.

## Verify directory, chapter and actual pages

Return to the same WebDAV connection and check the intended directory, sample comic, chapter and first and last pages in order. Verify work identity and actual content rather than just the connection name or cover. If needed, separately check download outcome and an existing local offline copy: acquiring a file and reading remotely are different actions. If a directory is visible but a page fails, retain the chapter and failure stage and investigate file-read permissions, network or service feedback. Do not simultaneously switch accounts, comics and networks.

## Identify remaining failure layers and preserve records

If authentication still fails, check service availability, the chosen account and credential type, then assess authorization using actual feedback. Change one condition and retry the same comic. If the service explicitly reports a temporary account lock or requires additional verification, follow the provider’s instructions and wait rather than repeatedly retrying. If no edit entry is visible, do not invent its name or reinstall or erase data to force a quick result. If network, service and login work but a directory is empty, compare the same account’s server-side view; an administrator’s full library does not establish the same permissions for this account. A report needs only a redacted address structure, service type, time and failure stage.

## Return and deliver layered results

Leave the reader and return to the same connection, checking whether the sample directory and chapter can be read again. Then verify the earlier local copy and important reading records are still locatable. Deliver the before/after service identity, credential type, server-side scope, ManYue directory and page results and pending items, without retaining or sharing actual credentials. If no new credential was obtained, the interface entry is unclear or reopening was not performed, mark that result untested. One successful comic covers this account, directory, file and device, not every server or future credential change.

## Related guides and sources

[Connect a WebDAV comic library](<https://allluckly.cn/en/guides/manyue-webdav-library/>); [Check server permissions](<https://allluckly.cn/en/guides/manyue-server-permission-matrix/>).

Checked on 20 November 2026: [Apple lookup](<https://itunes.apple.com/lookup?id=6753895889&country=cn&entity=software>) lists ManYue 2.0.6 and iOS / iPadOS 15.0 or later; the [App Store](<https://apps.apple.com/cn/app/id6753895889>) describes private WebDAV libraries. Method: [Nextcloud WebDAV documentation](<https://docs.nextcloud.com/server/stable/user_manual/en/files/access_webdav.html>) applies only to that service. No device login, credential change or private-server test is claimed.

