Can't access mopidy over network

General
1

hi, I just installed mopidy on my ubuntu machine, it works fine on ubuntu i can access 6680 port, but it’s not accessible on other devices on the same network,
when i try to access ubuntuIP:6680 i get connection_refused from browser,
mopidy service status :
● mopidy.service - Mopidy music server
Loaded: loaded (/lib/systemd/system/mopidy.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2017-12-13 20:29:18 UTC; 3s ago
Process: 12215 ExecStartPre=/bin/chown mopidy:audio /var/cache/mopidy (code=exited, status=0/SUCCESS)
Process: 12209 ExecStartPre=/bin/mkdir -p /var/cache/mopidy (code=exited, status=0/SUCCESS)
Main PID: 12220 (mopidy)
CGroup: /system.slice/mopidy.service
└─12220 /usr/bin/python /usr/bin/mopidy --config /usr/share/mopidy/conf.d:/etc/mopidy/mopidy.conf

Dec 13 20:29:20 tinkerboard mopidy[12220]: INFO Starting Mopidy audio
Dec 13 20:29:20 tinkerboard mopidy[12220]: INFO Starting Mopidy backends: StreamBackend, M3UBackend, FileBackend, LocalBackend
Dec 13 20:29:20 tinkerboard mopidy[12220]: INFO Audio output set to "autoaudiosink"
Dec 13 20:29:20 tinkerboard mopidy[12220]: INFO No local library metadata cache found at /var/lib/mopidy/local/library.json.gz. Please run mopidy local scan to index your local music library. If you do
Dec 13 20:29:20 tinkerboard mopidy[12220]: INFO Loaded 0 local tracks using json
Dec 13 20:29:20 tinkerboard mopidy[12220]: INFO Starting Mopidy core
Dec 13 20:29:20 tinkerboard mopidy[12220]: INFO Starting Mopidy frontends: MpdFrontend, HttpFrontend
Dec 13 20:29:20 tinkerboard mopidy[12220]: INFO MPD server running at [::ffff:127.0.0.1]:6600
Dec 13 20:29:20 tinkerboard mopidy[12220]: INFO HTTP server running at [::ffff:127.0.0.1]:6680
Dec 13 20:29:20 tinkerboard mopidy[12220]: INFO Starting GLib mainloop

and also mopidy config :
[mpd]
enabled = true
hostname = 127.0.0.1
port = 6600
password =
max_connections = 20
connection_timeout = 60
zeroconf = Mopidy MPD server on $hostname
#command_blacklist =
# listall
# listallinfo
default_playlist_scheme = m3u

[http]
enabled = true
hostname = 0.0.0.0
port = 6680
#static_dir =
zeroconf = Mopidy HTTP server on $hostname
2

See the warning at https://docs.mopidy.com/en/latest/ext/http/

3

thanks for quick reply, i’m using mopidy as a service so i was editing wrong config file, but now i can’t access local files from mpdroid android, mopidy local scan finds songs successfully but they don’t show up in the app

4

What about a http client? Mpdroid is unmaintained and I don’t think it still supports our non-standard MPD implementation. A good alternate mpd client for android is malp.

5

I’ll also add you obviously need to run the scan as a service too. When mopidy starts it should print how many songs it found in your local library database to the log file.

6

Hi, my Mopidy server is working well. i can access it with my browser and audio is good. However I am unable to access it with any Droid client. I’ve tried MALP as well as MPD Remote without success.

As I mentioned above the server IP 10.0.0.1:6680 is accessible via browser from LAN devices and I’m able to play local media files via the web client in Chrome (on laptop and Droid phone) using the 3.5 analog audio port however the Driod apps refuse to connect on the IP and Port above. Any advise? I feel like this should just work but no luck. :frowning:

7

Port 6680 is the Mopidy http server port. The MPD server runs on port 6600, this is usually the default in mpd apps. Mpd apps cannot connect on 6680. Also make sure you’ve set the mpd hostname config setting to 0.0.0.0 (just like the http hostname) .