'Error loading page' error message appears frequently since 1.7 upgrade

Hi @hmack,

Looking through your Roon logs, I am seeing the following traces when trying to access TIDAL content:

02/14 14:52:37 Debug: [easyhttp] GET to https://metadata.roonlabs.net/1/performers/122:0:MN0000131295/refs?c=tidal-gb returned after 1265 ms, status code: 200
02/14 14:52:39 Warn: [easyhttp] web exception without response: Name or service not known Name or service not known
02/14 14:52:39 Warn: [easyhttp] web exception without response: Name or service not known Name or service not known
02/14 14:52:40 Warn: [easyhttp] web exception without response: Name or service not known Name or service not known
02/14 14:52:40 Trace: [Muso] [HighQuality, 16/44 TIDAL FLAC => 16/44] [100% buf] [PLAYING @ 1:18/4:05] Skyline Drive - Shahin & Sepehr
02/14 14:52:40 Warn: [easyhttp] web exception without response: Name or service not known Name or service not known
02/14 14:52:41 Warn: [easyhttp] web exception without response: Name or service not known Name or service not known

At your timestamp:

02/15 20:47:15 Debug: [easyhttp] GET to https://metadata.roonlabs.net/1/albums/166:0:1410980/reviews?c=tidal-gb returned after 1539 ms, status code: 200
02/15 20:47:16 Warn: [easyhttp] web exception without response: Name or service not known Name or service not known
02/15 20:47:17 Warn: [easyhttp] web exception without response: Name or service not known Name or service not known

And I’m even seeing Airplay lost packets when playing back content:

02/14 12:30:30 Trace: [Muso] [HighQuality, 16/44 TIDAL FLAC => 16/44] [100% buf] [PLAYING @ 0:23/2:30] I Will Wait for You - Barbara Dickson
02/14 12:30:31 Trace: [airplay/client] server lost 1 packets starting at seq 43142
02/14 12:30:31 Trace: [airplay/client] resent packet to 192.168.0.12:1277 with seq 43142
02/14 12:30:31 Trace: [airplay/client] server lost 1 packets starting at seq 43143
02/14 12:30:31 Trace: [airplay/client] resent packet to 192.168.0.12:1277 with seq 43143
02/14 12:30:31 Trace: [airplay/client] server lost 1 packets starting at seq 43144
02/14 12:30:31 Trace: [airplay/client] resent packet to 192.168.0.12:1277 with seq 43144
02/14 12:30:31 Trace: [airplay/client] server lost 1 packets starting at seq 43146
02/14 12:30:31 Trace: [airplay/client] resent packet to 192.168.0.12:1277 with seq 43146

All these traces point back to network instability somewhere along the line, my first suggestion here would be to replace the ISP-provided router with a consumer grade one, I strongly believe that a new router would greatly help with the issues you are experiencing.