Roon app not connecting with Core

Roon Core Machine

432 Evo Music Streamer
Vortexbox and Linux Fedora 20
Squeezebox Server

Networking Gear & Setup Details

BT Smart Hub
Develo Line Adapter with Ethernet

Connected Audio Devices

Audionote USB DAC
Windows 10 PC
iOS remotes

Number of Tracks in Library

2000-3000 tracks - 3% storage used

Description of Issue

Following various iOS, PC and Roon updates, the system is connected to the router but the Squeezebox Server / Roon won’t connect. I’ve powered down and recycled everything and all other devices connect but not Roon. In the Vortexbox GUI, the library isn’t there and the Squeezebox webpage doesn’t load.

Please help!

Ignore Squeezebox comments as not relevant - my mistake.

Here’s my log

11/07/2021 12:50:02 - Starting upgrade. (This can take a long time...)

Cleaning repos: fedora updates vortexbox
Cleaning up everything
No packages marked for update
https://fedora-archive.ip-connect.info//fedora/linux/updates/20/i386/repodata/repomd.xml: [Errno 14] curl#35 - "Cannot communicate securely with peer: no common encryption algorithm(s)."
Trying other mirror.
https://fedora-archive.ip-connect.vn.ua//fedora/linux/updates/20/i386/repodata/1ecb1a996fd829cbdec9f8136c42e19c70d557506bcafd8b3ec8159b1e1dbc21-primary.sqlite.xz: [Errno 14] curl#35 - "Cannot communicate securely with peer: no common encryption algorithm(s)."
Trying other mirror.
https://fedora-archive.ip-connect.vn.ua//fedora/linux/releases/20/Everything/i386/os/repodata/607c312ecfd09c97b30489c0bb13e9ddf25624e703dea02611ba7000f739bb7c-primary.sqlite.bz2: [Errno 14] curl#35 - "Cannot communicate securely with peer: no common encryption algorithm(s)."
Trying other mirror.
Resolving Dependencies
There are unfinished transactions remaining. You might consider running yum-complete-transaction, or "yum-complete-transaction --cleanup-only" and "yum history redo last", first to finish them. If those don't work you'll have to try removing/installing packages by hand (maybe package-cleanup can help).
--> Running transaction check
---> Package 432evo.noarch 0:0.1-4 will be updated
---> Package 432evo.noarch 0:0.1-5 will be an update
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package          Arch             Version            Repository           Size
================================================================================
Updating:
 432evo           noarch           0.1-5              vortexbox            10 k

Transaction Summary
================================================================================
Upgrade  1 Package

Total download size: 10 k
Downloading packages:
No Presto metadata available for vortexbox
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction (shutdown inhibited)
Warning: RPMDB altered outside of yum.
** Found 14 pre-existing rpmdb problem(s), 'yum check' output follows:
bash-4.2.53-2.fc20.i686 is a duplicate with bash-4.2.47-2.fc20.i686
32:bind-license-9.9.4-18.P2.fc20.noarch is a duplicate with 32:bind-license-9.9.4-12.P2.fc20.noarch
fedora-release-20-4.noarch is a duplicate with fedora-release-20-3.noarch
glibc-2.18-19.fc20.i686 is a duplicate with glibc-2.18-12.fc20.i686
glibc-common-2.18-19.fc20.i686 is a duplicate with glibc-common-2.18-12.fc20.i686
hwdata-0.276-1.fc20.noarch is a duplicate with hwdata-0.265-1.fc20.noarch
libgcc-4.8.3-7.fc20.i686 is a duplicate with libgcc-4.8.2-7.fc20.i686
linux-firmware-20150521-48.git3161bfa4.fc20.noarch is a duplicate with linux-firmware-20140317-37.gitdec41bce.fc20.noarch
nss-softokn-freebl-3.19.1-1.0.fc20.i686 is a duplicate with nss-softokn-freebl-3.16.0-1.fc20.i686
perl-Exporter-5.70-1.fc20.noarch is a duplicate with perl-Exporter-5.68-293.fc20.noarch
4:perl-macros-5.18.4-293.fc20.i686 is a duplicate with 4:perl-macros-5.18.2-289.fc20.i686
setup-2.8.71-3.fc20.noarch is a duplicate with setup-2.8.71-2.fc20.noarch
tzdata-2015d-1.fc20.noarch is a duplicate with tzdata-2014b-1.fc20.noarch
vb-startup-1.0-7.fc20.noarch is a duplicate with vb-startup-1.0-3.fc20.noarch
  Updating   : 432evo-0.1-5.noarch                                          1/2
11/07/2021 19:59:38 - Starting upgrade. (This can take a long time...)

Cleaning repos: fedora updates vortexbox
Cleaning up everything
No packages marked for update
https://fedora-archive.ip-connect.vn.ua//fedora/linux/releases/20/Everything/i386/os/repodata/repomd.xml: [Errno 14] curl#35 - "Cannot communicate securely with peer: no common encryption algorithm(s)."
Trying other mirror.
https://fedora-archive.ip-connect.info//fedora/linux/releases/20/Everything/i386/os/repodata/repomd.xml: [Errno 14] curl#35 - "Cannot communicate securely with peer: no common encryption algorithm(s)."
Trying other mirror.
No packages marked for update
11/07/2021 20:00:26 - Upgrade complete. No need to reboot; nothing was updated.

Hello @Arran_Thoma and welcome to the forum.

Just another Roon user here, sharing some thoughts:

  • Fedora 20 reached the “End of Life” status in mid 2015
  • The VortexBox project seems to be abandoned or at least dormant (latest release information I found was about a 2.5 Beta from beginning 2019)
  • Looking at the log you shared, there is nothing related to Roon there
  • Latest Roon Server software comes with new prerequisites that have to be met

I suggest you contact the manufacturer (432 Evo) and ask for support there. Hopefully he is able to fix the firmware issues you seem to have here. You should also try to find out if he knows about the new prerequisites to run Roon Server and if they are already met.

Hi, BJ - yes it’s now with the reseller/manufacturer to sort. The Evo is an expensive piece of kit so expect them to find a workaround. Lots of people having the same issue basically, presumably for the Fedora/Vortexbox support or lack of.

1 Like

Hey @Arran_Thoma,

Thanks for not hesitating to share your experience with Roon — we’re sorry it hasn’t been what you hoped and what we intended. I also want to apologize for the delay in getting back to you…:pleading_face:

I wonder, was the streamer returned to you? Is there any improvement? How can we help? :nerd_face:

Hi, the manufacturer has now rectified the problem and everything is working ok. Many thanks