Daapd Container not starting

LSIO Discussion Container Support
1

Dear team
first and most important: I would like to thank you for your work. And I hope you are all healthy.

I would very much like you to provide some help with the linuxserver/ daapd container.

System: Synology NAS DS918+; Port 3689 open (within the Docker, also for the NAS itself)

Problem: I can’t access the Web-Interface. If I address the daapd-Server on my LAN via IP 123.123.123.123:3689 I get the feedback: “Forbidden”

I haven’t changed any information within the log-file within the config - folder?!? Should I?

The Docker-protocol indicates that the User has no "ownership on the log file - But the PUID is used also for other dockers and is working. So please could you help with your advise?

Please find enclosed part of the docker protocol:
18:32:12 User uid: 12_fake_34 stdout
18:32:12 User gid: 12_fake_34 stdout

18:32:12 [cont-init.d] 10-adduser: exited 0. stdout
18:32:12 [cont-init.d] 30-dbus: executing… stdout
18:32:13 [cont-init.d] 30-dbus: exited 0. stdout
18:32:13 [cont-init.d] 40-config: executing… stdout
18:32:13 [cont-init.d] 40-config: exited 0. stdout
18:32:13 [cont-init.d] 99-custom-files: executing… stdout
18:32:13 [custom-init] no custom files found exiting… stdout
18:32:13 [cont-init.d] 99-custom-files: exited 0. stdout
18:32:13 [cont-init.d] done. stdout
18:32:13 [services.d] starting services stdout
18:32:13 [services.d] done. stdout
18:32:14 Failed to set ownership on logfile: Operation not permitted stdout
18:32:14 [ LOG] main: Forked Media Server Version 27.1 taking off stdout
18:32:14 [ LOG] main: Built with: stdout
18:32:14 [ LOG] main: - ffmpeg stdout
18:32:14 [ LOG] main: - iTunes XML stdout
18:32:14 [ LOG] main: - LastFM stdout
18:32:14 [ LOG] main: - Chromecast stdout
18:32:14 [ LOG] main: - MPD stdout
18:32:14 [ LOG] main: - Device verification stdout
18:32:14 [ LOG] main: - Websockets stdout
18:32:14 [ LOG] main: - ALSA stdout
18:32:14 [ LOG] main: - Webinterface stdout
18:32:14 [ LOG] main: mDNS init stdout
18:32:14 [ LOG] mdns: Avahi state change: Client connecting stdout
18:32:14 [ LOG] db: Configured to use database file ‘/config/dbase_and_logs/songs3.db’ stdout
18:32:14 [ LOG] db: Now vacuuming database, this may take some time… stdout
18:32:14 [ LOG] db: Database OK with 2 active files and 6 active playlists stdout
18:32:14 [ LOG] mdns: Failed to create service browser: Bad state stdout
18:32:14 [ LOG] raop: Could not add mDNS browser for AirPlay devices stdout
18:32:14 [ LOG] mdns: Failed to create service browser: Bad state stdout
18:32:14 [ LOG] cast: Could not add mDNS browser for Chromecast devices stdout
18:32:14 Found user ‘avahi’ (UID 86) and group ‘avahi’ (GID 86). stdout
18:32:14 Successfully dropped root privileges. stdout
18:32:14 avahi-daemon 0.7 starting up. stdout
18:32:14 WARNING: No NSS support for mDNS detected, consider installing nss-mdns! stdout
18:32:14 Loading service file /etc/avahi/services/sftp-ssh.service. stdout
18:32:14 Loading service file /etc/avahi/services/ssh.service. stdout
18:32:14 Joining mDNS multicast group on interface eth0.IPv4 with address 172.17.0.6. stdout
18:32:14 New relevant interface eth0.IPv4 for mDNS. stdout
18:32:14 Network interface enumeration completed. stdout
18:32:14 Registering new address record for 172.17.0.6 on eth0.IPv4. stdout
18:32:15 [ LOG] mdns: Failed to create service browser: Bad state stdout
18:32:15 [FATAL] remote: Could not browse for Remote services stdout
18:32:15 [FATAL] main: Remote pairing service failed to start
stdout
18:32:15 [ LOG] main: MPD deinit stdout
18:32:15 [ LOG] main: HTTPd deinit stdout
18:32:15 [ LOG] scan: Bulk library scan completed in 0 sec stdout
18:32:15 Server startup complete. Host name is linuxserver-daapd1.local. Local service cookie is 2008276264. stdout
18:32:15 [ LOG] lib: Library init scan completed in 1 sec (0 changes) stdout
18:32:16 [ LOG] main: Player deinit stdout
18:32:16 Service “linuxserver-daapd1” (/etc/avahi/services/ssh.service) successfully established. stdout
18:32:16 Service “linuxserver-daapd1” (/etc/avahi/services/sftp-ssh.service) successfully established. stdout
18:32:16 [ LOG] main: Library scanner deinit stdout
18:32:16 [ LOG] main: Cache deinit stdout
18:32:16 [ LOG] main: Worker deinit stdout
18:32:16 [ LOG] main: Database deinit stdout
18:32:16 [ LOG] main: mDNS deinit stdout
18:32:16 [ LOG] main: Exiting. stdout
18:32:17 Failed to set ownership on logfile: Operation not permitted stdout
18:32:17 [ LOG] main: Forked Media Server Version 27.1 taking off stdout
18:32:17 [ LOG] main: Built with: stdout
18:32:17 [ LOG] main: - ffmpeg stdout
18:32:17 [ LOG] main: - iTunes XML stdout
18:32:17 [ LOG] main: - LastFM stdout
18:32:17 [ LOG] main: - Chromecast stdout
18:32:17 [ LOG] main: - MPD stdout
18:32:17 [ LOG] main: - Device verification stdout
18:32:17 [ LOG] main: - Websockets stdout
18:32:17 [ LOG] main: - ALSA stdout
18:32:17 [ LOG] main: - Webinterface stdout
18:32:17 [ LOG] main: mDNS init stdout
18:32:17 [ LOG] mdns: Avahi state change: Client running stdout
18:32:17 [ LOG] db: Configured to use database file ‘/config/dbase_and_logs/songs3.db’ stdout
18:32:17 [ LOG] db: Now vacuuming database, this may take some time… stdout
18:32:17 [ LOG] db: Database OK with 2 active files and 6 active playlists stdout
18:32:18 [ LOG] scan: Bulk library scan completed in 1 sec stdout
18:32:18 [ LOG] lib: Library init scan completed in 1 sec (0 changes)

2

Please supply the information about the deployment.

You should also use a local IP range instead of public IP addresses on your LAN.

3

Dear saarg

sorry, I don’t understand your feedback. Could you please be a bit more precise on what I should do? Please think of me as an IT-amateur who doesn’t understand to technical explanations: For instance I don’t know what informations you need (==> deployment - what part of my implementation is it?)?
Nor do I understand which IP I should use on my LAN? Please enlighten: what do you want me to do by saying “use a local IP range instead of public IP addresses on your LAN”?

Yours

4

How you deployed the container means how you installed it with all the options and variables and paths.

Google private IP address range for IP addresses that you can use on your local network.
The IP you posted, 123.123.123.123 is a public address that belongs to China unicom.

5

Dear saarg
Thanks for the clarification.

Concerning my deployment / set up:
Container-set up

  • Volume
    /config = docker/daapd_docker/config
    /music = docker/daapd_docker/music

  • Port
    local port = 3689 // Container-Port = 3689 // Typ: TCP

  • Environment
    Path = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin (unchanged from container)
    PS1 = $(whoami)@$(hostname):$(pwd)$ (unchanged from container)
    HOME = /root (unchanged from container)
    TERM = xterm (unchanged from container)
    PGID = 12345 (this is NOT the PGID - but it has 5 numbers…)
    PUID = 1234 (this is NOT the PUID - but it has 4 numbers…)

Synology DSM setup
I researched the PGID and PUID for the USER docker and the User-Group docker for another docker - and that one is working - so I guess they are correct

  • Goupe “docker” with read / write access for the folder /docker [relevant for PGID I guess]

  • User “docker” with read / write access for the folder /docker; member of the Group “docker” [relevant for the PUID I guess]

  • Synology-NAS-Firewall: including port 3689 in the settings for the Firewall
    Within the settings for the Synology NAS it is required to set information for security. DSM / security / Firewall: Firewall active! Port 3689 for application “Docker linuxserver-daapd1” active

  • Router:
    Internal / privat IP settings: Actually I might have been a bit slippy on my internal / privat IP. “123.123.123.123” is not the privat IP for the Synology NAS. It looks more like IP “192.168.xyz.ab”. The Synology NAS has a fixed internal IP. This is defined within the router-settings.
    I also included port-settings within the router-settings for the docker “linuxserver-daapd1”, but I guess this is not relevant for the LAN access via browser and internal/privat IP?!

I hope this informations are helping and are sufficient to solve the problem.

Thanks for your help!
Yours
Henning

6

Dear all
The problem “how to access the container” is solved - I had to make changes to the file “forked-daapd.conf”. Actually it might be helpful to include this information into the setup explanation.

But there is a new problem - how to pair the server / how to access with Clients, But I think ist better to open a new post for this

7

I just tested a clean install and I had no issues getting access to the webui.
So it’s something about your setup that is the issue. What did you have to change in the config file?

We also set host networking in the examples in the readme as that is needed for everything to work correctly.