Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Available Plugins Empty #1995

Open
cmbroth opened this issue Aug 23, 2020 · 1 comment
Open

Available Plugins Empty #1995

cmbroth opened this issue Aug 23, 2020 · 1 comment

Comments

@cmbroth
Copy link

cmbroth commented Aug 23, 2020

On a new install of version 2.806, the available plugin list is empty.

Platform: Raspberry pi 4 + HifiBerry Amp2

When updating the plugin list, the plugin manager attempts to grab a json file from following url:
http://plugins.volumio.org/plugins/volumio/armhf/plugins.json

That host redirects to http://plugins.volumio.workers.dev/plugins/volumio/armhf/plugins.json

plugins.volumio.workers.dev resolves to the following addresses:
104.18.33.211
104.18.32.211
172.67.153.54

If 172.67.153.54 is used, the request times out and an error message appears in the volumio logs. Volumio does not retry with one of the other ip address. Below is the output of a wget request.

wget http://plugins.volumio.org/plugins/volumio/armhf/plugins.json
--2020-08-23 12:27:39-- http://plugins.volumio.org/plugins/volumio/armhf/plugins.json
Resolving plugins.volumio.org (plugins.volumio.org)... 192.64.119.194
Connecting to plugins.volumio.org (plugins.volumio.org)|192.64.119.194|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://plugins.volumio.workers.dev/plugins/volumio/armhf/plugins.json [following]
--2020-08-23 12:27:40-- http://plugins.volumio.workers.dev/plugins/volumio/armhf/plugins.json
Resolving plugins.volumio.workers.dev (plugins.volumio.workers.dev)... 172.67.153.54, 104.18.32.211, 104.18.33.211, ...
Connecting to plugins.volumio.workers.dev (plugins.volumio.workers.dev)|172.67.153.54|:80... failed: Connection timed out.
Connecting to plugins.volumio.workers.dev (plugins.volumio.workers.dev)|104.18.32.211|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 20684 (20K) [application/json]
Saving to: ‘plugins.json’

Checking from a different host on another network results in the following:

wget http://plugins.volumio.org/plugins/volumio/armhf/plugins.json
--2020-08-23 17:29:43-- http://plugins.volumio.org/plugins/volumio/armhf/plugins.json
Resolving plugins.volumio.org (plugins.volumio.org)... 192.64.119.194
Connecting to plugins.volumio.org (plugins.volumio.org)|192.64.119.194|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://plugins.volumio.workers.dev/plugins/volumio/armhf/plugins.json [following]
--2020-08-23 17:29:44-- http://plugins.volumio.workers.dev/plugins/volumio/armhf/plugins.json
Resolving plugins.volumio.workers.dev (plugins.volumio.workers.dev)... 172.67.153.54, 104.18.32.211, 104.18.33.211
Connecting to plugins.volumio.workers.dev (plugins.volumio.workers.dev)|172.67.153.54|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 20684 (20K) [application/json]
Saving to: ‘plugins.json’

So for some reason, my system is unable to download from 172.67.153.54 while the other two hosts work fine.

Possible improvement:
Update the plugin manager so that additional ip addresses are tried after a time out error.

Thanks,
Chris.

@sikaiser
Copy link

sikaiser commented Mar 31, 2021

Can we somehow bump this? It's still the same in April '21.

Edit: It seems that I was having a different issue. Will document it here for anyone else who comes across it. I am running volumio on a raspberry zero w, which uses Wifi. Apparently there is an issue with the wifi driver that causes it to not set the time and date correctly on the device. This leads to issues with https certificates.

The solution that worked for me (as per https://community.volumio.org/t/solved-unable-to-set-accurate-time-time-zone/6928):

timedatectl set-ntp true
sudo dpkg-reconfigure tzdata
sudo reboot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants