Skip to content

Cannot create second Filesystem provider in v2.7.4 #4801

@pereverti

Description

@pereverti

What version of Music Assistant has the issue?

2.7.4

How is the MA server installed?

Docker Container

Carefully read the Troubleshooting FAQ and confirm that

  • I have examined the logs and tried to resolve this issue
  • I have fixed any errors in the logs that relate to tags
  • I am not running MA across a VPN, VLAN, subnet, behind a firewall, or using local SSL or have any other complex network setup
  • I have disabled tool such as AdGuard, Pi-hole or pfSense and retested
  • I have checked my network setup to ensure mDNS/multicast is not being blocked
  • If using HA, I have confirmed the internal URL is set correctly
  • I have tried a wired connection for issues related to interrupted or poor playback quality
  • If the problem relates to a device then I have checked the device settings
  • If it is a frontend issue, I have tried a different widely used browser
  • I have reviewed the applicable player or music provider documentation
  • For voice problems, I have sought help elsewhere before returning here
  • For playback problems, I have recycled power to the physical device
  • I have tried restarting MA and rebooting the host

Have you reviewed the Open and Closed Issues and Discussions to resolve this yourself?

  • Yes

The problem

Version: 2.7.4
Previous working version: 2.7.3

Description

After upgrading from 2.7.3 to 2.7.4, it's impossible to create a second Filesystem music provider. The first provider can be created successfully, but attempting to create a second one fails with a Python AttributeError.

How to reproduce

Upgrade Music Assistant from 2.7.3 to 2.7.4
Go to Settings → Music Providers
Create a first Filesystem provider (e.g., /music) → ✅ Works fine
Try to create a second Filesystem provider (e.g., /youtube-music) → ❌ Fails with error

Error Message

'LocalFileSystemProvider' object has no attribute 'base_path'

Expected Behavior

Should be able to create multiple Filesystem providers pointing to different directories, as was possible in v2.7.3.

Actual Behavior

First Filesystem provider: Works
Second Filesystem provider: Fails with base_path AttributeError
This affects both new installations and upgrades where existing providers were deleted and recreated

Workaround

Downgrade to v2.7.3 - multiple Filesystem providers work correctly.

Environment

Music Assistant Version: 2.7.4
Installation method: Docker (ghcr.io/music-assistant/server:latest)
Platform: Unraid

Docker mount configuration:

/mnt/user/Musique → /music (ro)
/mnt/user/Divers/Youtube Downloader/Musique → /youtube-music (ro)

Music Providers

Filesystem provider

Player Providers

N/A

Full log output

N/A

Additional information

N/A

What version of Home Assistant Core (if used) are your running

2026.1.2

What type of installation are you running?

Home Assistant OS

On what type of hardware are you running?

Generic x86-64 (e.g. Intel NUC)

Have you included ALL of the information specified in the Troubleshooting FAQ or explained why you cannot

  • Yes

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions