# ManYue HTTPS library connections: distinguish domain and numeric-IP certificate identity

Language: en
Canonical: [ManYue HTTPS library connections: distinguish domain and numeric-IP certificate identity](<https://allluckly.cn/en/guides/manyue-https-domain-ip-certificate-identity/>)
中文：[中文 HTML](<https://allluckly.cn/guides/manyue-https-domain-ip-certificate-identity/>)
English: [English HTML](<https://allluckly.cn/en/guides/manyue-https-domain-ip-certificate-identity/>)
Published: 2026-11-20T00:00:00+08:00
Modified: 2026-11-20T12:41:29+08:00
Author: Bison

Check domain, IP and certificate identity with an administrator-confirmed secure address, then verify the intended library and comic.

English translation of the [Chinese original](<https://allluckly.cn/guides/manyue-https-domain-ip-certificate-identity/>), translated on 2026-11-20. Original publication dates, attribution, code and version notes are retained.

Check domain, IP and certificate identity with an administrator-confirmed secure address, then verify the intended library and comic.

## Prepare a known library and its trusted address

Prepare an HTTPS comic service you are authorized to use, one recognizable comic, and the complete domain URL supplied by its administrator. Record service type, port, original path and any error, retaining the settings and a local original; redact passwords from screenshots. This exercise compares domain and numeric-IP identity for the same service. It does not require buying a service or installing certificates. If no administrator-confirmed secure URL is available, stop after collecting information rather than guessing addresses.

## Separate the changing URL components

Split the administrator’s URL into scheme, host, port and path; https://comics.example.test:8443/library/ is an illustration, not an address to connect to. Separately note the failing numeric-IP form, preserving its port and path. Do not publish household IP addresses, accounts or tokens. Even if a domain resolves to the same machine, virtual hosting, a proxy or certificate configuration can lead to a different service configuration. Similar page colors do not prove the libraries are identical.

## Confirm the service at its trusted domain

Enter the administrator-supplied domain URL in a browser on the same device. Confirm that no certificate warning appears and, with normal authorization, check whether the intended service is reached. If there is a warning, stop, record it, and neither bypass the warning nor submit credentials. On a normal page, verify service identity, path and an authorized comic. A login screen without a successful sign-in proves only that the screen was reachable. Browser success describes that browser and connection, not guaranteed app behavior.

## Compare certificate identity without changing it

If the administrator can safely supply certificate details, or the browser actually displays them, inspect DNS-name and IP-address entries in subjectAltName, plus validity and issuer. Do not publish certificate serial numbers, internal hosts or full screenshots. RFC 9525 specifies exact matching between an IP reference identity and an IP-address entry; a domain-only certificate should not be assumed valid for the server’s numeric address. A name match alone is not complete trust: chain, validity and client policy matter too. For example, a certificate listing only comics.example.test does not automatically match another alias or a numeric address; inspect the actual identity type and applicable rules. If alternative names are not shown, do not infer them from the certificate title: ask the administrator for verifiable details. What a tool displays may be incomplete, so “not visible” does not prove the server has no such entry. If only a warning is shown and details are unavailable, record its wording and time for the administrator; do not install an unknown root certificate. Continue after the administrator confirms the address and trust chain; otherwise mark the result untested.

## Use the confirmed complete URL in ManYue

Choose the server connection type actually available in ManYue and enter the confirmed HTTPS domain, port and original path as supplied by the administrator. If this version lacks the entry or requires an entitlement, record that state without inventing controls. Keep account and directory constant, authenticate normally and observe save, sign-in and catalog feedback. Preserve a useful existing connection or screenshot before editing; do not clear data for a test. Record the exact failure stage and message rather than assigning every error to the certificate.

## Verify the library and selected comic

After connecting, confirm library name, target folder and cover, then open recognizable first, middle and last pages. A visible listing does not prove image retrieval; if only the catalog appears, record catalog success and page failure separately. Leave the reader and locate the work again through the same entry, excluding a similarly named library. This checks the selected work and observed pages only, not every chapter or offline availability.

## Narrow the difference on failure

If domain and IP results differ, first compare scheme, port, path, network, account and actual service identity. DNS, proxy rules and certificates can all cause differences; one comparison cannot establish a cause. For a name or expiry problem ask the server administrator to repair it and provide the correct secure address, rather than disabling verification, switching to plaintext or blindly trusting a certificate. If the browser works but the app fails, record times, versions and exact messages; check service type and app entry, and share redacted evidence if needed.

## Keep a reproducible outcome

Keep redacted service type, URL components, whether certificate identity could be inspected, browser outcome, ManYue connection stage and page results. Mark unperformed steps untested and unavailable certificate details unknown. Check that the existing connection and local comic remain locatable and restore temporary settings. A successful secure domain works under the observed conditions; it does not prove the numeric IP should work or every certificate issue is solved. For further diagnosis contact the administrator without sharing passwords, tokens or private comics.

## Related guides and sources

[HTTPS and proxy subpaths](<https://allluckly.cn/en/guides/manyue-https-proxy-base-path/>); [Server connection troubleshooting](<https://allluckly.cn/en/guides/manyue-server-connection-troubleshooting/>).

Checked 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 server support. Identity matching reference: [RFC 9525](<https://www.rfc-editor.org/rfc/rfc9525.html>). Actual app entries depend on the installed version. No device or private-server test is claimed.

