Cannot Connect to Qobuz: Network Error on Roonserver with Ubuntu 20.04.5 LTS (ref#CPC6QI)

Support
1

What’s happening?

I cannot connect Qobuz to Roon anymore. Network error when trying to sign in to qobuz. Seems to have happened when changing KPN (ZTE) router to the new Fritzbox router (not changing the network ip's).

How can we help?

· I read about many same issues in previous years. No clear solution found as far as i can see.
A suggested solution (replacing bits-file with new one) was done by me, did not help. Also removing the Roonserver Cache folder dit not help.
Please provide a new solution.

Other options

· Other

Describe the issue

In Roonserver I cannot connect to Qobuz: When trying to sign in I get a network error: Please check your connection (see screenshot)
- I have restarted router, nuc, devices multiple times
- I have reinstalled all remote Roons (desktop, tablet, phone)
- I have reinstalled Roonserver on the NUC.
- I have installed a new file called "bits" as was suggested in older support thread.
- First real qobuz related error in logfile: Warn: {easyhttp} [80] GET https://www.qobux.com/api.json/0.2/user/login?device_... mail=...&password=....: socketerr (HostUnreachable): No route to host (34.242.7.204:443)

Describe your network setup

Hardware: NUC5i5RHYH (5th gen i5 processor)
Software: Roonserver (nuc/linux) 2.0 build 1413
Software: Ubuntu 20.04.5 LTS (Focal Fossa)
NUC is connected to my network with Netgear switch.
Router is a new Fritzbox 7590AX
Seems like the error appeared not long after I switched to this new router.

2

Have you logged into your server and checked network connectivity to outside servers, including Qobuz, using traceroute (optional Ubuntu Server install)? I’m wondering if there’s some routing issue between your server and the outside internet as a result of the router change. For instance (I’m not saying this is the case in your system), if your server had a fixed IP programmed into it (as opposed to supplied by DHCP with a static IP allocation), the new router might be unable to route properly between it and outside servers.

3

Thanks for the reply Fernando.
Weird, I thought the IP would trace to qobuz, but using traceroute it shows that its the fritzbox ip ??
But no error, so it seems your suggestion does not apply, right?

nuc:~$ traceroute 34.242.7.204
traceroute to 34.242.7.204 (34.242.7.204), 30 hops max, 60 byte packets
1 nuc.fritz.box (192.168.2.22) 2238.523 ms !H 2238.486 ms !H 2238.460 ms !H

4

!H means the target host is unreachable. When you say “the fritzbox ip” I don’t see it, the IP in line 1 is 192.168.2.22, which I’d guess is your NUC’s, as the internal (LAN) router IP is typically something like 192.168.2.1. Something like this could happen if your NUC “thinks” its LAN IP is 192.168.2.22, but the Fritzbox has actually assigned it a different IP.

Here’s what I get when I do the same:

1  _gateway (192.168.2.1)  3.028 ms  2.987 ms  2.975 ms
 2  192.168.1.254 (192.168.1.254)  3.605 ms  3.592 ms  3.579 ms
 3  75-25-136-1.lightspeed.plalca.sbcglobal.net (75.25.136.1)  21.369 ms  22.134 ms  22.122 ms
 4  71.148.164.9 (71.148.164.9)  22.110 ms  22.896 ms  22.087 ms
 5  12.242.117.22 (12.242.117.22)  25.774 ms  25.762 ms  27.486 ms
 6  192.205.37.58 (192.205.37.58)  25.738 ms  23.579 ms  24.290 ms
 7  ae-0.r24.snjsca04.us.bb.gin.ntt.net (129.250.2.122)  62.774 ms  32.737 ms  24.960 ms
 8  ae-8.r23.chcgil09.us.bb.gin.ntt.net (129.250.5.16)  72.717 ms  71.967 ms  71.211 ms
 9  ae-2.r00.bstnma07.us.bb.gin.ntt.net (129.250.4.103)  94.166 ms  94.154 ms  94.952 ms
10  ae-0.newfold-digital.bstnma07.us.bb.gin.ntt.net (129.250.193.78)  94.129 ms  94.118 ms  94.105 ms
11  * * *
12  ip38-113-20-1.yourhostingaccount.com (38.113.20.1)  91.333 ms  92.076 ms  92.419 ms
13  1.149.96.66.static.eigbox.net (66.96.149.1)  91.426 ms  92.059 ms  91.318 ms
1 Like
5

Thanks again Fernando.

Understand what you’re saying, but not sure if it’s so and what to do then.

I will add some logging fragments, to hopefully be of some help..

From line 127 in the log i can see that the FRITZ!Box router is found (192.168.2.1):

(and indeed, the nuc = 192.168.2.22)

06/17 09:35:52 Trace: [mobile] [remoteconnectivity] found new upnp device: Device={ DeviceType=urn:schemas-upnp-org:device:InternetGatewayDevice Version=1 FriendlyName=FRITZ!Box 7590 AX Manufacturer=AVM Berlin

ModelName=FRITZ!Box 7590 AX UDN=uuid: Description=FRITZ!Box 7590 AX ModelNumber=7590avme ManufacturerUri=http://www.avm.de/

ModelUrl=http://www.avm.de/Device={ DeviceType=urn:schemas-upnp-org:device:WANDevice Version=1 FriendlyName=WANDevice - FRITZ!Box 7590 AX

Manufacturer=AVM Berlin ModelName=WANDevice - FRITZ!Box 7590 AX UDN=uuid: Description=WANDevice - FRITZ!Box 7590 AX

ModelNumber=7590avme UPC=AVM IGDDevice={ DeviceType=urn:schemas-upnp-org:device:WANConnectionDevice Version=1 FriendlyName=WANConnectionDevice - FRITZ!Box 7590 AX

Manufacturer=AVM Berlin ModelName=WANConnectionDevice - FRITZ!Box 7590 AX UDN=uuid:

Description=WANConnectionDevice - FRITZ!Box 7590 AX

ModelNumber=7590avme UPC=AVM IGDService={ ServiceType=urn:schemas-upnp-org:service:WANDSLLinkConfig ServiceVersion=1 ServiceId=urn:upnp-org:serviceId:WANDSLLinkC1

ControlUri=http://192.168.2.1:49000/igdupnp/control/WANDSLLinkC1 SCPDUri=http://192.168.2.1:49000/igddslSCPD.xml }

Service={ ServiceType=urn:schemas-upnp-org:service:WANIPConnection ServiceVersion=1 ServiceId=urn:upnp-org:serviceId:WANIPConn1

ControlUri=http://192.168.2.1:49000/igdupnp/control/WANIPConn1 SCPDUri=http://192.168.2.1:49000/igdconnSCPD.xml }

Service={ ServiceType=urn:schemas-upnp-org:service:WANIPv6FirewallControl ServiceVersion=1 ServiceId=urn:upnp-org:serviceId:WANIPv6Firewall1

ControlUri=http://192.168.2.1:49000/igd2upnp/control/WANIPv6Firewall1 SCPDUri=http://192.168.2.1:49000/igd2ipv6fwcSCPD.xml } }

Service={ ServiceType=urn:schemas-upnp-org:service:WANCommonInterfaceConfig ServiceVersion=1 ServiceId=urn:upnp-org:serviceId:WANCommonIFC1

ControlUri=http://192.168.2.1:49000/igdupnp/control/WANCommonIFC1 SCPDUri=http://192.168.2.1:49000/igdicfgSCPD.xml } }

Service={ ServiceType=urn:schemas-any-com:service:Any ServiceVersion=1 ServiceId=urn:any-com:serviceId:any1

ControlUri=http://192.168.2.1:49000/igdupnp/control/any SCPDUri=http://192.168.2.1:49000/any.xml } Icon={ MimeType=image/gif Width=118 Height=119 Depth=8 Uri=http://192.168.2.1:49000/ligd.gif } }

First warning in the log:

06/17 09:35:53 Info: [remoting] loaded protocol hash da9ee47624275d1cfac1375edb3753519fe14440 from /opt/RoonServer/Appliance/Roon.Broker.Api.Remote.dll

06/17 09:35:53 Info: [remoting/brokerserver] Remoting server (V1) listening on port 9331

06/17 09:35:53 Info: [remoting/brokerserver] Remoting server (V2) listening on port 9332

06/17 09:35:53 Trace: [inetdiscovery] added service com.roonlabs.roon.broker.tcp for device broker/

06/17 09:35:53 Trace: [inetdiscovery] added service com.roonlabs.roon.broker.tcpv2 for device broker/

06/17 09:35:53 Trace: [inetdiscovery] added service com.roonlabs.roon.broker.http for device broker/

06/17 09:35:53 Trace: [geoip] GET https://geoip.roonlabs.net/geoip/1/lookup

06/17 09:35:53 Warn: [linuxmount/pinfo] coudn’t ascertain disk block device from devpts

06/17 09:35:53 Warn: [linuxmount/pinfo] coudn’t ascertain disk block device from /dev/mapper/ubuntu–vg-ubuntu–lv

06/17 09:35:53 Warn: [linuxmount/pinfo] coudn’t ascertain disk block device from securityfs

06/17 09:35:53 Warn: [linuxmount/pinfo] coudn’t ascertain disk block device from cgroup2

06/17 09:35:53 Debug: [broker/filebrowser/volumeattached] initial listing found drive mounted at /proc

First Error in the log:

06/17 09:35:55 Info: [broker/locations] adding storage location: Qobuz:Name=QOBUZ:Id=

06/17 09:35:55 Warn: [metadata_context.cs][qobuz] SetCollection 1, collection: <>

06/17 09:35:55 Info: [qobuz] [module] update qobuz location => False

06/17 09:35:55 Info: [broker/locations] updating location Qobuz:Name=QOBUZ:Id=

06/17 09:35:55 Info: [broker/locations] updating location Qobuz:Name=QOBUZ:Id=

06/17 09:35:55 Info: NotifyIsMediaModuleLoading(qobuz,False), _ismedialoading=True => True

06/17 09:35:55 Info: qobuz => False

06/17 09:35:55 Info: tidal => False

06/17 09:35:55 Info: kkbox => True

06/17 09:35:55 Info: metadata => False

06/17 09:35:55 Debug: [oauthcb] update bit: use_tidal_max=True protocolversion=3

06/17 09:35:55 Trace: [kkbox] transition loginstatus from NoAccountConfigured to NoAccountConfigured

06/17 09:35:55 Info: NotifyIsMediaModuleLoading(kkbox,False), _ismedialoading=True => False

06/17 09:35:55 Info: qobuz => False

06/17 09:35:55 Info: tidal => False

06/17 09:35:55 Info: kkbox => False

06/17 09:35:55 Info: metadata => False

06/17 09:35:55 Info: [loadstatus] IsMediaModuleLoading qobuz,tidal,kkbox,metadata: True => False

06/17 09:35:55 Warn: [linuxmount/pinfo] coudn’t ascertain disk block device from gvfsd-fuse

06/17 09:35:56 Warn: [realtime] failed to get time: Connection timed out

06/17 09:35:57 Warn: [easyhttp] [4] GET https://geoip.roonlabs.net/geoip/1/lookup check network configuration: socketerr (HostUnreachable): No route to host (35.231.208.158:443)

06/17 09:35:57 Warn: [easyhttp] [1] POST https://accounts5.roonlabs.com/accounts/3/machineallocate check network configuration: socketerr (HostUnreachable): No route to host (34.148.110.116:443)

06/17 09:35:57 Warn: [easyhttp] [2] POST https://accounts5.roonlabs.com/accounts/3/login check network configuration: socketerr (HostUnreachable): No route to host (34.148.110.116:443)

06/17 09:35:57 Warn: [easyhttp] [3] POST https://accounts5.roonlabs.com/accounts/3/login check network configuration: socketerr (HostUnreachable): No route to host (34.148.110.116:443)

06/17 09:35:57 Warn: [broker/accounts] failed to refresh account info: Result[Status=NetworkError]

06/17 09:35:57 Info: [loadstatus] account loading is complete

06/17 09:35:57 Warn: [broker/accounts] failed to update machine allocation: Result[Status=NetworkError]

06/17 09:35:57 Warn: [broker/accounts] failed to refresh account info: Result[Status=NetworkError]

06/17 09:36:02 Trace: [volumewatcher] ev_VolumeChanged DidMount: /run/user/1000/doc

06/17 09:36:02 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /run/user/1000/doc

06/17 09:36:02 Debug: [broker/filebrowser/volumeattached] skipping /run/user/1000/doc because it is not a /dev/sd[0-9]* (mountline: /dev/fuse /run/user/1000/doc fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0)

06/17 09:36:02 Trace: [broker/accounts] refreshing account info for email=‘pjotrbaccounts@gmail.com’ userid=

06/17 09:36:02 Trace: [fiveaccountserver] POST https://accounts5.roonlabs.com/accounts/3/login

06/17 09:36:02 Trace: [fiveaccountserver] BODY token=

06/17 09:36:03 Warn: [easyhttp] [6] POST https://accounts5.roonlabs.com/accounts/3/login check network configuration: socketerr (HostUnreachable): No route to host (34.148.110.116:443)

06/17 09:36:03 Warn: [easyhttp] [5] GET https://push-manager.roonlabs.net/1/connect check network configuration: socketerr (HostUnreachable): No route to host (35.231.208.158:443)

06/17 09:36:03 Warn: [broker/accounts] failed to refresh account info: Result[Status=NetworkError]

06/17 09:36:03 Warn: [push2] request to push manager failed (https://push-manager.roonlabs.net/1/connect) with status code: 999

06/17 09:36:03 Trace: [push2] retrying connection in 66047ms

06/17 09:36:03 Warn: [auth] EnsureAuthReady failed: Result[Status=NetworkError]

06/17 09:36:03 Warn: [auth] EnsureAuthReady failed: Result[Status=NetworkError]

06/17 09:36:03 Warn: [auth] EnsureAuthReady failed: Result[Status=NetworkError]

06/17 09:36:03 Trace: [roondns] flushed 37 last-known-good entries

06/17 09:36:05 Info: [stats] 5107mb Virtual, 318mb Physical, 115mb Managed, 260 Handles, 81 Threads

06/17 09:36:06 Warn: [easyhttp] [8] POST https://discovery.roonlabs.net/1/register check network configuration: socketerr (HostUnreachable): No route to host (35.231.208.158:443)

06/17 09:36:06 Warn: [easyhttp] [9] POST https://roonmobile.roonlabs.net/1/cores/announce check network configuration: socketerr (HostUnreachable): No route to host (104.22.15.70:443)

06/17 09:36:06 Warn: [easyhttp] [7] GET https://messaging.roonlabs.net/1/api/messages/ check network configuration: socketerr (HostUnreachable): No route to host (35.231.208.158:443)

06/17 09:36:06 Warn: [inetdiscovery] failed to register: Result[Status=NetworkError]

6

Hum… For the first block of warnings, looks like Roon is enumerating all possible block devices, and noticing that most are not actual mountable block devices (for instance proc). I looked at my logs, same kind of warnings, for a totally functioning system.

The first warning that really concerns me is

Warn: [realtime] failed to get time: Connection timed out

which suggests a network problem independent of Qobuz. I’d suggest you look at your Linux logs (/var/log/syslog) for any warnings/errors, and do some more network connectivity probing on the NUC.

1 Like
8

Hi @Pjotr_Bee,

I wanted to check in on your thread and see if you were still having issues? If so, please reproduce the issue and use the directions found here and send over a set of logs to our File Uploader?

Thank you!

9

Hello, yes still having the issue and not been able to find any leads in linux log files. I will react to your suggestions in coming days.

Done, Pjotr_Bee-roon-Logs.zip uploaded with Roon Log Uploader-Zoho WorkDrive.
Hope it helps !

KR,
Pjotrbee

10

Hi Roon Support,

I have uploaded the log files on june 21 (Pjotr_Bee-roon-Logs.zip)

To be complete here the current problems I am experiencing:

  1. Cannot connect to Qobuz : network error
  2. Search function does not work anymore : Can’t connect to Roon Search
  3. Most (not all) album art covers disappeared (grey square). When choosing an album I can see a quick flash of the cover, then it just shows grey.

Waiting for a solution,

KR,
Pjotr Bee

11

Hi @Pjotr_Bee,

Thanks for the update. As was mentioned on this thread, it doesn’t appear to be a Qobuz-specific issue, but more so an issue tied to your local network. We’re seeing frequent breaks and disconnects through out the logs you’ve sent over:

Warn: [auth] EnsureAuthReady failed: Result[Status=NetworkError]

Can you set up a direct ethernet connection from your Roon Server directly to your router? I’d give your router and server a hard reboot and leave them unplugged for a few minutes before powering back up.

12

Unfortunatelly no effect. Exactly same issues.
I’ll not be able to react the coming week.
After that I will start with reinstalling the old router (which I gave away, so I have to retrieve it first). I will let you know the results.

1 Like
16

Hi @Pjotr_Bee,

We wanted to check in before this thread auto-closed. Are you still encountering the symptoms you reported in your posts above?

17

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.