Hi there, I used to just click on Lidarr and it opened straight away. Now it is asking for login credentials and there is no auto-generate PW in the services section. Thanks!
22 replies
Chris wrote:
The Lidarr admin password SparkBox generates should be listed in Service Passwords, so I’m sorry it isn’t showing up there. Could you share your SparkBox version and whether this is running on a NAS, Linux, or Windows with WSL or Docker Desktop? Please don’t post the password itself.
kiltmann wrote:
Version 1.6.912, NAS - Docker, Ubuntu Server 24.04.5
Chris wrote:
Sorry—I shouldn't have assumed the Lidarr password must be there. Some installs can skip creating Lidarr's login, which leaves no generated password for Service Passwords to show. Please check whether /opt/sparkbox/state/lidarr-admin-password.txt exists on the NAS; tell me only yes or no, and don't share its contents. I've corrected what I know about this so I don't send the next person down the same path.
Chris wrote:
Sorry—I shouldn’t have sent you to check that file; I hadn’t verified it was the right place. SparkBox’s first-time Lidarr setup can skip creating the login if it can’t confirm whether the database already has a user, leaving no generated password; your check alone doesn’t tell us whether that is the case here. One check: is the prompt a small browser username/password popup, or a sign-in page branded Lidarr? Please don’t post credentials. I’ve corrected what I know so I don’t send the next person to that unverified file.
kiltmann wrote:
Its a lidarr branded sign in page.
Chris wrote:
Sorry—I sent you to check an unverified file path, and that wasn’t a reliable step. Since this is Lidarr’s own sign-in page, the browser-popup distinction doesn’t apply; we still don’t know what caused the login prompt. One check: did you ever turn on or change Lidarr’s authentication yourself, or did the prompt appear without you changing its settings? Please don’t post credentials. I’ve corrected what I know so I don’t send the next person to that unverified file.
kiltmann wrote:
I didn't turn on Lidarr's authentication myself. There was a duplicate configuration error that I had to fix that was lidarr,notifiarr.
Chris wrote:
I’m sorry—I sent you through unsupported guesses about a missing password file and first-time setup; that was wrong. You didn’t enable authentication yourself, and you found a duplicate configuration error involving Lidarr and Notifiarr. That’s important context, but I can’t verify from this alone whether fixing it changed Lidarr’s login setting. One check: after fixing that duplicate configuration error, does Lidarr still show the sign-in page? I’ve corrected what I know so this unsupported file/setup explanation isn’t repeated.
kiltmann wrote:
LIdarr started to ask for the login after I made the duplicate config change.
Chris wrote:
I’m sorry—I gave you an unsupported explanation that Lidarr’s first-time setup may have skipped creating its login. I checked the setup path: SparkBox only applies its no-login-on-your-local-network setting for a Lidarr instance with no users; it leaves an existing, user-managed instance’s authentication alone. So the timing after your configuration change matters, but it doesn’t yet tell us which setting changed. Was the duplicate-configuration fix made in SparkBox/Docker configuration, or in Lidarr’s own settings? Please don’t post configuration files or credentials. I’ve corrected what I know so I don’t repeat the unsupported seed explanation.
kiltmann wrote:
In the Sparkbox configuration .env file per Tom AI.
Chris wrote:
I'm sorry—I sent you through several unsupported guesses about the missing password file and Lidarr's first-time setup. SparkBox only applies its LAN-trust login behavior to a new Lidarr instance with no users; it leaves an existing instance's authentication settings alone, and Notifiarr's own settings are separate from Lidarr's. One check: what was the exact .env variable NAME you changed? Please share only the name, not its value or the file. I've corrected what I know so I don't repeat those unsupported explanations.
kiltmann wrote:
I changed the COMPOSEPROFILES by putting a comma between COMPOSEPROFILES=lidarr,notifiarr NOTIFIARRAPIKEY= SBLICENSEKEY= LIDARRENABLED=true
Chris wrote:
Thanks—that narrows down the timing. This was a change to SparkBox's Compose profile selection, not Lidarr's authentication settings, so I don't want to assume it directly changed the login. Was Lidarr already installed and opening without a login before this edit, or did it first start after you added it to the profile? Please don't post the rest of your .env file or any values.
kiltmann wrote:
Lidarr was already installed and opening without a login before this edit.
Chris wrote:
I’m sorry—I’ve kept sending you through guesses instead of using the key detail you gave me. Since Lidarr was already installed and opened without a login, the earlier fresh-install password-seeding explanation does not fit; changing Compose profile selection is not itself a Lidarr authentication setting. One check: after editing the profile, did you run a SparkBox action that restarted or recreated Lidarr, or did the sign-in page appear without Lidarr restarting? I’ve corrected what I know so I don’t repeat the unsupported first-install explanation.
kiltmann wrote:
I'm not certain if I restarted Sparkbox or just updated the .env file. It was several days ago.
Chris wrote:
I'm sorry—I kept asking variations of whether Lidarr restarted instead of giving you a useful next step. COMPOSEPROFILES selects which optional services start; it does not set Lidarr's authentication. SparkBox preserves an existing Lidarr configuration, and its automatic LAN no-login setting only applies to a fresh instance with no users, so I can't yet say what changed here. One read-only check: on the NAS, run sudo grep -E '<Authentication(Method|Required)' /opt/sparkbox/modules/media/config/lidarr/config.xml and share only those two output lines (not the whole file); please don't change anything yet.
kiltmann wrote:
I click on the lidarr tile in sparkbox to get to lidarr.
Chris wrote:
Thanks, that settles it: you're opening Lidarr the normal way from the dashboard, so you shouldn't be stuck at its sign-in page. Sorry this took so many rounds. Until now SparkBox had no way to give you a Lidarr password when it never saved one for your box, which is why Service Passwords had no Lidarr row. SparkBox 1.6.915, out now, adds one. On the NAS, over SSH: 1. sudo sparkbox upgrade 2. sudo sparkbox reset-password lidarr The second command sets a new password on Lidarr's own account and prints the Username and Password. It also adds a "Lidarr admin" row to Settings → Service Passwords. Lidarr restarts, so give it about a minute, then click the tile again and sign in with that pair. It only changes the password: your artists, history and settings stay as they are. Legend boxes get 1.6.915 right away. Other boxes get it within about a week, so if sudo sparkbox upgrade says you're already up to date, it hasn't reached yours yet. If the reset prints an error instead, paste just that error line here (not the password).
kiltmann wrote:
Upgrade hasn't hit my legend box yet.