Wrong banner image URLs for boruto on thetvdb.com

Sonarr version (exact version):
Mono version (if Sonarr is not running on Windows):
OS: Linux 5.9.0-0.bpo.5-arm64 #1 SMP Debian 5.9.15-1~bpo10+1 (2020-12-31) aarch64 GNU/Linux
Debug logs:

cat /var/log/syslog | grep -E ‘Warn].*Metadata’
Apr 1 00:01:01 downpi4 mono[1979]: [Warn] MetadataService: Couldn’t download image https://artworks.thetvdb.com/banners/seasons/321285-0.jpg for [321285][Boruto: Naruto Next Generations]. HTTP request failed: [403:Forbidden] [GET] at [https://artworks.thetvdb.com/banners/seasons/321285-0.jpg]
Apr 1 00:01:02 downpi4 mono[1979]: [Warn] MetadataService: Couldn’t download image https://artworks.thetvdb.com/banners/seasons/321285-1.jpg for [321285][Boruto: Naruto Next Generations]. HTTP request failed: [403:Forbidden] [GET] at [https://artworks.thetvdb.com/banners/seasons/321285-1.jpg]

Description of issue:
I’m using “Kodi (XBMC) / Emby” Metadata with all boxes ticked and after importing all my series (Anime and Standard), everything else is working as expected and I have clean logs except this one issue.

These URLs in the logs are indeed not existent. For at least one of them the filename is correct but the path is wrong:
wrong: https://artworks.thetvdb.com/banners/seasons/321285-1.jpg
correct: https://artworks.thetvdb.com/banners/posters/321285-1.jpg

Whereas the the series folder itself seems to have all the images and poster I’d expect:

-rwxrwxr-x 1 dluser debian-transmission  90K Apr  1 00:20  banner.jpg
-rwxrwxr-x 1 dluser debian-transmission 420K Apr  1 00:20  fanart.jpg
-rwxrwxr-x 1 dluser debian-transmission 256K Apr  1 00:20  poster.jpg
-rwxrwxr-x 1 dluser debian-transmission 115K Apr  1 00:20  season01-banner.jpg
drwxrwxr-x 2 dluser debian-transmission    0 Mar 31 23:57 'Season 1'
-rwxrwxr-x 1 dluser debian-transmission 5.4K Apr  1 00:20  tvshow.nfo

Can anyone point me to where those URLs come from and what I could do to get rid of the warning, or is it maybe temporary?

Thanks in advance.

They comes from TheTVDB’s API, which can be 24+ hours behind (due to caching), if the URLs changed around the time your post was made then it’d have been resolved by now, but if it’s still an issue let us know and we can investigate further.

Hi @markus101, I waited some days but the error described in the first post still shows up exactly the same way. What else can I do to help?