Remote Libraries

Remote Libraries

Astra can index and stream music from Subsonic-compatible servers, including Navidrome, and from Jellyfin. Remote tracks join the normal Astra library alongside local files, while the audio remains on the server until played.

Open Settings > Library > Remote Music Servers.

Add a server

1. Select Add Server.
2. Enter the server URL, username, and password.
3. Select Test Connection. Astra tries the Subsonic and Jellyfin APIs and identifies the server automatically.
4. If detection fails but you know the server type, choose Subsonic / Navidrome or Jellyfin and retry.
5. Give the source a recognizable name, leave it enabled, and select Add Source.

Astra immediately starts the first sync. Passwords are protected with the operating system's secure storage and are not embedded in track URLs.

Use the base address that is reachable from this computer. Include the protocol and any nonstandard port or path, such as https://music.example.net or http://192.168.1.20:4533.

What sync does

A sync reads the server's library metadata and makes its tracks browsable in Astra. It does not download permanent audio copies. Starting playback asks the configured server for the track stream.

The source card shows its type, address, last successful sync, current progress, or most recent error. Use Sync for one source or Sync All for every configured remote source.

Astra also syncs automatically after a source is added or edited, and when a disabled source is enabled again.

Names, disabled sources, and deletion

The Source Name is Astra's label for that server. Changing it helps you distinguish libraries; it does not rename anything on the server.

Disabling a source stops it from syncing and makes its remote content unavailable without discarding the configuration. Enable it again to reconnect and start a sync.

Deleting a source gives you two choices:

• Keep Tracks: remove the connection but leave its indexed tracks as unavailable placeholders. This preserves playlist references and makes missing content visible.
• Purge Tracks: remove the connection and its synced tracks from Astra entirely.

Keeping placeholders is safer if you may reconnect the server or repair playlist entries later. Purging is cleaner when the source is permanently gone.

Playback behavior

Remote tracks need the server to be reachable when played. They use Astra's Standard playback path; native exclusive or bit-perfect output is for compatible local files.

If a remote track is unavailable, Astra keeps the entry visible rather than quietly substituting another track. Reconnect and sync the source, or use Astra's playlist repair tools where appropriate.

Troubleshooting

• Connection test fails: verify the full URL, sign-in details, server availability, and any reverse-proxy path. Try the manual server-type choice if auto-detection cannot identify it.
• Secure credential storage is unavailable: Astra cannot reach the operating system's keychain or keyring to protect the password. See Troubleshooting, including the Linux launch flag for Hyprland and similar sessions.
• It works in a browser but not Astra: confirm the URL is reachable from the Astra computer and that its TLS certificate is trusted by the operating system.
• Sync has an error: read the source card's current error, then use Sync after correcting the connection.
• New server music is missing: run Sync; Astra cannot show server changes it has not indexed yet.
• A track appears but will not play: the metadata may be cached while the server or original item is unavailable. Check the server, enable the source, and sync again.
• Two servers contain the same recording: Astra treats them as separate source items. Their shared tags do not make one a fallback for the other.