That’s a fair comment but never got a reason or answer why it didn’t work.
All a waste of time after the no logins and rubbish bitrate as you say.
And finally the PC (x86) Build:
http://logs.volumio.org/volumio/8A4boZp.html
Similar to others, 4.084 build works great on everything except Qobuz and Roon output to HDMI. At least here it will “start” playing from Roon but no audio. When I switch to the internal speaker on the PC, it plays just fine.
I might be wrong (I often am 
)…
But there were several advices on this thread pointing you to your network, and I don’t see any mention from you about that. Have you tried to fix, or at least verify, that all is well in the network?
PS. Sent a log file or two in the past with error messages. I couldn’t find the cookie in chrome, maybe my router is blocking it (Skynet installed and another thing). Or the country is wrong, or live videos are different.
All pretty pointless trying to play from videos anyway, Chromecast audio can’t do it either. Shouldn’t need to do all that. It used to work by signing in. Better off streaming music from music apps at better bitrate.
Hey @Rochambeaux,
You flashed 4.084 and have the same issues. This confirms it is not a Volumio version problem.
Time Sync failure
Both your Pi 5 and x86 logs show:
setdatetime-helper: all HTTPS Date fallbacks failed
Your Pi 5 boots with the system clock set to 1970. NTP cannot resolve pool servers because DNS is failing. The HTTPS fallback also fails. With wrong system time, TLS certificates appear invalid and OAuth tokens get rejected - this common scenario where streaming services fail to authenticate.
DNS failures
Your x86 log shows Spotify failing 12 consecutive times with “device or resource busy” on DNS lookups. OAuth token refresh fails the same way.
@vmiguel already pointed you toward your network. Volumio works fine on multitude of installations. When identical failures appear across Pi 4, Pi 5, Pi 400, and x86, the problem is not Volumio - it is your local network. I can not reproduce the issue on my entire fleet from Pi Zero 2W all way up to CM5, and I mean every single Raspberry Pi SBC SKU.
Check your router. Some routers have unreliable DNS forwarding, caching issues, or rate limiting. Try configuring 8.8.8.8 or 1.1.1.1 as upstream DNS.
Why Tidal Connect works
Tidal Connect works because the Tidal app pushes to the device. Volumio does not need to initiate outbound connections or validate certificates for incoming streams. Qobuz, Spotify, and other services require Volumio to reach out and authenticate - which fails when DNS is broken and time cannot sync.
See also: [GUIDE] Volumio Time Sync Watchdog (setdatetime-helper)
Roon Bridge
This is a community plugin - issues should be raised with the developer here: [PLUGIN] Volroon - Roon Bridge plugin with metadata and control
We can help with official releases and beta - current version is 4.119.
Kind Regards,
Thank you.
Why would the clock on the Pi 5 and X86 device be wrong but all the Pi 4s and other PCs and devices on my LAN be correct? And if the clock on my Pi 4 is good, then why would it be the same issue on the Pi 5 and X86?
I did try the router suggestions, i.e. rebooting and assigning DNS to 8.8.8.8 and 1.1.1.1 - same result.
For the Roon Bridge HDMI, issues the link you referenced is for the Volroon plugin, which I can’t find after enabling in /Dev. has it been pulled?
Hey @Rochambeaux,
Your logs show time sync failure on both Pi 5 and x86:
setdatetime-helper: all HTTPS Date fallbacks failed
This is not theory - it is in your logs. Why it affects your Pi 5 and x86 but not your Pi 4 is for you to investigate. The evidence is there.
I have tested Volumio on Pi and x86 - it works. Your logs show failures that do not appear on working systems.
Have you actually verified whether time is correct on your affected devices? SSH in and run:
date
If it shows a significantly wrong date, that problem is in your system. The guide I linked explains the time sync mechanism and how to diagnose it: [GUIDE] Volumio Time Sync Watchdog (setdatetime-helper)
Changing router DNS to 8.8.8.8 does not help if something else on your network is intercepting or blocking DNS/NTP traffic. Some routers, firewalls, or IoT security appliances do this.
Roon Bridge
I do not use Roon. The link I shared appears to be the correct plugin thread. Perhaps another Roon user can assist.
Kind Regards,
You’ve got a mix of things going on, at one point it was even a wrong image (V3 on Pi 5), plus there are hints of bad flashes and even a corrupted MPD database. But the big thing that keeps showing up in your logs is DNS failing. That would explain why Tidal Connect works (it’s pushed from the phone), but Spotify/Qobuz/Roon keep failing, they need proper outbound connections.
Also the fact that you’re seeing the same behavior on Pi 4, Pi 5 and a PC kinda rules out it being just a Volumio bug.