Can you help me please. I upgraded the Roon remote (technically roonallinone x64) on my windows PC to Roon 2.0 before being told / realising that my ROCK core will not be able to upgrade to 2.0.
Now my roon remote is 1.8 legacy, my ROCK core is 1.8 and they are not talking to each other.
I have followed all the instructions in Roon 1.8-2.0 migration guide.
I know my core is working because I can still control it from roon remote on my android phone which is still 1.8
@Steven_Booker, I have moved your post to a new thread, so it doesn’t get missed.
Please take a look at this guide, and shout out if you still have problems.
If you are on this page, it means you are not quite ready to use Roon 2.0, but would like to know what your options are. We answer questions like "how long can I use Roon 1.8", "will I be able to upgrade to Roon 2.0 later?" and more in this...
@Martin_Webster. I have followed the migration guide and am still having trouble. Please see the attachments.
Your core needs to be on the Legacy version too. So that will need upgrading. (1.8 Legacy, Production1x)
To use 1.8, they must all be the same version. Which it currently is not.
Roon 2.0 is here, and with it comes some exciting new updates to the Roon platform - including Roon ARC, our mobile app for remote listening - free and exclusive for Roon users.
However, we know not everyone will want to - or will have the capacity to - upgrade to Roon 2.0 straight away. We know some users will want or need to ‘hang back’ from 2.0, at least for a little while.
So alongside Roon 2.0, we’re also giving users the option of sticking with Roon 1.8 - should they choose to. In this p…
How do I upgrade the core to the legacy version? Where do I get the 1.8 legacy version for the core? I already followed the instructions under “RoonOS Core 1.8 Legacy (Nucleus / ROCK)” in the 1.8-2.0 migration FAQ, so if that is not how I upgrade the core to legacy 1.8 then I have no idea what to do next.
Can you try to use the reinstall button again? If it still does not work, can you post a screenshot of the network setup in the WebUI? You might have a DNS issue and may want to try a standard DNS (220.127.116.11 or 18.104.22.168) and see then if it works.
@noris thanks. You solved it. Was running a custom DNS setting for a pihole. Reverting it to 22.214.171.124 fixed the issue.
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.