Grey Placeholder for Artist and Album

Hi,

I was able to successfully install the Roon Core on my Synology. Streaming to my Rose RS250 also works.
Unfortunately I have problems with the display of album and artist pictures. Only gray placeholders are displayed here.

Warn: [broker/images] unexpected error GET'ing https://imagecache.roonlabs.net/im/1/artists/7a004d4e30303030313138353434/avatar/1by1_1024.jpg: statuscode=998 error=Request canceled due to timeout
03/08 20:28:41 Warn: [broker/images] unexpected error GET'ing https://imagecache.roonlabs.net/im/1/artists/7a004d4e30303030313138353434/photo/16by7_2048.jpg: statuscode=998 error=Request canceled due to timeout
03/08 20:28:41 Trace: GetImageData[Remote](id=3708 spec=1by1_1024 key=qmfaaaaa uri=https://imagecache.roonlabs.net/im/1/artists/7a004d4e30303030313138353434/avatar/1by1_1024.jpg) => fetched in 100003ms status=998 size=0 overalltime=100003ms
03/08 20:28:41 Trace: GetImageData[Remote](id=3709 spec=16by7_2048 key=rmfaaaaa uri=https://imagecache.roonlabs.net/im/1/artists/7a004d4e30303030313138353434/photo/16by7_2048.jpg) => fetched in 100003ms status=998 size=0 overalltime=100003ms
03/08 20:28:41 Debug: GET /image/zxubaaaa.1by1_512.jpg
03/08 20:28:41 Debug: GET /image/kmnaaaaa.1by1_512.jpg
03/08 20:28:44 Trace: [push] restarting connection (Unable to read data from the transport connection: Software caused connection abort.)
03/08 20:28:44 Trace: [push] retrying connection in 4186ms

03/08 23:20:25 Debug: [easyhttp] [605] HEAD to https://imagecache.roonlabs.net/im/1/albums/3e013944ab2fe63bfd488f0ffcae6b81998f/cover/256sq.jpg timed out after 100002 ms
03/08 23:20:25 Warn: [broker/images] unexpected error HEAD'ing roon://albums/3e013944ab2fe63bfd488f0ffcae6b81998f/cover/__ROON_IMAGE_SIZE__.jpg: statuscode=998
03/08 23:20:25 Warn: [additionalimages] othererror downloading album cover for 62:1:2fab4439-3be6-48fd-8f0f-fcae6b81998f: Result[Status=UnexpectedError]
03/08 23:20:25 Trace: [additionalimages] downloading cover for 62:1:ce5ca649-3bf7-458c-99a8-b4523b3143d3 (libraryalbum=LibraryAlbum[314927, George Winston - Autumn]) (metaalbumid=62:1:ce5ca649 -3bf7-458c-99a8-b4523b3143d3)
03/08 23:20:25 Trace: [library] finished with 12 dirty tracks 1 dirty albums 1 dirty performers 1 dirty works 1 dirty performances 1 dirty genres 0 clumping tracks, 0 clumping auxfiles 0 compute tracks, 0 deleted tracks, 0 tracks to (re)load, 0 tracks to retain, 0 auxfiles to (re)load, 0 auxfiles to retain, and 5 changed objects

I then installed the Roon Core on my Win10 PC. I have no problems here.
Is there a way to fix the error.

Synology DS1621+, DSM 7.0.1-42218 Update3

The Active Directory server is installed on the Synology.

A forwarder to my Speedport Smart 3 router and to Google (8.8.8.8) is entered in the Synology DNS-App.

A SG350-10 10-port gigabit managed switch sits between the router and the NAS.

Nils

Hi @Nils_Biebricher and welcome to the forum.

Do you still experience the same today?

Hi @BlackJack,

it’s still the same

03/09 14:13:48 Debug: GET /image/xeedaaaa.1by1_256.jpg
03/09 14:13:48 Debug: GET /image/rmjbaaaa.1by1_256.jpg
03/09 14:13:48 Debug: GET /image/lxgcaaaa.1by1_256.jpg
03/09 14:13:48 Debug: GET /image/nqeaaaaa.1by1_256.jpg
03/09 14:13:48 Debug: GET /image/busdaaaa.1by1_256.jpg
03/09 14:13:48 Warn: [broker/images] unexpected error GET'ing https://imagecache.roonlabs.net/im/1/artists/7a004d4e30303030363131313032/avatar/1by1_256.jpg: statuscode=998 error=Request canceled due to timeout
03/09 14:13:48 Trace: GetImageData[Remote](id=2427 spec=1by1_256 key=jpdaaaaa uri=https://imagecache.roonlabs.net/im/1/artists/7a004d4e30303030363131313032/avatar/1by1_256.jpg) => fetched in 100018ms status=998 size=0 overalltime=100019ms
03/09 14:13:48 Warn: [broker/images] unexpected error GET'ing https://imagecache.roonlabs.net/im/1/artists/7a004d4e30303030393139323339/avatar/1by1_256.jpg: statuscode=998 error=Request canceled due to timeout
03/09 14:13:48 Trace: GetImageData[Remote](id=194 spec=1by1_256 key=mhaaaaaa uri=https://imagecache.roonlabs.net/im/1/artists/7a004d4e30303030393139323339/avatar/1by1_256.jpg) => fetched in 100030ms status=998 size=0 overalltime=100030ms
03/09 14:13:48 Warn: [broker/images] unexpected error GET'ing https://imagecache.roonlabs.net/im/1/artists/7a004d4e30303030303133383939/avatar/1by1_256.jpg: statuscode=998 error=Request canceled due to timeout
03/09 14:13:48 Trace: GetImageData[Remote](id=19801 spec=1by1_256 key=phdbaaaa uri=https://imagecache.roonlabs.net/im/1/artists/7a004d4e30303030303133383939/avatar/1by1_256.jpg) => fetched in 100020ms status=998 size=0 overalltime=100020ms
03/09 14:13:48 Warn: [broker/images] unexpected error GET'ing https://imagecache.roonlabs.net/im/1/artists/7a004d4e30303030353038343433/avatar/1by1_256.jpg: statuscode=998 error=Request canceled due to timeout
03/09 14:13:48 Trace: GetImageData[Remote](id=7556 spec=1by1_256 key=qelaaaaa uri=https://imagecache.roonlabs.net/im/1/artists/7a004d4e30303030353038343433/avatar/1by1_256.jpg) => fetched in 100028ms status=998 size=0 overalltime=100028ms
03/09 14:13:48 Warn: [broker/images] unexpected error GET'ing https://imagecache.roonlabs.net/im/1/artists/7a004d4e30303030393333383833/avatar/1by1_256.jpg: statuscode=998 error=Request canceled due to timeout
03/09 14:13:48 Warn: [broker/images] unexpected error GET'ing https://imagecache.roonlabs.net/im/1/artists/7a004d4e30303030373238303235/avatar/1by1_256.jpg: statuscode=998 error=Request canceled due to timeout
03/09 14:13:48 Trace: GetImageData[Remote](id=887 spec=1by1_256 key=dibaaaaa uri=https://imagecache.roonlabs.net/im/1/artists/7a004d4e30303030393333383833/avatar/1by1_256.jpg) => fetched in 100029ms status=998 size=0 overalltime=100029ms
03/09 14:13:48 Trace: GetImageData[Remote](id=20217 spec=1by1_256 key=pxdbaaaa uri=https://imagecache.roonlabs.net/im/1/artists/7a004d4e30303030373238303235/avatar/1by1_256.jpg) => fetched in 100019ms status=998 size=0 overalltime=100019ms
03/09 14:13:48 Warn: [broker/images] unexpected error GET'ing https://imagecache.roonlabs.net/im/1/artists/7a004d4e30303030363030393230/avatar/1by1_256.jpg: statuscode=998 error=Request canceled due to timeout
03/09 14:13:48 Trace: GetImageData[Remote](id=909 spec=1by1_256 key=zibaaaaa uri=https://imagecache.roonlabs.net/im/1/artists/7a004d4e30303030363030393230/avatar/1by1_256.jpg) => fetched in 100026ms status=998 size=0 overalltime=100026ms

grafik

As of your description, it seems there is a network related problem either on your NAS or how it is connected to the internet.

Things you can check while you’re troubleshooting your issue:

  • Is your working Win10 PC connected to the same managed switch as your NAS?
  • Is there a firewall on your NAS that you can turn off temporarily to see if it makes a change?
  • Is Synology’s vSwitch active on your NAS?

How big is your library btw. and how much RAM is installed in your NAS?

Is your working Win10 PC connected to the same managed switch as your NAS? - Yes
Is there a firewall on your NAS that you can turn off temporarily to see if it makes a change? - I deactivated the firewall, error still exists
Is Synology’s vSwitch active on your NAS? - Yes, for the VM-Ware Manager
How big is your library btw. and how much RAM is installed in your NAS? - 16GB

grafik

grafik

Then the source of your problem is more likely located on your NAS.

vSwitch is known to create issues with Roon. While the known issues aren’t exactly what you experience, it might still play into it. Try with it disabled.

Might suffice for your library but depends on what else is also running on your NAS (VM-Ware Manager: VMs?). You should monitor the free RAM and make sure there is enough.

Do you also use link aggregation? If so, did you make sure it’s properly configured on your switch too?

If you have a VPN configured on your NAS, try with it disabled.

Sorry that I can’t be of more help, but Roon is just a software and the software runs and has no network related issues when run from your Win10 PC. Also all the links from your logs work for me too.
As it is your network and your NAS you have to do the troubleshooting, turning services on and off to see if they make a difference and/or play around with settings. Maybe another user that reads this has some additional ideas for you to test, but I wouldn’t hold my breath - especially if you don’t want to share your complete NAS setup (details about settings, what other software/services are in use, …) with the community.

Note: The more details you share, the more likely it becomes that someone might be able to point out additional troubleshooting steps for you to try.

@BlackJack
You are my hero. IPv6 was enabled on my NAS. After I deactivated that, the covers also work now.
Thanks very much

2 Likes

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.