I have put together the Pirate Radio and is now trying to get the VLC radio to work.
My first try was to follow the tutorial and everything went fine until it was time to launch the one-line installer.
It downloaded the packages (I think) and maybe doing some other stuff, but after the “Checking envirorment…” appears I got a message similar to this: We can´t connect to the Internet (or network). Check your network connection.
Fine, I double checked the networks settings and they seems ok. Tried again a few times (including a few reboots) but got the same message.
Next attempts was to reinstall, and now I picked the regular Rasbian version to have the GUI to help me.
Network settings once again looked ok and I was able to visit Google search page through Chromium.
Tried the same one-line installer command and had the same result. Same message appeared.
I then tried the mopidy installer and that worked, no error message and the setup went smootly.
It’s possible something in your network config (not necessarily on the Pi, but your router or otherwise) is blocking package install. Our install script relies on the package management features available on the Pi, and any problems those have with networking will break out installer too.
Try running these commands manually to see what happens:
The first command found three upgradable packages, second one upgraded them.
No issues at all.
I reinstalled Jessie Lite for a third attempt and it didn´t work. The Spotify installer seemed to work better first, but has issue too. Most of the packages are installed, but Mopidy doesn´t run at at startup. Manually starting give me a line in the the command log saying “No module named Spotipy”.
How do I find out if my router is the problem? What should I look for in the router admin menu?
I have a Netgear R6220 router if that helps.
Well that’s curious! From that output the check_network call should be working. Although the code looks like it would fail if there was >= 1% packet loss (assuming fractions of a percent are displayed as 0.1% etc). But then that still doesn’t really explain why the failure was repeatable. If you run the ping time a few times, do you experience any packet loss or failures?
Sorry to put you through the debug wringer, but this is a bit of a tricky one! You’re only the second person (as far as I know) to ever have a problem with the network check.
I don´t know exactly how this stuff works, but could it be so that the installer script doesn´t work since the adress where it y´should try to ping isn´t written out? Or does the VLC script get that data from somewhere else within the script?
That’s some good sleuthing. It looks like the VLC radio script might be running an earlier (or perhaps newer) version of the script. I checked the VLC radio command and it, indeed, fails spectacularly for me. This is weird, because I’m pretty certain I used exactly this script to install VLC radio on my Stretch setup for testing recently.
Looks like I’ve got a bit of detective work to do.