rebooted the world , recreated services account and so on…
all with version 1.6 working fine… I’m experiencing issue after 1.7 update this morning…
rollback to version 1.6 … ?
thanks for support
PS: experiencing high throughput on network machine running Roon Server on receive … Roon work for rescan local library … >100k file … low cpu… any way to attach some screenshot?
when try to refresh Qobuz or Tidal on “what’s new page” an intermittent red flag flash and fast disappear at bottom of the page … Error loading page … check network …
but my network is working fine…
I think the next step here is to enable diagnostics on your account so the team can take a look. First, can you reboot your Core machine, launch Roon, and then navigate to the TIDAL page and let us know the time you do so and see the error?
I wanted to reach out because I’ve been keeping an eye on our servers, waiting for the aforementioned diagnostics report.
For some reason it is not reaching our servers, even after I tried re-enabling diagnostics on your account. I also ran a quick test and I was able to submit a similar report from my setup here, so something else is going on.
So we can move forward, I was hoping for now you could use the directions found here and send us over a set of logs using a shared Dropbox link.
Hi @Dylan ,
I’m behind hw firewall… but same firewall don’t influence the Roon Core on Mac… , Core on Linux machine don’t run any local firewall or hardening.
this is the log extract from host running Roon Server , I didn’t understood why some messages passes successfully and the broker response is: failed to auth
I escalated this to our senior development team and received some feedback from them on what our next steps here should be.
First, if you have a Windows or Mac machine that you can temporarily use as your Roon Core, can you try updating it to 1.7 and let us know if you’re seeing the same issues?