Synology DS218+, just updated to the latest firmware (DSM 6.2.2-24922 Update 2). The Core is on a docker container, via steefdebruijn/docker-roonserver. Remote on MacOS and Android.
Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Nas is on ethernet, remote on wi-fi. Routeur is Livebox Orange. Audio device is on wifi.
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
RaspberryPI3 with HiFiBerry Dac+ plugged (RCA) on my sono system.
Description Of Issue
Since i’ve upgraded to the latest Synology Firmware, i can’t login to my Roon Server on my different remotes. Even if i put the right credentials, it says “Network error, please check your internet connection”. If i shell into the container to see the logs, here’s what it says :
07/13 12:42:29 Trace: [fiveaccountserver] POST https://accounts5.roonlabs.com/accounts/3/login
07/13 12:42:29 Trace: [fiveaccountserver] BODY email=**************&password=<<<PASSWORD>>>
07/13 12:42:29 Trace: [broker/accounts] Data updated. AccountStatus=NoAccountConfigured MachineStatus=NeedsAccount UserId=<none>
07/13 12:42:29 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
07/13 12:42:29 Trace: [push] retrying connection in 29716ms
07/13 12:42:29 Warn: Error in web request https://accounts5.roonlabs.com/accounts/3/login: NetworkError (The remote server returned an error: (405) Not Allowed.)
Are you by any chance running any new firewalls on the Synology? From the trace you posted, it appears that access to our Roon servers is being blocked somewhere along the line. I would also make sure that you do not by any chance have Open vSwitch turned on in the Synology config settings.
The only thing i’ve done recently is updating the firmware of the Nas.
And, nothing, in the new features, seem to be related to any firewall…
Open vSwitch was turned on, i switched it off, reboot, but nothing change.
Thank you for letting me know that the native install works as expected and that this issue is limited to just the Docker install. I will discuss your findings with our technical team and will reach out to you again once I have further feedback.