功能說明
Step 1: run the source check-up
- Open Settings › Manage Sources.
- Touch and hold the problem source and choose Source Diagnostics, or swipe left and tap Check. On Mac, choose Source Diagnostics from the source's menu.
- Wait for "Checking connection and scan readiness..." to finish, then review items under Checks such as Configuration, Credentials and Connection.
There are three possible results: "Ready to scan", "Ready with warnings" and "Needs attention". After fixing something, tap Run Again to confirm.
Fix by check-up message
| Check-up message | Meaning | What to do |
|---|---|---|
| Network unreachable | Primuse could not reach the source over the current network. | Make sure the phone and source are on the same LAN or VPN, and confirm the host and port. |
| Connection timeout | The source did not respond in time. | Check Wi-Fi/VPN, server wake state, port forwarding, and whether the NAS is sleeping. |
| Certificate problem | The HTTPS certificate could not be trusted. | Verify the certificate, then trust it only if it belongs to your server. |
| Authentication problem | The server rejected the current credential. | Re-enter the password, API key, or token. If the source uses 2FA, reconnect it first. |
| Cloud authorization expired | The cloud drive token is missing or expired. | Reconnect this cloud drive and authorize Primuse again. |
| Path problem | The selected path cannot be opened. | Re-select the folder or confirm the account has permission to read it. |
| Provider rate limit | The provider is temporarily limiting requests. | Wait a few minutes, then retry, and avoid repeated scans or playback attempts in a short period. |
| Source response error | The source returned an unreadable response. | Check the server status and try again. If the problem persists, export logs from Diagnostic Reports. |
Address and network
If the connection fails while adding or editing a source, Primuse shows "Connection Failed" with the address it actually tried, plus hints:
- This is a local network address — it only works while you are on the same network.
- With a domain name the port is usually 443 or 80 — the service’s own port is often only open on the local network.
- This address goes over the Internet without encryption, which many servers refuse.
- This goes through the vendor’s relay — check that the device is online and remote access is turned on.
Tap Change Address to change it directly. The first time you connect to a device on your local network, the system asks for Local Network permission: Primuse needs local network access to discover and connect to your NAS devices, media servers, and other music sources. If you denied it before, turn Local Network back on for Primuse in the system's privacy settings.
HTTPS certificates
If the server uses a self-signed certificate or one that doesn't match the host name, you are asked to confirm the certificate when connecting. After you confirm, Primuse pins that certificate; if it changes later, you see "Server Certificate Changed": The server certificate differs from the one you previously confirmed. Verify the details before updating trust.
Trusted items are managed in Settings › Trusted Domains (in the Security group): Manually added endpoints still require certificate review on first connection. Confirmed entries are pinned to a certificate fingerprint and prompt again after a change. Swipe to remove.
HTTP on public addresses
Local network addresses can use HTTP directly. A public host using HTTP shows "Allow an Insecure HTTP Connection?", and you must tap Allow HTTP Anyway to connect. If it hasn't been allowed, you see: The host “…” has not been allowed to use public HTTP. Use HTTPS or explicitly allow this host in Security settings. On iPhone and iPad, allowed hosts are listed in Trusted Domains › Hosts Allowed to Use HTTP: Only these public hosts may use cleartext HTTP. The connection is not encrypted, so account credentials, sessions, and media may be intercepted. Prefer HTTPS.
Sign-in fails
If the server rejects the password during a background sync, "Sign-in failed" appears with "Login failed. Check credentials or NAS status.". Tap Re-enter password to enter it again. SMB sources may also show "SMB: Wrong username or password". For servers with two-step verification (such as Synology), connect again once.
Connected, but no songs
- The check-up says the folder is empty: This may be an empty folder, a filtered view, or a permission-limited account.
- For SMB and NFS, set the share or export path first (Connect once and choose the shared folder to make scans faster and more reliable.).
- A scan may pause in the background and continues when you return to the app. See Scan, refresh and organize your library.
Still not solved
Send diagnostics as described in Collect and send diagnostics to the author, and include the source type, whether you connect over the local network or the internet, and when the problem happened.
Related articles
- Add and manage music sources: supported types, where to add them, and everyday actions
- Connect a NAS or network share: Synology, QNAP, SMB, WebDAV, FTP, SFTP, NFS, S3, UPnP
- Connect a media server: Jellyfin, Emby, Plex, Subsonic/Navidrome, Audiobookshelf, fnOS Music and more
- Connect a cloud drive: Baidu Netdisk, Aliyun Drive, Google Drive, OneDrive, Dropbox, 123pan, Guangya, pCloud, Drime, InfiniCLOUD
問題原因
A connection usually fails for one of these reasons: the device and server aren't on the same network, the address or port is wrong, the HTTPS certificate can't be verified, a public address uses unencrypted HTTP, the password or token has expired, the cloud drive authorization has expired, the selected folder can't be read, or the provider is temporarily limiting requests.