I cannot login the accout to get the plugin

Help and Support
1

It said the network error. I do not have any network issue in my device. I can play the BBC radio.

2

Hi @Kingfisher, and welcome to the community.

We understand login issues can be frustrating, but we’ll need a clear set of details to assist you. Right now, simply saying “network error” doesn’t give us a starting point. We’re happy to help - but we’re not mind readers.

Please provide the following:

  1. Device and Volumio Version
    What device are you using (e.g., Raspberry Pi 3, PC, etc.)? Are you using the official Volumio image? Which version?

  2. Network Setup
    Are you using Wi-Fi or Ethernet? Do you have a stable connection to the internet from this device?

  3. Exact Error Behavior
    What are you doing when the error occurs? Logging into MyVolumio? Trying to install a plugin? Please describe step-by-step.

  4. Steps to Reproduce
    What should we do to trigger the same issue on our end?

  5. Debug Log
    Please send us a system log so we can inspect what’s going wrong. Here’s how:

    • In your browser, go to:
      http://volumio.local/dev
      or
      http://your-volumio-ip/dev (replace with your actual IP, e.g., http://192.168.1.54/dev)

    • Scroll down to “Send logs for bug report”

    • Enter a short description of your issue

    • Click Send

    • Once done, you’ll get a log link like http://logs.volumio.org/xxxxx - copy and paste it here.

    More detail here if needed:
    How to send a log link for a bug report

Kind Regards,

3

I already login but I can not see my device on myvolumio. The log is here:http://logs.volumio.org/volumio/zKZ3Iph.html

4

Hey @Kingfisher,

You’ve reported persistent MyVolumio login issues and plugin access failures. The logs you’ve shared contain sufficient evidence to conduct a structured diagnostic across all relevant areas. Below is a breakdown of what we know from your data, what it implies, and what next steps are possible.

1. Hardware Identification - Suggestive Evidence Only

From the ALSA playback device listing:

# aplay -l
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
card 0: b1 [bcm2835 HDMI 1], device 1: bcm2835 HDMI 1 [bcm2835 HDMI 1]
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]

This indicates:

  • Dual HDMI output (suggests Raspberry Pi 4 or Pi 400, since Pi 3 only has one HDMI).
  • bcm2835 Headphones device consistent with onboard analog out.

Conclusion: Hardware is almost certainly a Raspberry Pi 4, but this is not confirmed. No lscpu or /proc/cpuinfo was shared, so this must remain an inference, not a hard fact.

2. Connectivity Test Results - Partial Internet Reachability

From volumio endpointstest:

TESTING REMOTE ENDPOINTS
https://google.com, 5077 ms: FAILED
https://www.googleapis.com, 5069 ms: FAILED
https://securetoken.googleapis.com, 5068 ms: FAILED
https://myvolumio.firebaseio.com, 5069 ms: FAILED
https://functions.volumio.cloud, 850 ms: OK
https://oauth-performer.dfs.volumio.org, 1521 ms: OK
http://cddb.volumio.org, 1940 ms: OK
http://plugins.volumio.org, 5889 ms: FAILED

This confirms that the device can reach some internet resources, but fails to reach a consistent and critical set of endpoints - notably:

  • Google infrastructure (google.com, googleapis.com, firebaseio.com)
  • Volumio plugin server (plugins.volumio.org)
  • Authentication tokens (securetoken.googleapis.com)

Conclusion: This is a selective block, not a full disconnect. It likely stems from regional network filtering, DNS manipulation, TLS-level filtering, or transparent proxying/firewall behavior.

3. DNS Configuration - Unknown in This Case, But Critical

No logs show the current DNS configuration of the device. However, Volumio does provide a way to override DNS via UI.

How to check and override DNS:

From the Volumio Web UI:

  • Go to Settings → Network → DNS Settings
  • Enable “Custom DNS Server”
  • Suggested values:
    • Primary DNS: 208.67.222.222 (OpenDNS)
    • Secondary DNS: 208.67.220.220
    • Alternatively: 1.1.1.1 and 1.0.0.1 (Cloudflare)

If DNS interception is occurring (common in filtered networks), switching to these addresses may allow resolution to bypass local DNS poisoning or redirection.

Recommendation: Check whether DNS override is in effect. If not, enable it and reboot. Then retest connectivity via http://your-volumio-ip/dev → Send log.

4. MyVolumio Login Errors - Confirmed from System Log

From repeated runtime logs:

error: MyVolumio got a network error: A network error (such as timeout, interrupted connection or unreachable host) has occurred.
info: Retrying Login Due to Network Error
info: MyVolumio login type: Token

Conclusion: These messages confirm Volumio is attempting token-based login, but the request cannot complete. This correlates directly with the failed Google and Firebase endpoints observed above.

5. RTC Absence and Time Synchronization Failure

From startup logs:

volumio-time-update-util: Fetching time from Volumio...
volumio-time-update-util: Date not found in response
ntpd: Unexpected origin timestamp 0xebb0112f...

These errors are indicative of:

  • No hardware Real-Time Clock (RTC), as found in Raspberry Pi by default
  • Failed attempts to fetch time via NTP or cloud-based endpoints

If time cannot be synchronized:

  • TLS certificates appear expired or not-yet-valid
  • HTTPS endpoints such as plugins.volumio.org, Firebase, and others may reject the connection silently

Conclusion: Incorrect system time due to failed NTP sync is a likely contributing factor to MyVolumio and plugin access failures.

Remediation:

  • Use a network that allows NTP access.
  • Manually SSH into the device and use:
    sudo date -s "YYYY-MM-DD HH:MM:SS"
    to set time as a temporary fix (not persistent across reboots unless NTP works or RTC is added).

6. Regional Filtering - Strongly Suggested by Timezone and Endpoint Patterns

From system time in the log:

Tue Apr 01 2025 01:00:57 GMT+0800 (China Standard Time)

This confirms the system is operating under UTC+8, which aligns with China Standard Time.

Combined with:

  • Blocked Google services
  • Broken Firebase connectivity
  • Lack of plugin availability

Conclusion: These behaviors are fully consistent with the known restrictions imposed by the Great Firewall of China, which blocks or filters access to Google services, cloud infrastructure, and certain CDNs. This is the most likely root cause of your issues.

7. Remediation Options - Tested and Practical

Option 1: Configure DNS via UI
See section 3. Ensure DNS override is enabled with global, unfiltered resolvers.

Option 2: Test with Alternative Network
Temporarily connect the Volumio device to a mobile hotspot, VPN-protected router, or any other unrestricted network. This can confirm whether the issues are network-induced.

Option 3: Manual Plugin Installation
If the plugin store is inaccessible:

  1. Download plugin ZIP from another device:
    https://github.com/volumio/volumio-plugins
  2. Transfer it to Volumio via USB or SCP.
  3. SSH into Volumio and run:
    volumio plugin install

Option 4: Use VPN Gateway or Tunnel
Volumio does not include a VPN client by default, but:

  • You can run it behind a router that routes traffic via VPN
  • Or use a proxy or tunnel that bypasses regional restrictions

Option 5: Force Time Sync Temporarily
Use manual time setting or local NTP relay if public NTP servers are filtered. This may resolve TLS validation failures that block plugin or login requests.

Certainly. Here’s a clean, injection-ready subsection you can paste directly into your response. It provides manual DNS testing steps via SSH from a Volumio system, with clear commands and expected outcomes:

8. How to Manually Test DNS from Volumio via SSH

To verify that your Volumio device can resolve hostnames correctly - and to check whether DNS filtering is in effect - you can perform the following tests via SSH:

1. Open an SSH session to your Volumio device:
If you haven’t already enabled SSH, do so via http://volumio.local/dev or your device’s IP.

Then connect from a terminal:

ssh volumio@<your-volumio-ip>

Default password: volumio

2. Test DNS resolution with dig or nslookup:

If dig is available:

dig plugins.volumio.org

Alternatively:

nslookup plugins.volumio.org

Expected output should include:

  • A valid IP address in the “ANSWER SECTION”
  • A short query time (under 100ms)
  • No SERVFAIL or REFUSED errors

3. Test resolution of a known blocked domain (for comparison):

dig google.com

If this hangs or returns no answer while other domains resolve, it’s likely DNS filtering or manipulation is occurring.

4. Confirm which DNS server is currently in use:

cat /etc/resolv.conf

This shows which nameserver is actively being queried. If this lists a local router IP (e.g., 192.168.1.1), and DNS queries are failing, it’s worth overriding DNS via the Volumio UI.

5. Optional - Test fallback resolution using a direct DNS server:

dig @1.1.1.1 plugins.volumio.org

This forces a DNS lookup using Cloudflare, bypassing your default resolver. Successful resolution here indicates local DNS interception is the problem.

Closing Summary

You are not facing a bug in Volumio. Based on the logs, you are facing a network environment that blocks or interferes with essential cloud endpoints, combined with a lack of hardware RTC and failed time synchronization.

The correct diagnostic approach has already yielded the following:

  • Cloud service access failure is real and confirmed
  • Time sync is broken, further blocking TLS-dependent services
  • DNS configuration is unknown but critical to verify
  • Workarounds include VPN, offline plugin install, DNS override, or manual time setting

Please confirm your DNS settings and attempt one of the proposed remediations. Then either retry the MyVolumio login or submit a full system log for further inspection.

Kind Regards,