# Mopidy local error

**URL:** <https://discourse.mopidy.com/t/mopidy-local-error/5809>\
**Category:** Help and support\
**Created:** [August 28, 2023, 6:52pm UTC](https://discourse.mopidy.com/t/mopidy-local-error/5809 "2023-08-28T18:52:49Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mbh181](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/mbh181/32/1931_2.png) [@mbh181](https://discourse.mopidy.com/u/mbh181)\
**Post date:** [August 28, 2023, 6:52pm UTC](https://discourse.mopidy.com/t/mopidy-local-error/5809/1 "2023-08-28T18:52:49Z")

</div>

hi - trying to scan local folder on rpi  
have modified the conf. file as follows  
running mopidy as service.

[local]  
media\_dir = /home/disk\_mount/Music

but get the following error when running sudo mopidy local scan

WARNING 2023-08-28 19:49:41,031 [13732:MainThread] mopidy. **main**  
Found local configuration errors. The extension has been automatically disabled:  
WARNING 2023-08-28 19:49:41,032 [13732:MainThread] mopidy. **main**  
local/media\_dir must be set.  
WARNING 2023-08-28 19:49:41,033 [13732:MainThread] mopidy. **main**  
Please fix the extension configuration errors or disable the extensions to silence these messages.

any thoughts ?

---

<div class="post-metadata">

**Author:** ![jjok](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/jjok/32/448_2.png) [@jjok](https://discourse.mopidy.com/u/jjok)\
**Post date:** [August 29, 2023, 7:20pm UTC](https://discourse.mopidy.com/t/mopidy-local-error/5809/2 "2023-08-29T19:20:40Z")

</div>

As you’re saying that you’ve set that value in your config file, I would assume that it isn’t reading that config file.

This is how to see what the effective configuration is:  
[https://docs.mopidy.com/en/latest/config/#view-effective-configuration](https://docs.mopidy.com/en/latest/config/#view-effective-configuration)

This tells you how to find the right config file to edit:  
[https://docs.mopidy.com/en/latest/config/#configuration-file-location](https://docs.mopidy.com/en/latest/config/#configuration-file-location)

---

<div class="post-metadata">

**Author:** ![wasmgrr](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/wasmgrr/32/2476_2.png) [@wasmgrr](https://discourse.mopidy.com/u/wasmgrr)\
**Post date:** [January 17, 2024, 1:02am UTC](https://discourse.mopidy.com/t/mopidy-local-error/5809/3 "2024-01-17T01:02:59Z")

</div>

I have a similar error and am editing the correct config file because other settings have been applied…  
Did you find a solution or does anyone else have a suggestion?

---

<div class="post-metadata">

**Author:** ![mbh181](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/mbh181/32/1931_2.png) [@mbh181](https://discourse.mopidy.com/u/mbh181)\
**Post date:** [January 17, 2024, 8:03am UTC](https://discourse.mopidy.com/t/mopidy-local-error/5809/4 "2024-01-17T08:03:20Z")

</div>

It’s a while back now but i think for me it was readong the wrong config file as mopidy was set up as a service on my rpi.

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [January 17, 2024, 9:37am UTC](https://discourse.mopidy.com/t/mopidy-local-error/5809/5 "2024-01-17T09:37:00Z")

</div>

This always end up being an issue relating to the wrong config file. There are two ways to run Mopidy and they each have a different file and different commands as per [Running — Mopidy 3.4.2 documentation](https://docs.mopidy.com/en/latest/running/)

Please clarify which way you are running Mopidy and then use the appropriate command to display the effective config and provide that here.

---

<div class="post-metadata">

**Author:** ![system](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/system/32/1_2.png) [@system](https://discourse.mopidy.com/u/system)\
**Post date:** [July 17, 2024, 9:37pm UTC](https://discourse.mopidy.com/t/mopidy-local-error/5809/6 "2024-07-17T21:37:41Z")

</div>

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.