No access to musicbox.local or via ip address

Pi MusicBox
1

Hello I have done a new install but have no web access to the pi!
Not via musicbox.local or via ip address? SSH is working and i can login
After cmd mopdiy i get the below output
Error code is address already in use ???
Any thing I am doing wrong?

root@MusicBox:~# mopidy
INFO Starting Mopidy 1.1.2
INFO Loading config from builtin defaults
INFO Loading config from command line options
INFO Creating dir /root/.cache/mopidy
INFO Creating dir /root/.config/mopidy
INFO Creating dir /root/.local/share/mopidy
INFO Loading config from builtin defaults
INFO Loading config from command line options
INFO Creating file /root/.config/mopidy/mopidy.conf
INFO Initialized /root/.config/mopidy/mopidy.conf with default config
INFO Enabled extensions: file, stream, spotify_tunigo, podcast-gpodder, http-kuechenradio, podcast-itunes, softwaremixer, moped, musicbox_webclient, websettings, tunein, mopify, somafm, internetarchive, mpd, http, podcast, alsamixer, mobile, local-sqlite, youtube, simple-webclient, m3u, audioaddict
INFO Disabled extensions: spotify, gmusic, scrobbler, subsonic, spotify_web, dirble, local, soundcloud
WARNING Found dirble configuration errors, the extension has been automatically disabled:
WARNING dirble/api_key must be set.
WARNING Found gmusic configuration errors, the extension has been automatically disabled:
WARNING gmusic/username must be set.
WARNING gmusic/password must be set.
WARNING Found local configuration errors, the extension has been automatically disabled:
WARNING local/media_dir must be set.
WARNING Found scrobbler configuration errors, the extension has been automatically disabled:
WARNING scrobbler/username must be set.
WARNING scrobbler/password must be set.
WARNING Found soundcloud configuration errors, the extension has been automatically disabled:
WARNING soundcloud/auth_token must be set.
WARNING Found spotify configuration errors, the extension has been automatically disabled:
WARNING spotify/username must be set.
WARNING spotify/password must be set.
WARNING Found spotify_web configuration errors, the extension has been automatically disabled:
WARNING spotify_web/client_secret must be set.
WARNING spotify_web/client_id must be set.
WARNING Found subsonic configuration errors, the extension has been automatically disabled:
WARNING subsonic/username must be set.
WARNING subsonic/hostname must be set.
WARNING subsonic/ssl must be set.
WARNING subsonic/password must be set.
WARNING subsonic/port must be set.
WARNING Please fix the extension configuration errors or disable the extensions to silence these messages.
INFO Starting Mopidy mixer: SoftwareMixer
INFO Starting Mopidy audio
INFO Starting Mopidy backends: StreamBackend, M3UBackend, FileBackend, YouTubeBackend, TuneInBackend, SpotifyTunigoBackend, SomaFMBackend, PodcastBackend, InternetArchiveBackend, AudioAddictBackend
INFO Audio output set to "autoaudiosink"
INFO Creating dir /root/.local/share/mopidy/m3u
INFO Loaded 0 M3U playlists from /root/.local/share/mopidy/m3u
INFO Starting Mopidy-Podcast directories: FeedsDirectory, iTunesDirectory, GPodderDirectory
INFO Refreshing Mopidy-Podcast directories
INFO AudioAddict: premium streams not available on your account
INFO Loaded 35 SomaFM channels
INFO Starting Mopidy core
INFO Starting Mopidy frontends: MpdFrontend, HttpFrontend, QueueManagerFrontend
ERROR Frontend (MpdFrontend) initialization error: MPD server startup failed: [Errno 98] Address already in use
ERROR Frontend (HttpFrontend) initialization error: HTTP server startup failed: [Errno 98] Address already in use

2

Mopidy is already running in the background so if you then go and also manually run Mopidy yourself you’ll now have two instances running. The second instance will not be able to start the Web/MPD servers because the address/port is already being used by the first instance. You can see if mopidy is already running as a background service with service mopidy status. You can check the log files at /var/log/mopidy/mopidy.log to see if there are any errors when Mopidy starts. You can also check for general Musicbox startup problems in /var/log/musicbox_startup.log. Both of those logs should report if the Web server successfully started or not.

There are lots of configuration errors reported in your output above. Did you make some manual changes to settings.ini? You may have made a mistake when doing so, perhaps near the Dirble section?