Same problem with the previous version of Volumio.
Any idea? can you tell what could be wrong with the HW and if it can be fixed
Do you have a pihole in your network?
I think that the problem not the os
But position in your network, wired works best for first install
Dns could be still a thing
How is the struture of your network?
what is a pihole?
Pihole is a pi that keeps adv. Oway from your phone and pc ect. Ad blocker
That could mess with volumio some times.
OK, no pi-hole. I have a primary router (where fiber comes in) that runs the DHCP. Also I have a secondary wifi repater, connected via wire to the router. The RPI is conncted via wire to the repeater.
Add volumio on your primary router if you can wired this should give a good stable connection.
And set your pi up with a static ip ( handy so you know what ip you have. )
I already had the fixed IP on the pi. I will try connecting to the primary router tomorrow.
Anyway, connecting via SSH, i can resolve volumio.local to 127.0.0.1
127.0.0.1 is local host that is not the ip of your pi on the outside.
It should be if you have a 192.168.1.x if your router is set on the 192 range
Some are on 10.x.x.x i don’t know what kind of router you have.
Hi Richetto,
Please SSH to your Volumio installation and enter the following, please paste back the results:
volumio endpointstest
volumio@volumio-rpi:~$ volumio endpointstest
TESTING REMOTE ENDPOINTS
https://google.com, 313 ms: OK
https://www.googleapis.com, 168 ms: OK
https://securetoken.googleapis.com, 284 ms: OK
https://myvolumio.firebaseio.com, 377 ms: OK
https://functions.volumio.cloud, 813 ms: OK
https://oauth-performer.dfs.volumio.org, 343 ms: OK
https://browsing-performer.dfs.volumio.org, 295 ms: OK
http://cddb.volumio.org, 740 ms: OK
https://functions.volumio.cloud, 840 ms: OK
http://pushupdates.volumio.org, 206 ms: OK
http://plugins.volumio.org, 1140 ms: OK
https://database.volumio.cloud, 539 ms: OK
https://radio-directory.firebaseapp.com, 277 ms: OK
----------
REMOTE ENDPOINTS TEST OK, all Endpoints are reachablemmmm, running out of suggestions:
- Network appears to be ok
- Raspbian boots without issues
- Only Volumio ssems to get into a loop
Hello, some updates.
Today I restarted the network routers in my net and Volumo 3.324 went back working fine. Upgraded to 3.378 and the restart issue was there again.
So I reflashed the card with 3.324 and it did not work. Restarted the routers and it went back to normal.
Apparently version 3.378 is doing someting to the network router/DNS that prevents Volumio to work properly.
Have you ever scanned your network, to be sure that no IP has a double entry.
As you’re using a WiFi extender, which I assume, indeed only as an extender for you main WiFi network and has no DHCP enabled?
Are V3.324 and 3.378 running on the same IP?
@Richetto It could be that if you have mutliple routers that one of them should be in bridge mode ?
If they are behind one a other.
I have 2 routers one of my isp and one of my own first is in bridge mode
And the second one is normal.
The wifi extender is in bridge mode, Only 1 DHCP in the network. The DHCP is set to assign the same IP to a given physical address. The RPI always gets 192.168.1.200.
This i what I used for the tests.
So yes, the 2 volumio versions had the same IP
can you release 192.168.1.200 from the router, restart the router, and assign the MAC address of the pi back to 192.168.1.200.
It’s some weird behavior.
1 Like
Couldn’t he just set one or both on static ip and not the same ip and not use the dhcp of the pi?
I believe that I just said that.
Ps. i said that 23 hrs ago already to him…
Hi, this might be due to the new Chromecast and SONOS search.
In the past, we had this issue when some “non-compliant” network devices were found. So, to solve this issue, we really need logs from you.
If you can connect via SSH and do:
node /volumio/logsubmit.js
You will receive something like:
{"status":"OK","link":"http://logs.volumio.org/XXXXXXXl"}
Please copy and past this last line here. That will help us troubleshoot