Hello All,
We realize it has been some time since you have heard from us, but there has been quite a lot of work regarding this issue happening in the background.
I wanted to touch base with some good news, which is that after a lengthy investigation, we have finally had a breakthrough earlier this week in understanding the issue, what is causing it, and how to resolve it.
The fix for this issue is set to go out to Early Access testers the week of December 19th, and then to the production RoonServer release following the winter holidays.
For those impacted by this issue, please keep an eye out for the earlyaccess release coming up and let us know if it solves the issue on your end. You can freely join the earlyaccess program by following this guide: https://help.roonlabs.com/portal/en/kb/articles/roon-early-access-program
We have also been working with @crieke , and have discovered a manual fix for this issue, but the fix involves editing the RoonServer startup script and is technically involved, so I will let Chris explain the manual fix in a comment below.
This issue has been discussed internally on a weekly basis for some time, and we apologize for the lengthy investigation that it took until the root cause of the issue was located, this issue was tricky to nail down.
Please, stay tuned for the next earlyaccess RoonServer release or Chris’ workaround which will be mentioned below. Thank you!