Plex Media Server is hammering lyricfind.plex.tv

Hi all,

My PMS is hammering lyricfind.plex.tv since I moved it from a FreeNas plugin to a manual jail install.

In my Pi-hole admin console I can see Plex did almost 40k DNS requests to this specific domain for the last 24 hours, and this is going on for days now:

My music library contains less than 5k songs. I already did a ‘refresh all metadata’ on the music library and rebooted the system where it is installed on multiple times.

Can somebody explain to me what is going on? I can provide logs if needed, please let me know which one.

Best regards, nMad

Anyone? :smile:

These requests to lyricfind.plex.tv are still going on, exact every 20 minutes ca. 400 queries.
For example: 8 AM: ca. 400 queries, 8:20 AM: ca. 400 queries, 8:40 AM: ca. 400 queries, and so on…

@“MovieFan.Plex” @gbooker02 @timwoj @“Chris C” @StSimm1 @chrisallen @drzoidberg33

Can someone please respond?

How often do you let your libraries update? Every 20 minutes?

@OttoKerner said:
How often do you let your libraries update? Every 20 minutes?

Thanks for your reply OttoKerner.

Library update interval is set to 15 minutes. This is because ‘Update my library automatically’ (on folder change) is not working. I believe this has something to do with FreeNAS / FreeBSD not supporting this functionality.

Consider changing that to a much longer interval.

I’m experiencing the same thing @Tommeh is experiencing, 30,000 attempts to get to lyricfind.plex.tv between 0400 and 0730. lyricfind.plex.tv has been blacklisted on my pi-hole devices now.

Two questions. Can lyricfind be completely disabled on Plex? I went through all of the settings on my server but not finding the end all be all kill switch for the lyricfind feature. I don’t want it, an IMO should have the ability to turn if completely off as a Plex Pass subscriber.

If lyricfind cannot be disabled how can I got about scheduling different scanning updates for my various libraries?

Update to the just-released PMS 1.13
https://forums.plex.tv/discussion/comment/1661803/#Comment_1661803

It contains fix for a bug which may play a role in the above behaviour

(Metadata) Don’t rematch things which have been unsuccessfully matched (#8394)