Thank you for your donation!


Solved: TIDAL
#11
(09-04-2018, 04:26 PM)TheOldPresbyope Wrote: Aha.

The Linux OS hosting your moOde player is asking the DNS system to resolve (e.g., get the IP address for) the hostname ab-pr-ak.audio.tidal.com but the resolution fails.

Can you "ping" this hostname directly from the command line?

Here's what I see when I ping it:

Code:
pi@moode:~ $ ping ab-pr-ak.audio.tidal.com
PING eip-tata.eip4ab-pr-ak.audio.tidal.com.akahost.net (23.40.100.13) 56(84) bytes of data.
64 bytes from a23-40-100-13.deploy.static.akamaitechnologies.com (23.40.100.13): icmp_seq=1 ttl=59 time=6.32 ms
^C
It's geeky but it shows the hostname can be resolved here.
Regards,
Kent


At the first sight I thought about DNS issue. Nevertheless Tidal application for iOS and OSX are resolving IP thru DNS servers defined in router. Apparently moOde does not:


Code:
pi@moode:~ $ ping ping ab-pr-ak.audio.tidal.com
ping: ab-pr-ak.audio.tidal.com: Temporary failure in name resolution


Regards,
Reply
#12
No issue on my end. Try rebooting your Router.

Code:
pi@rp3:~ $ ping ab-pr-ak.audio.tidal.com
PING eip-ntt.eip4ab-pr-ak.audio.tidal.com.akahost.net (2.18.48.13) 56(84) bytes of data.
64 bytes from a2-18-48-13.deploy.static.akamaitechnologies.com (2.18.48.13): icmp_seq=1 ttl=57 time=21.3 ms
64 bytes from a2-18-48-13.deploy.static.akamaitechnologies.com (2.18.48.13): icmp_seq=2 ttl=57 time=19.4 ms
64 bytes from a2-18-48-13.deploy.static.akamaitechnologies.com (2.18.48.13): icmp_seq=3 ttl=57 time=16.7 ms
64 bytes from a2-18-48-13.deploy.static.akamaitechnologies.com (2.18.48.13): icmp_seq=4 ttl=57 time=18.8 ms
64 bytes from a2-18-48-13.deploy.static.akamaitechnologies.com (2.18.48.13): icmp_seq=5 ttl=57 time=20.0 ms
64 bytes from a2-18-48-13.deploy.static.akamaitechnologies.com (2.18.48.13): icmp_seq=6 ttl=57 time=17.8 ms
^C
--- eip-ntt.eip4ab-pr-ak.audio.tidal.com.akahost.net ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5005ms
rtt min/avg/max/mdev = 16.711/19.041/21.349/1.506 ms
Reply
#13
Hi Tim,

Before touching Router I tried ping Tidal from my laptop:


Code:
MacBook-Pro:~ $ ping ab-pr-ak.audio.tidal.com
PING eip-tata.eip4ab-pr-ak.audio.tidal.com.akahost.net (23.7.244.13): 56 data bytes
64 bytes from 23.7.244.13: icmp_seq=0 ttl=59 time=48.098 ms
64 bytes from 23.7.244.13: icmp_seq=1 ttl=59 time=47.261 ms
64 bytes from 23.7.244.13: icmp_seq=2 ttl=59 time=44.795 ms

..no isues

Regards,
Reply
#14
(09-04-2018, 07:43 PM)gza123 Wrote: At the first sight I thought about DNS issue. Nevertheless Tidal application for iOS and OSX are resolving IP thru DNS servers defined in router. Apparently moOde does not:


Code:
pi@moode:~ $ ping ping ab-pr-ak.audio.tidal.com
ping: ab-pr-ak.audio.tidal.com: Temporary failure in name resolution

Ok, so if other hosts on your LAN can resolve the hostname but your moOde player can't, I would suspect your moOde player is not using the same service.

Are you using firewalls, subnets, proxies, etc., which could be cause different devices to respond differently?

What's the content of /etc/resolv.conf on your moOde host and how does it compare with the equivalent on your OSX host?

On my LAN, DNS requests are resolved on my Verizon Fios router at 192.168.1.1. For all my moOde players and for my Linux Mint laptop, the content is identical and

Code:
<username@hostname>:~ $ cat /etc/resolv.conf
# Generated by resolvconf
domain fios-router.home
nameserver 192.168.1.1


In a pinch, one could check by temporarily changing the nameserver value in this file to a public server outside the home domain. Examples are Google's DNS server 8.8.8.8, OpenDNS 208.67.222.222, Dyn 216.146.35.35, or even CloudFlare's new 1.1.1.1.

Regards,
Kent
Reply
#15
(09-04-2018, 10:59 PM)TheOldPresbyope Wrote: .......

Ok, so if other hosts on your LAN can resolve the hostname but your moOde player can't, I would suspect your moOde player is not using the same service.

Are you using firewalls, subnets, proxies, etc., which could be cause different devices to respond differently?

What's the content of /etc/resolv.conf on your moOde host and how does it compare with the equivalent on your OSX host?

On my LAN, DNS requests are resolved on my Verizon Fios router at 192.168.1.1. For all my moOde players and for my Linux Mint laptop, the content is identical and

Code:
<username@hostname>:~ $ cat /etc/resolv.conf
# Generated by resolvconf
domain fios-router.home
nameserver 192.168.1.1


In a pinch, one could check by temporarily changing the nameserver value in this file to a public server outside the home domain. Examples are Google's DNS server 8.8.8.8, OpenDNS 208.67.222.222, Dyn 216.146.35.35, or even CloudFlare's new 1.1.1.1.

Regards,
Kent


I have no proxies nor subnets. Just simple configuration LAN-Router-WAN.
Router is giving external DNS (ISP's) servers to all LAN hosts via DHCP service.
Following your advise, I compared /etc/resolv.conf at both moOde and OSX seem to be identical:

moOde:

Code:
pi@moode:~ $ cat /etc/resolv.conf
# Generated by resolvconf
domain gdansk-morena.vectranet.pl
nameserver 37.8.214.2
nameserver 31.11.202.254

OSX:

Code:
MacBook-Pro:~ $ cat /etc/resolv.conf
#
# macOS Notice
#
# This file is not consulted for DNS hostname resolution, address
# resolution, or the DNS query routing mechanism used by most
# processes on this system.
#
# To view the DNS configuration used by this system, use:
#   scutil --dns
#
# SEE ALSO
#   dns-sd(1), scutil(8)
#
# This file is automatically generated.
#
domain gdansk-morena.vectranet.pl
nameserver 37.8.214.2
nameserver 31.11.202.254

Regards,
Reply
#16
(09-05-2018, 08:19 AM)gza123 Wrote: I have no proxies nor subnets. Just simple configuration LAN-Router-WAN.
Router is giving external DNS (ISP's) servers to all LAN hosts via DHCP service.
Following your advise, I compared /etc/resolv.conf at both moOde and OSX seem to be identical:

moOde:

Code:
pi@moode:~ $ cat /etc/resolv.conf
# Generated by resolvconf
domain gdansk-morena.vectranet.pl
nameserver 37.8.214.2
nameserver 31.11.202.254

OSX:

Code:
MacBook-Pro:~ $ cat /etc/resolv.conf
#
# macOS Notice
#
# This file is not consulted for DNS hostname resolution, address
# resolution, or the DNS query routing mechanism used by most
# processes on this system.
#
# To view the DNS configuration used by this system, use:
#   scutil --dns
#
# SEE ALSO
#   dns-sd(1), scutil(8)
#
# This file is automatically generated.
#
domain gdansk-morena.vectranet.pl
nameserver 37.8.214.2
nameserver 31.11.202.254

Regards,

@gza123

I just tried to resolve the Tidal hostname with the nameservers listed in your resolv.conf by using the 'dig' command [1]. The process failed in both instances. Here's just the first failure:


Code:
pi@moode:~ $ dig @37.8.214.2 ab-pr-ak.audio.tidal.com

; <<>> DiG 9.10.3-P4-Raspbian <<>> @37.8.214.2 ab-pr-ak.audio.tidal.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 36545
;; flags: qr rd ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;ab-pr-ak.audio.tidal.com.    IN    A

;; Query time: 135 msec
;; SERVER: 37.8.214.2#53(37.8.214.2)
;; WHEN: Wed Sep 05 12:26:07 EDT 2018
;; MSG SIZE  rcvd: 53


In contrast, here's a successful result using the Google nameserver 8.8.8.8:

Code:
pi@moode:~ $ dig @8.8.8.8 ab-pr-ak.audio.tidal.com

; <<>> DiG 9.10.3-P4-Raspbian <<>> @8.8.8.8 ab-pr-ak.audio.tidal.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50490
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;ab-pr-ak.audio.tidal.com.    IN    A

;; ANSWER SECTION:
ab-pr-ak.audio.tidal.com. 74    IN    CNAME    ab-pr-ak.audio.tidal.akadns.net.
ab-pr-ak.audio.tidal.akadns.net. 29 IN    CNAME    eip4ab-pr-ak.audio.tidal.com.edgekey.net.
eip4ab-pr-ak.audio.tidal.com.edgekey.net. 17877    IN CNAME eip4ab-pr-ak.audio.tidal.com.eip.akadns.net.
eip4ab-pr-ak.audio.tidal.com.eip.akadns.net. 299 IN CNAME eip-tata.eip4ab-pr-ak.audio.tidal.com.akahost.net.
eip-tata.eip4ab-pr-ak.audio.tidal.com.akahost.net. 8 IN    A 23.7.244.13

;; Query time: 201 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Sep 05 12:24:38 EDT 2018
;; MSG SIZE  rcvd: 272


You can try the same test at your location using your own moOde player.

I don't have any experience with OSX. These comment lines from your /etc/resolv.conf file tell me I can't simply extrapolate from my past Linux/Unix experience:

Quote:# This file is not consulted for DNS hostname resolution, address
# resolution, or the DNS query routing mechanism used by most
# processes on this system.

It could mean that your OSX is actually using a different nameserver than those listed in its resolve.conf file.

Regards,
Kent

[1] dig is not part of a default raspbian installation. You can install it from the dnsutils package:

Code:
pi@moode:~ $ sudo apt-get install dnsutils
Reply
#17
Photo 
Thanks Kent,

After few tests I'm quite convinced that problem lays in DNS provided by my ISP's which cannot resolve Tidal URL's.

I solved it by setting Static network configuration instead of DHCP at moOde because my ISP has restricted Router user configuration to SSID and WIFI password change. (lol)

   

@dekac please confirm whether Static network configuration at your moOde solved issue with Tidal service.

Greetings,
Reply
#18
(09-04-2018, 01:45 PM)TheOldPresbyope Wrote:
(09-04-2018, 08:24 AM)gza123 Wrote: Thanks Kent,

I enabled upmpdcli logging exactly as you advised. Then I tried to play one of my Tidal playlists and see what has been written into /var/log/moodeupnp.log . Surprisingly the logfile was not been created at all.
Then I had a look at Audio info -> Input Processing -> Source from moOde menu. In most cases there is statement: File Not Found.
However, sometimes it shows moOde local adderes instead of Tidal's url:



I'm wondering what was happened?

Regards,

It's been a while since I explored the innards of upmpdcli. I probably left something out of my instructions. 

However, the source info you reported is correct. upmpdcli is acting as a proxy server for the Tidal stream so you see the IP address of the local host rather than a Tidal server.

[EDIT] Do you see anything interesting in /var/log/mpd/log? 

Here's what my log contains after successfully playing first a radio station and then a track from Tidal:

Code:
Sep 04 09:34 : player: played "http://stream.radioactive.fm:8000/ractive"
Sep 04 09:37 : player: played "http://192.168.1.184:49149/tidal/track?version=1&trackId=89621546"


I'll report back after revisiting my notes on upmpdcli.

Regards,
Kent

For your Notes Kent:
I am no longer on the version UPMPDCLI that is default with Moode but I think the log entries actually end up in syslog, perhaps a bug. I think think this is fixed in the latest source code but it is not available as a package.

From what I understand from the developer UPMPDCLI serves up a url (as above) but this url actually does a redirect to the tidal url which is why the Tidal URL errors appear in the MPD logs I think.
Reply
#19
What version are u using?
Reply
#20
(09-09-2018, 12:30 PM)serverbaboon Wrote: For your Notes Kent:
I am no longer on the version UPMPDCLI that is default with Moode but I think the log entries actually end up in syslog, perhaps a bug. I think think this is fixed in the latest source code but it is not available as a package.

From what I understand from the developer UPMPDCLI serves up a url (as above) but this url actually does a redirect to the tidal url which is why the Tidal URL errors appear in the MPD logs I think.

I twigged to the syslog entries only a couple of days ago Blush Thanks for getting the information into this thread.

I recently built upmpdcli 1.3.0 to try out its Radio Paradise FLAC capability. The basic UPnP functionality is working on my moOde player but I haven't sorted out the plugins yet. TIDAL/gmusic are generating "Service login of communication failure" messages in BubbleUPnP and I haven't sorted how to present the radio list in BubbleUPnP for either this version of upmpdcli or the 1.2.16 version distributed with recent moOde releases. This weekend I've been doing community volunteer work so won't get back to the problem for a couple of days yet.

Yes, the URL is redirected within upmpdcli. MPD remains blissfully unaware of TIDAL.

Regards,
Kent
Reply


Forum Jump: