
Deploy Navidrome | (Just Updated) Self-Hosted Music Streaming Server, Subsonic API, Spotify Alternative, Admin Login Generated
Navidrome self-hosted music streaming server, Subsonic API, admin generated
navidrome
Just deployed
/data
Deploy and Host Navidrome on Railway
Built for an LLM agent to deploy and use. The deploy form has no fields to fill: the administrator account is created at first boot with a generated password, nobody can claim the instance first, and the database and the music library live on a volume. Navidrome is a self-hosted music streaming server that speaks the Subsonic and OpenSubsonic APIs, a self-hosted alternative to Spotify, Plex and Jellyfin for your own music, streamed to any Subsonic client app.
About Hosting Navidrome
This template runs one service, navidrome: the upstream Navidrome v0.64.2 image, pinned by digest, through a thin wrapper, with a volume at /data that holds the database, the cache and the music library at /data/music. One public domain serves the web player, the native REST API and the Subsonic API. The server listens on Railway's injected PORT, and the healthcheck is GET /ping.
What the wrapper fixes. Upstream Navidrome shows a create-administrator page and, while no user exists, accepts an anonymous POST /auth/createAdmin that makes the caller the administrator, so on a public domain the first visitor owns the instance and its library. It also listens on port 4533 baked into the image and ignores Railway's PORT, and it keeps data and music on two volumes where Railway allows one per service. The wrapper refuses to start if ADMIN_PASSWORD is empty or shorter than 8 characters, has upstream seed the administrator admin from it on the first boot before the server accepts a request, so the first-user route is gone from then on, listens on PORT, and puts the music library under the one volume. Measured on an unmodified deluan/navidrome:0.64.2 run locally: an anonymous POST /auth/createAdmin answered 200 with isAdmin true. On the wrapper the same call answers 403 Cannot create another first admin. Not reproduced on a Railway control of the incumbent listing.
Using it. Open the domain and sign in as admin with ADMIN_PASSWORD. Put music in /data/music (for example with railway ssh, or set a MUSIC_ARCHIVE_URL variable to a .zip, .tar, .tar.gz or .tgz link and the first boot unpacks it into an empty library); Navidrome scans it and the albums appear. Point any Subsonic client (DSub, Symfonium, Amperfy, Feishin, Supersonic) at the domain with the same username and password. ADMIN_PASSWORD is read at the first boot only; change the password in the web player afterwards, and redeploys keep the same account. Upstream's first-boot message prints the generated password once in the deploy log, which only you can read.
Agent contract
- Public URL:
https://RAILWAY_PUBLIC_DOMAIN(the generated domain of thenavidromeservice) - Private URL:
http://navidrome.railway.internal:8080 - Credentials: the variable
ADMIN_PASSWORDon thenavidromeservice is the password of the administratoradmin - Auth:
POST /auth/loginwith a JSON body ofusernameandpasswordreturnstoken; send it as the headerX-ND-Authorizationwith the valueBearerplus a space plus the token on every/apicall. The Subsonic API at/resttakesu,p,v,candfquery parameters with the same login. Without the token a write answers 401. Public sign-up is closed. - Health:
GET /pingreturns 200 without credentials
#!/bin/sh
# needs: RAILWAY_PUBLIC_DOMAIN, ADMIN_PASSWORD (variables of the navidrome service); also curl, sed, grep.
R="https://$RAILWAY_PUBLIC_DOMAIN"
J="Content-Type: application/json"
STAMP=$(date +%s)
n=0; until [ "$(curl -s -o /dev/null -w '%{http_code}' "$R/ping")" = 200 ]; do n=$((n+1)); [ "$n" -le 60 ] || break; sleep 5; done
curl -s -o /dev/null -w "health: %{http_code}\n" "$R/ping"
# a stranger cannot become the administrator: the first-user route answers 403 once an administrator exists
curl -s -X POST -H "$J" -d "{\"username\":\"stranger$STAMP\",\"password\":\"pw$STAMP$STAMP\"}" "$R/auth/createAdmin" -o /dev/null -w "public signup: %{http_code}\n"
# a stranger cannot write: creating a user without a token or with a wrong one is refused
BODY="{\"userName\":\"x$STAMP\",\"name\":\"x$STAMP\",\"password\":\"pw$STAMP$STAMP\",\"email\":\"x$STAMP@example.com\"}"
curl -s -X POST -H "$J" -d "$BODY" "$R/api/user" -o /dev/null -w "write without key: %{http_code}\n"
curl -s -X POST -H "$J" -H "X-ND-Authorization: Bearer not-a-token" -d "$BODY" "$R/api/user" -o /dev/null -w "write with wrong key: %{http_code}\n"
# a wrong password is refused, the generated one signs in as the administrator "admin"
curl -s -X POST -H "$J" -d "{\"username\":\"admin\",\"password\":\"wrong$STAMP$STAMP\"}" "$R/auth/login" -o /dev/null -w "login with wrong password: %{http_code}\n"
LOGIN=$(curl -s -X POST -H "$J" -d "{\"username\":\"admin\",\"password\":\"$ADMIN_PASSWORD\"}" "$R/auth/login")
TOKEN=$(echo "$LOGIN" | sed -n 's/.*"token":"\([^"]*\)".*/\1/p')
if [ -n "$TOKEN" ]; then echo "login with key: ok"; else echo "login with key: FAILED"; fi
# the Subsonic API that music clients speak accepts the same login and reports the library
sub() { curl -s -G --data-urlencode "u=admin" --data-urlencode "p=$ADMIN_PASSWORD" --data-urlencode "v=1.16.1" --data-urlencode "c=agent" --data-urlencode "f=json" "$R/rest/$1"; echo; }
sub ping.view | sed -n 's/.*"status":"\([a-z]*\)".*/subsonic ping: \1/p'
sub getMusicFolders.view | sed -n 's/.*"musicFolder":\[{[^}]*"name":"\([^"]*\)".*/music folder: \1/p'
# with the token a user is created and read back
curl -s -X POST -H "$J" -H "X-ND-Authorization: Bearer $TOKEN" -d "$BODY" "$R/api/user" -o /dev/null -w "write with key: %{http_code}\n"
FOUND=$(curl -s -H "X-ND-Authorization: Bearer $TOKEN" "$R/api/user" | grep -c "\"userName\":\"x$STAMP\"")
if [ "$FOUND" -ge 1 ]; then echo "user listed: found"; else echo "user listed: MISSING"; fi
Expected output against a fresh deploy (measured on a Railway deploy of the generated draft):
health: 200
public signup: 403
write without key: 401
write with wrong key: 401
login with wrong password: 401
login with key: ok
subsonic ping: ok
music folder: Music Library
write with key: 200
user listed: found
The refusals are the contract: write without key: 401 and write with wrong key: 401 on the user create, public signup: 403 on the first-user route, and login with wrong password: 401.
Why Deploy Navidrome on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Navidrome on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
- Agent-ready - no deployer fields, a contract block, and one script that proves the server is healthy, a stranger can neither write nor register, and the generated password signs in on both the native and the Subsonic API.
- Owned by you from the first request - the administrator is seeded before the server accepts a connection, so nobody else can claim it.
- Works on first deploy - the listener already follows Railway's injected
PORT. - Data survives redeploys - the database, the cache and the music library live on one volume.
- Pinned - the upstream image is pinned by digest and the wrapper by tag and digest.
Common Use Cases
- Personal music streaming - your own library in a web player and on your phone, without a subscription.
- Subsonic server for client apps - DSub, Symfonium, Amperfy, Feishin and Supersonic connect with a username and password.
- Self-hosted alternative to Spotify, Plex and Jellyfin for music - one small Go server, about 20 MiB of memory idle.
Dependencies for Navidrome Hosting
- The navidrome service with its volume, created by the template. A music archive link is optional; add it as a
MUSIC_ARCHIVE_URLvariable before the first boot.
Deployment Dependencies
Template Content
