Posts: 8
Threads: 2
Joined: Sep 2024
Reputation:
0
01-20-2025, 12:07 PM
(This post was last modified: Yesterday, 06:58 PM by kosi123.)
Hello guys!
I recently installed moode on a rpi4 and tried a few radio stations. One of the ones that I usually listen to is FM4, which is preprogrammed into moode. However, it doesn't seem to work - all the other radio stations do work though.
Other radio stations that I added by the same provider (ORF) don't work either.
I did some searching but the only results I found were based on a technical error by the player, hence my question here. Does anybody have an idea for a solution? Or should I open an issue on github?
Posts: 13,839
Threads: 314
Joined: Mar 2018
Reputation:
563
Works ok for me.
Try rebooting your Router, etc.
Posts: 8
Threads: 2
Joined: Sep 2024
Reputation:
0
Oh wow sorry, I just immediately assumed moode was the problem since all the other radios worked. The weird thing is the radio stream does work on other devices, just not mine. I just rebooted my router and the rpi with moode, but I still get the same error:
Code: Failed to decode https://orf-live.ors-shoutcast.at/fm4-q2a; CURL failed: Resolving timed out after 10630 milliseconds
Again, the weird things are:
1. All the radio stations (FM4, OE3, ...) from the same provider with almost the same streaming link (ORF) do not work
2. All the other radio stations I tried do work
3. The ORF radio stations do work on other devices
No idea what I should do now. Thank you though for your quick reply! I really love your work, moode has been amazing so far.
Posts: 6,146
Threads: 182
Joined: Apr 2018
Reputation:
245
@ kosi123
Curious. Working here in Maryland in moOde 9.2.2 on a Pi3B+ connected wirelessly to my access point/router.
What do you see if you try curl -v https://orf-live.ors-shoutcast.at/fm4-q2a | more from the command line of your moOde player?
Code: rho@m922green:~ $ curl -v https://orf-live.ors-shoutcast.at/fm4-q2a | more
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 81.16.149.156:443...
* Connected to orf-live.ors-shoutcast.at (81.16.149.156) port 443 (#0)
* ALPN: offers h2,http/1.1
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: /etc/ssl/certs
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
{ [19 bytes data]
* TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [3074 bytes data]
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
{ [520 bytes data]
* TLSv1.3 (IN), TLS handshake, Finished (20):
{ [52 bytes data]
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.3 (OUT), TLS handshake, Finished (20):
} [52 bytes data]
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN: server accepted h2
* Server certificate:
* subject: CN=*.ors-shoutcast.at
* start date: Feb 7 00:00:00 2024 GMT
* expire date: Feb 6 23:59:59 2025 GMT
* subjectAltName: host "orf-live.ors-shoutcast.at" matched cert's "*.ors-shoutcast.at"
* issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=RapidSSL TLS RSA CA G1
* SSL certificate verify ok.
} [5 bytes data]
* using HTTP/2
* h2h3 [:method: GET]
* h2h3 [:path: /fm4-q2a]
* h2h3 [:scheme: https]
* h2h3 [:authority: orf-live.ors-shoutcast.at]
* h2h3 [user-agent: curl/7.88.1]
* h2h3 [accept: */*]
* Using Stream ID: 1 (easy handle 0x559fa247c0)
} [5 bytes data]
> GET /fm4-q2a HTTP/2
> Host: orf-live.ors-shoutcast.at
> user-agent: curl/7.88.1
> accept: */*
...
Regards,
Kent
Posts: 8
Threads: 2
Joined: Sep 2024
Reputation:
0
Hello there!
Sorry for not mentioning the info sooner - working on a rpi zero 2w with moode 9.2.0 and also connected wirelessly.
This is the output:
Code: % Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- 0:00:14 --:--:-- 0* Could not resolve host: orf-live.ors-shoutcast.at
* Closing connection 0
curl: (6) Could not resolve host: orf-live.ors-shoutcast.at
Sorry if this issue doesn't have anything to do with moode; I'm not really well-versed in this topic and didn't know where else to ask.
Posts: 6,146
Threads: 182
Joined: Apr 2018
Reputation:
245
(01-20-2025, 06:49 PM)kosi123 Wrote: Hello there!
Sorry for not mentioning the info sooner - working on a rpi zero 2w with moode 9.2.0 and also connected wirelessly.
This is the output:
Code: % Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- 0:00:14 --:--:-- 0* Could not resolve host: orf-live.ors-shoutcast.at
* Closing connection 0
curl: (6) Could not resolve host: orf-live.ors-shoutcast.at
Sorry if this issue doesn't have anything to do with moode; I'm not really well-versed in this topic and didn't know where else to ask.
This output confirms what was said in the error message you previously posted. "Could not resolve host" means the domain name service (DNS)---on your router or at your ISP or whatever---can't find a reference to the host at orf-live.ors-shoutcast.at.
The .at top-level domain (TLD) is Austria. The only entry in the moOde radio-station table which has .at as its TLD is the one for FM4. Looks like you may be blocked from this domain.
Regards,
Kent
Posts: 8
Threads: 2
Joined: Sep 2024
Reputation:
0
Thank you for your quick reply.
I am actually from Austria myself, which is why I like to listen to FM4. FM4 is part of the ORF, which roughly translated stands for public media company. It is funded by the state and by every citizen in Austria with a yearly fee.
Because of that, ORF and its programs should be accessible everywhere and by everyone - which is why the error is even more interesting.
Therefore I don't think I'm blocked - additionally, other members in the same household (connected to the same router) can access the stream.
No idea why it doesn't work - hopefully I'll figure it out.
Posts: 6,146
Threads: 182
Joined: Apr 2018
Reputation:
245
@ kosi123
Then you said
Quote: additionally, other members in the same household (connected to the same router) can access the stream.
By the same URL?---he asked with "a kind of Alice in Wonderland feeling of curiouser and curiouser."
As for figuring it out---Viel Glück!
Regards,
Kent
Posts: 8
Threads: 2
Joined: Sep 2024
Reputation:
0
Dankeschön!
Just tried it with a hotspot, to not be on the same network - did work.
As for the same URL - no guarantee for anything, as I said I'm not very well-versed. But there is a BluOS Speaker running, connected to the same router and playing FM4 every morning via TuneIn.
As far as I'm concerned, TuneIn also just uses the stream URL - so either both should work or neither, correct?
My laptop (on the same network) also gets an error using curl - I tried TuneIn there as well (the web version) and again, the ORF stations do not work, the others do.
I'm really confused. Thank you very much for your help though! If I ever find a solution, I'll post it here for future users with the same problem.
Posts: 13,839
Threads: 314
Joined: Mar 2018
Reputation:
563
What are the network settings in moode?
Maybe its a DNS address issue.
They are listed in the startup log. The log can be viewed via the SSH command moodeutl -l or downloaded via the Logs section in System Config, or via Menu, System info from any of the Config screens. The startup log will be at the end of System info output.
|