I apologize for my impatience but more than ten months have passed since that bug occurred. Is there some development on that issue?
Same here , vers 2.806
I am running into this issue as well with a couple week old install (version 2.806). Previously, I was able to look at the available plugins. My install now has the following error message:
info: Cannot download Available plugins list: Error: connect ETIMEDOUT 172.67.153.54:80
I am able to ping that machine from my network.
Thanks,
Chris.
Tried a fresh install today and I am still getting the same error.
Version: 2.806
Raspberry Pi 4 4GB
Hifiberry Amp2
Thanks,
Chris.
Submitted a bug report for this issue. It can be found here:
I think it has to do with the DNS settings. Have you rebooted/reset your router recently?
Updated the bug report. For some reason, my system cannot connect to one of the hosts serving the available plugin list (172.67.153.54) whereas the other two hosts work just fine.
Chris.
I am having the same issue 2 years later.
I have tried to turn the wifi on and off.
I disabled the hotspot.
I tried to use the custom DNS.
Nothing is working.
This exact set up was working 2 weeks ago, and I have done a system update since then.
http://logs.volumio.org/volumio/rIkNNMJ.html
Any thoughts anyone, I can’t move forward at all now…
what version are you using?
i see that you got a time out on the plugins.
http://plugins.volumio.org, 5602 ms: FAILED
the rest runs with ok
did you try with network cable?
Hi, I think it’s all in the logs, latest version 3.324
did you reboot?
what some times helps is playing with the buttons on the plugin page.
and what i see in log is that wifi is switched off …can you check that?
hi balbuze is this a common thing with the 3.324?
We see in your log that plugins endpoint can’t be reached
http://plugins.volumio.org, 5602 ms: FAILED
something in your network block this access.
So you use a firewall?
@dvo I am using a wired connection, rebooted, and “played” with the buttons…
@balbuze I can’t access that URL in a browser either. I am of course using a firewall, however it was working until recently and there are no settings in firewall to explicitly block that URL.
Looking at a tracert it’s getting lost outside my network
C:\Users\Dave>tracert plugins.volumio.org
Tracing route to plugins.volumio.org [192.64.119.194]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms UBIQUITIUSGRack [192.168.1.1]
2 <1 ms <1 ms <1 ms 185-144-72-250.ip4.tkom.io [185.144.72.250]
3 <1 ms <1 ms <1 ms 185-144-73-0.ip4.tkom.io [185.144.73.0]
4 11 ms 49 ms 52 ms 10.128.48.4
5 2 ms 1 ms 1 ms 185-144-72-130.ip4.tkom.io [185.144.72.130]
6 1 ms 1 ms 1 ms 10ge-te-0-0-1-811.bozen-85-route-special-01.as34347.net [185.35.183.137]
7 17 ms 27 ms 17 ms 10ge-te0-0-0-59-frankfurt-43-route-02.as34347.net [185.35.182.226]
8 18 ms 17 ms 18 ms 10ge-te0-0-0-59-frankfurt-43-route-02.as34347.net [185.35.182.226]
9 18 ms 18 ms 18 ms Frankfurt-MX80.incapsula.com [80.81.193.87]
10 159 ms 160 ms 159 ms 10.255.20.33
11 * * * Request timed out.
12 * * * Request timed out.
If I enter the IP it’s resolving to into a browser, I get taken to https://plugins.volumio.workers.dev/ which also doesn’t respond (times out)
@balbuze …
C:\Users\Dement>tracert plugins.volumio.org
Tracing route to plugins.volumio.org [192.64.119.194]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms netwerk [192.168.1.1]
2 2 ms 1 ms 2 ms 192.168.178.1
3 12 ms 13 ms 11 ms xxx-xxx-xxx-1.cable.dynamic.v4.ziggo.nl [xx.xx.xx.xx]
4 14 ms 13 ms 10 ms 212.142.3.37
5 14 ms 15 ms 21 ms asd-tr0021-cr101-be113-2.core.as33915.net [213.51.7.96]
6 20 ms 10 ms 11 ms nl-ams02a-rc2-lag60-2.core.as33915.net [213.51.64.134]
7 14 ms 14 ms 13 ms nl-ams17b-rc1-lag-56-0.aorta.net [84.116.130.221]
8 * * * Request timed out.
9 24 ms 24 ms 33 ms uk-lon01b-ri1-ae-25-0.aorta.net [84.116.136.102]
10 19 ms 21 ms 23 ms 213.46.182.188
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 182 ms 176 ms 177 ms 192.64.119.194
Trace complete.
C:\Users\Dement>
it looks like tracing to the server is with some hikups.
Ping from the Volumio Pi device itself is actually fine
___
/\_ \ __
__ __ ___\//\ \ __ __ ___ ___ /\_\ ___
/\ \/\ \ / __`\\ \ \ /\ \/\ \ /' __` __`\/\ \ / __`\
\ \ \_/ |/\ \L\ \\_\ \_\ \ \_\ \/\ \/\ \/\ \ \ \/\ \L\ \
\ \___/ \ \____//\____\\ \____/\ \_\ \_\ \_\ \_\ \____/
\/__/ \/___/ \/____/ \/___/ \/_/\/_/\/_/\/_/\/___/
Free Audiophile Linux Music Player - Version 3.0
© 2015-2021 Michelangelo Guarise - Volumio Team - Volumio.org
Volumio Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Welcome to Volumio for Raspberry Pi (5.10.92-v7+ armv7l)
volumio@volumio-pi3:~$ ping plugins.volumio.org
PING plugins.volumio.org (192.64.119.194) 56(84) bytes of data.
64 bytes from 192.64.119.194 (192.64.119.194): icmp_seq=1 ttl=55 time=162 ms
64 bytes from 192.64.119.194 (192.64.119.194): icmp_seq=2 ttl=55 time=162 ms
64 bytes from 192.64.119.194 (192.64.119.194): icmp_seq=3 ttl=55 time=162 ms
64 bytes from 192.64.119.194 (192.64.119.194): icmp_seq=4 ttl=55 time=162 ms
64 bytes from 192.64.119.194 (192.64.119.194): icmp_seq=5 ttl=55 time=168 ms
64 bytes from 192.64.119.194 (192.64.119.194): icmp_seq=6 ttl=55 time=162 ms
^C
--- plugins.volumio.org ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 12ms
rtt min/avg/max/mdev = 162.259/163.242/167.780/2.056 ms
volumio@volumio-pi3:~$
what do you get with :
volumio@volumio-rpi4:~$ volumio endpointstest
should be
TESTING REMOTE ENDPOINTS
https://google.com, 595 ms: OK
https://www.googleapis.com, 244 ms: OK
https://securetoken.googleapis.com, 328 ms: OK
https://myvolumio.firebaseio.com, 499 ms: OK
https://functions.volumio.cloud, 1185 ms: OK
https://oauth-performer.dfs.volumio.org, 363 ms: OK
https://browsing-performer.dfs.volumio.org, 499 ms: OK
http://cddb.volumio.org, 2377 ms: OK
https://functions.volumio.cloud, 1201 ms: OK
http://pushupdates.volumio.org, 380 ms: OK
http://plugins.volumio.org, 1803 ms: OK
https://database.volumio.cloud, 653 ms: OK
https://radio-directory.firebaseapp.com, 533 ms: OK
----------
REMOTE ENDPOINTS TEST OK, all Endpoints are reachable
----------Interesting
volumio@volumio-pi3:~$ volumio endpointstest
TESTING REMOTE ENDPOINTS
https://google.com, 566 ms: OK
https://www.googleapis.com, 247 ms: OK
https://securetoken.googleapis.com, 365 ms: OK
https://myvolumio.firebaseio.com, 435 ms: OK
https://functions.volumio.cloud, 979 ms: OK
https://oauth-performer.dfs.volumio.org, 376 ms: OK
https://browsing-performer.dfs.volumio.org, 397 ms: OK
http://cddb.volumio.org, 762 ms: OK
https://functions.volumio.cloud, 1098 ms: OK
http://pushupdates.volumio.org, 315 ms: OK
http://plugins.volumio.org, 5626 ms: FAILED
https://database.volumio.cloud, 640 ms: OK
https://radio-directory.firebaseapp.com, 397 ms: OK
----------
WARNING!!! Some remote endpoints cannot be reached!
Failing endpoints:
http://plugins.volumio.org, 397 ms
---------
Also… the URL is found immediately by the Pi.
volumio@volumio-pi3:~$ curl http://plugins.volumio.org
<a href='http://plugins.volumio.workers.dev/'>Found</a>.
volumio@volumio-pi3:~$
But it does again resolve to a different URL
Request time out is not necessarily bound to hickups. This is an ICMP message which you can turn off on a server. This to block tracert or ping commands.