MyVolumio is not working

Help and Support
1

MyVolumio has stopped work. I’m able to access to myvolumio(dot)org with my PREMIUM account.
When I go to myvolumio(dot)org/playback a only a black screen appare (there’s shadows of the volumio interface) and a rotating volumio logo in the middle.

Using developer tools of the browser, I can see many errors, the first one is :
‘https://8lhdrmxti4ftxfdgqvx7qwr4ixf1-5573fce343dd19daa0f3e314cbe69bae.eu4.myvolumio.org/partnerlogo’ from origin ‘https://myvolumio.org’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. If an opaque response serves your needs, set the request’s mode to ‘no-cors’ to fetch the resource with CORS disabled.

System Information

  • OS info

  • Version of Volumio: 3.785

  • Hostname: volumio

  • Kernel: 6.6.62-v7+

  • Governor: performance

  • Uptime: 0 days, 0 Hrs, 43 Minutes, 13 Seconds

  • Network info

  • Interface: eth0

  • IP Address: 192.168.1.6

  • MAC Address: xx:xx:xx:xx:xx:xx

  • Type: wired

  • Speed: 1000Mb/s

  • Audio info

  • Hw audio configured: Allo BOSS

  • Mixer type: Hardware

  • Number of channels: 2

  • Supported sample rate: 22050 44100 48000 88200 96000 176400 192000 384000

  • Board info

  • Manufacturer: Raspberry Pi Foundation

  • Model: Raspberry Pi 3 Model B Plus Rev 1.3 Raspberry Pi / 3B+ - 1.3 /

  • Version: a020d3 / 3B+ - 1.3

  • Firmware Version: Nov 11 2024 15:50:32 version 903570ba72a9e117f92e5499de439f59dd96e417 (clean) (release) (start)

  • CPU info

  • Brand: BCM2837

  • Speed: 1.4 GHz

  • Family: Cortex-A53

  • Model: 4

  • Number of cores: 4

  • Physical cores: 4

  • Average load: 12%

  • Temperature: 55°C

  • Memory info

  • Memory: 890632 Ko

  • Free: 96760 Ko

  • Used: 793872 Ko

  • Software info

  • Mpd version: Music Player Daemon 0.23.15 (0.23.15)

  • Storage info

  • INTERNAL storage - Size: 56440Mo

  • Used: 611Mo

  • Available for storage: 52914Mo (94%)

2

Please reboot the rPi and send a log after fully boot/

3

I’m very sorry.
Now, it seems, it start work properly.

Anyway, I attach the current log file
log.txt (293.0 KB)

and the previous one, when it doesn’t work
log2.txt (235.7 KB)

In this log2.txt I can find those strange messages:
Jan 02 01:04:44 volumio nmbd[806]: [2025/01/02 01:04:44.968413, 0] …/source3/nmbd/nmbd_namequery.c:109(query_name_response)
Jan 02 01:04:44 volumio nmbd[806]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.6 for name WORKGROUP<1d>.
Jan 02 01:04:44 volumio nmbd[806]: This response was from IP 192.168.1.12, reporting an IP address of 192.168.1.12.

I don’t know what is it, but 192.168.1.12 is another raspberry in my home network where is running my IOT infrastructure (Home Assistant, some custom made nodejs applications (that also use Socket.io), MQTT server and a reverse proxy using nginx. Obviously routers has port forwarding for port 80 and 443 to this raspberry.

4

I get the impression that the date/time was not updated yet by the network.
If the date/time offset is to big, myvolumio will not connect.

Volumio will run a small scan do find other Volumio devices in order to use “Play here”, “Grouping” and “Switch device”.

Good to here it’s all up and running again.