Skip to content

Lidarr Connect Lidarr

Bring album release dates, monitored artist context, and integration health into JellyGlance.

Before you begin

  • Finish Lidarr's own setup and confirm it opens in a browser.
  • Sign in to JellyGlance with permission to manage integrations.
  • Have the API key under Lidarr Settings → General → Security. Reveal advanced settings if that section is hidden.

Choose the connection URL

Use the service name and its internal port:

http://lidarr:8686

Both containers must be on the same Docker network. Replace the service name if yours differs. 8686 is Lidarr's default port.

Use the server's LAN IP and the published service port:

http://192.168.1.50:8686

Replace the example IP and port with your deployment's values. The JellyGlance container must be able to reach them.

Use the service's configured HTTPS base URL, including any path prefix:

https://lidarr.example.com

A proxy login page can block API calls. Prefer a reachable internal address or a deliberate API access policy.

Do not paste a browser page such as /web/ or a URL fragment. Do not append an API endpoint to the base URL.

Configure JellyGlance

  1. Open Settings → Integrations → Arr Apps. Enable Lidarr.
  2. Enter the base URL and API key.
  3. Run the connection test. A successful test reports the Lidarr version.
  4. Save the integration.
  5. Run Arr Calendar Sync under Settings → Tasks when you want a fresh pull.

Verify it works

Open Calendar and compare an upcoming album with Lidarr. A successful connection can still produce an empty calendar when nothing is monitored or releasing. Confirm the artist is configured in Lidarr before troubleshooting JellyGlance.

JellyGlance reads service data. Quality profiles, root folders, indexers, and download clients stay in Lidarr. Servarr documents API keys under General → Security.

Common connection problems

Symptom Next check
Connection refused Correct host and port; Lidarr running; container networking.
Name cannot be resolved Service name exists on a shared network; use a reachable LAN address otherwise.
401 or 403 Correct API key, no surrounding spaces, and no proxy authentication interception.
404 Base URL and any configured URL prefix; remove extra UI/API paths.
Certificate failure Correct HTTPS hostname and a certificate trusted by the backend.
Test succeeds but the calendar is empty Saved and enabled integration, completed Arr Calendar Sync, and monitored releases in Lidarr.

See troubleshooting for log collection and task reference for refresh behaviour.