No, there’s no software update here. Since the server thinks that it needs to be updated, it probably will not attempt to speak to the metadata service again until it is restarted–so the first thing to do is restart your Roon Server and see if the message goes away.
That message means that your Roon Server got a response from something that looked like a “nope, your software is too old” message. The thing is–we haven’t obsoleted any software versions yet. Support for that error case is in the Roon software in case we need to someday, but the code in our cloud services that would send that message back doesn’t exist yet.
Is there any chance that a proxy, WiFi access confirmation screen, national firewall, or something else got between your app and our metadata services and inserted a web page or error? It’s possible that the client would go into the “halted” state if it got a totally nonsensical response like one of those things.
We did try to replicate this from multiple locations and were not successful. Our server monitoring doesn’t show any crashes or problems. We ran through some QA processes on the servers just in case and everything went properly. This includes things like importing large TIDAL collections + thousands of albums and letting the identification process completely, browsing to every kind of TIDAL page to confirm that they are working, checking that “identify album” is returning results appropriately, confirming that artwork is loading when it should, and other similar things.