Cannot add a new artist with "Monitor New Albums" set to "All" #2221

New issue

Closed

opened 2026-02-20 02:06:20 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-20 02:06:20 -05:00

Owner

Originally created by @addisonbabcock on GitHub (May 5, 2022).

Is there an existing issue for this?

I have searched the existing issues

Current Behavior

Currently Lidarr is unable to add a new artist after searching when "Monitor New Albums" is set to "All". Changing that field to any other value allows the artist to be added successfully. You can get all the way up to the "Add " button but the button press fails silently.

Expected Behavior

An artist should be able to be added regardless of the "Monitor New Albums" setting.

Steps To Reproduce

In the top left search bar, search for Test.
Attempt to add the artist with the following settings:
The artist will silently fail to add.
Verify that the Test artist was not added to Lidarr.

Environment

- OS: Windows 11 21H2
- Lidarr: 1.0.0.2567
- Docker Install: No
- Using Reverse Proxy: Yes, but it reproduces without reverse proxy.
- Browser: Edge dev 102.0.1220.1 64 bit. Reproduces in incognito and regular mode.

What branch are you running?

Nightly

Trace Logs?

No evidence of the add artist request.

2022-05-05 13:15:54.5|Trace|EventAggregator|Publishing CommandUpdatedEvent
2022-05-05 13:15:54.5|Trace|EventAggregator|CommandUpdatedEvent -> CommandController
2022-05-05 13:15:54.5|Trace|EventAggregator|CommandUpdatedEvent <- CommandController
2022-05-05 13:15:54.5|Trace|EventAggregator|Publishing CommandExecutedEvent
2022-05-05 13:15:54.5|Trace|EventAggregator|CommandExecutedEvent -> TaskManager
2022-05-05 13:15:54.5|Trace|EventAggregator|CommandExecutedEvent <- TaskManager
2022-05-05 13:15:54.5|Trace|EventAggregator|CommandExecutedEvent -> TaskController
2022-05-05 13:15:54.5|Trace|EventAggregator|CommandExecutedEvent <- TaskController
2022-05-05 13:15:54.5|Trace|CommandExecutor|DeleteLogFilesCommand <- DeleteLogFilesService [00:00:00.0086781]
2022-05-05 13:15:54.5|Trace|Http|Req: 2207 [GET] /api/v1/command (from 192.168.1.1)
2022-05-05 13:15:54.5|Trace|CommandQueueManager|Getting all commands
2022-05-05 13:15:54.5|Trace|Http|Res: 2207 [GET] /api/v1/command: 200.OK (1 ms)
2022-05-05 13:15:54.5|Debug|Api|[GET] /api/v1/command: 200.OK (1 ms)
2022-05-05 13:15:56.3|Trace|Http|Req: 2208 [GET] /api/v1/log/file (from 192.168.1.1)
2022-05-05 13:15:56.3|Trace|Http|Res: 2208 [GET] /api/v1/log/file: 200.OK (0 ms)
2022-05-05 13:15:56.3|Debug|Api|[GET] /api/v1/log/file: 200.OK (0 ms)
2022-05-05 13:16:01.6|Trace|Http|Req: 2209 [GET] /api/v1/rootFolder (from 192.168.1.1)
2022-05-05 13:16:01.6|Trace|Http|Res: 2209 [GET] /api/v1/rootFolder: 200.OK (1 ms)
2022-05-05 13:16:01.6|Debug|Api|[GET] /api/v1/rootFolder: 200.OK (1 ms)
2022-05-05 13:16:01.9|Trace|Http|Req: 2210 [GET] /api/v1/search?term=test (from 192.168.1.1)
2022-05-05 13:16:01.9|Trace|ConfigService|Using default config value for 'metadatasource' defaultValue:''
2022-05-05 13:16:01.9|Trace|HttpClient|Req: [GET] https://api.lidarr.audio/api/v0.4/search?type=all&query=test
2022-05-05 13:16:01.9|Trace|ConfigService|Using default config value for 'proxyenabled' defaultValue:'False'
2022-05-05 13:16:02.0|Trace|HttpClient|Res: [GET] https://api.lidarr.audio/api/v0.4/search?type=all&query=test: 200.OK (44338 bytes) (147 ms)
2022-05-05 13:16:02.1|Trace|Http|Res: 2210 [GET] /api/v1/search?term=test: 200.OK (189 ms)
2022-05-05 13:16:02.1|Debug|Api|[GET] /api/v1/search?term=test: 200.OK (189 ms)
2022-05-05 13:16:08.7|Trace|Http|Req: 2211 [GET] /api/v1/config/host (from 192.168.1.1)
2022-05-05 13:16:08.7|Trace|ConfigService|Using default config value for 'proxyenabled' defaultValue:'False'
2022-05-05 13:16:08.7|Trace|ConfigService|Using default config value for 'proxytype' defaultValue:'Http'
2022-05-05 13:16:08.7|Trace|ConfigService|Using default config value for 'proxyhostname' defaultValue:''
2022-05-05 13:16:08.7|Trace|ConfigService|Using default config value for 'proxyport' defaultValue:'8080'
2022-05-05 13:16:08.7|Trace|ConfigService|Using default config value for 'proxyusername' defaultValue:''
2022-05-05 13:16:08.7|Trace|ConfigService|Using default config value for 'proxypassword' defaultValue:''
2022-05-05 13:16:08.7|Trace|ConfigService|Using default config value for 'proxybypassfilter' defaultValue:''
2022-05-05 13:16:08.7|Trace|ConfigService|Using default config value for 'proxybypasslocaladdresses' defaultValue:'True'
2022-05-05 13:16:08.7|Trace|ConfigService|Using default config value for 'certificatevalidation' defaultValue:'Enabled'
2022-05-05 13:16:08.7|Trace|ConfigService|Using default config value for 'backupfolder' defaultValue:'Backups'
2022-05-05 13:16:08.7|Trace|ConfigService|Using default config value for 'backupretention' defaultValue:'28'
2022-05-05 13:16:08.7|Trace|Http|Res: 2211 [GET] /api/v1/config/host: 200.OK (4 ms)
2022-05-05 13:16:08.7|Debug|Api|[GET] /api/v1/config/host: 200.OK (4 ms)
2022-05-05 13:16:13.3|Trace|Http|Req: 2212 [PUT] /api/v1/config/host (from 192.168.1.1)
2022-05-05 13:16:13.3|Trace|EventAggregator|Publishing ConfigFileSavedEvent
2022-05-05 13:16:13.3|Trace|EventAggregator|ConfigFileSavedEvent ~> ReconfigureLogging
2022-05-05 13:16:13.3|Trace|ConfigService|Using default config value for 'autounmonitorpreviouslydownloadedtracks' defaultValue:'False'
2022-05-05 13:16:13.3|Trace|ConfigService|Using default config value for 'retention' defaultValue:'0'
2022-05-05 13:16:13.3|Trace|ServerSideNotificationService|Getting server side health notifications

Browser network logs contain the following error: