Hi @vadim , well it seems ive narrowed down the issue to ropieee instances acting as extensions for a display.
My system will work fine and have zero issues if i run roon with no ropieee displays connected to the network. The minute i connect a ropieee instance acting as a display, roon server errors and goes down.
@spockfish took a look at the logs i sent him as part of this thread
And said he couldnt see anything odd aside from the extension not finding the roon core.
He suggested i delete all the extension authorisations i had (which i did) . I then reconnected the ropieee display unit and i didnt even have chance to go in and reauthorise my extension as roon died there and then.
Coild something have changed in this last release around the way extensions speak to roon?