Change server settings
Server > Settings in the admin console holds the server's settings, one topic at a time. This page explains each one: what it does, and when you would change it. You need to be an admin.
The Server area also has About (your version and updates), Logs and the Audit log, covered at the end of this page. The health of what the server depends on (ffmpeg, the certificate, disk space, backups) is on Health > System.
Settings

The topics are listed down the left (across the top on a phone). Five of them have their own pages: Sign-in, Backups, Notifications, Import and Bridge.
To change a setting:
- Change the values you want in a card.
- Press Save changes at the foot of the card (Reset undoes your edits).
If the server refuses a value, the reason shows under the field and nothing in the card is saved. Switches, such as Check for new versions, save the moment you flip them. The console warns you before you leave a card with unsaved changes.
Your changes are written to config.yaml in the server's data folder, so they
last across restarts.
When a change takes effect
Most settings apply as soon as you save. No restart is needed.
A few only apply after a restart, and carry a Restart to apply badge:
- the listen address, the HTTPS mode and certificate names;
- the web player folder and the backups folder;
- the community metadata Service address and Source;
- turning demo mode on or off, and how long idle demo guests are kept.
After you save one, a notice at the top of Settings lists what is waiting. The server keeps its current values until you restart it.
The console can't restart the server. Restart it the way you started it: for
example docker compose restart, restarting the service, or quitting and
starting the program again.
A port that something else uses, or a Let's Encrypt name that doesn't point at
the server, can stop it from starting. Open config.yaml in the data folder,
put the old value back (the keys are in the
configuration reference), and start it
again.
Settings set somewhere else
A setting marked Set by AUDIOSILO_... is set by an environment variable,
often from your docker-compose.yml. It can't be changed here. An environment
variable wins over this page and config.yaml, so change it where it is set
and recreate the container.
General
- Server name - shown in the apps, on invites and in the console's top bar. Set one so people recognize your server.
- Public address - the address people use from outside your home, like
https://books.example.com. Invite links and QR codes use it. See Tell the server its public address. - Home address - the address devices use on your home network, like
http://192.168.1.20:8080. The apps switch to it when they can reach it. See Tell the server its home address. - Days to keep sessions (in Listening history) - how long each listening session keeps its device and time of day. After that, it is folded into daily totals, which Activity keeps for good. 400 days by default (30 to 3,650), which keeps a full year of detail.
- Check for new versions (in Updates) - on by default. The server asks GitHub once a day whether a newer AudioSilo exists. See What the update check sends.
Network & HTTPS

The HTTPS card chooses how the server secures connections (more in Reach your server from outside your home):
- Off - plain HTTP. Use it only behind a reverse proxy that does HTTPS.
- Self-signed - encrypted, but browsers warn the first time. The default, and fine on a home network.
- Let's Encrypt - free trusted certificates, renewed for you. Needs ports
80 and 443 open to the internet. Enter each Certificate name (like
books.example.com) on its own line.
With Self-signed, leave Plain HTTP at home on. Without it, the iOS and Android apps can't connect, because they can't trust a self-signed certificate. See Plain HTTP at home.
The Certificate row shows whether the current certificate is valid and when it runs out.
The Network card:
- Listen address - the address and port the server listens on, like
0.0.0.0:8080. Change it only if something else uses the port. - Trusted proxies - your reverse proxies, one per line. Set this so the server sees each visitor's real address.
- Allowed web origins - other websites allowed to use this server from a browser. Usually empty; see Settings you can leave alone.
Players & app links
The Web player card says whether people can listen in a browser at /web.
The player folder can only be set in config.yaml (web_dir) or with
AUDIOSILO_WEB_DIR.
The App links card lets invite links on your own domain open the installed app directly. It only helps with an app build made for your domain, so most servers leave it empty.
Community metadata

Look up community metadata turns on extra book details from the free community database at AudioSilo Meta. Books with an ASIN or ISBN, and books you matched in the console, gain an "About this book" section in the player: a description, series, and (where written) characters and recaps. See A book's page.
What is sent:
- Looking up a book sends only its ASIN or ISBN, or the community entry you matched it to, never file paths or who is listening.
- Matching a book in the console sends search terms from its tags, folder names and length, only when you match. See What matching sends.
- Community chapters: the server checks matched books in the background (see Community chapters).
- Cover images: your server downloads them from where the community database keeps them. Listeners' devices never contact those hosts.
Turning the switch off stops all of this at once, for everyone. The server then never contacts the Service address or the cover hosts.
The other settings on this topic:
- Status - whether the Service address (or your local copy) is answering.
- Check for upcoming releases - on by default. A daily check of the series you hold, for preorders, recent releases and missing books. Listeners (except kids) see them on Upcoming releases, and you can get a notification. A calendar app in the cloud, like Google Calendar, needs a public HTTPS Public address with a trusted certificate. Switched off, the server still looks up which community book each of your books is, so the players can keep recordings of the same book together.
- New release window - how many days after its release a book still counts
as new, 90 by default. You can only read it here. To change it, set
upcoming.window_daysinconfig.yamlorAUDIOSILO_UPCOMING_WINDOW_DAYS, then restart the server. - Help complete the community database - off by default. See Helping complete the community database.
- Audible marketplace (in Matching) - the store you buy from. When a recording sells in several stores, a match takes this store's ASIN. It has nothing to do with your library's language. Until a marketplace is chosen, the card offers the one nearest you, from your browser's language and time zone, unless that is the US store. Use store saves it, and Keep no preference keeps none. See Which ASIN a match takes.
- Service address -
https://meta.audiosilo.appby default. Change it only if you run your own. - Clear community matches (in Danger zone) - undoes every community match in one library or all of them, so you can match again from fresh. Your own edits and uploaded covers stay. It can't be undone.
The upcoming-release check and the missing-books report only work while Look up community metadata is on.
Helping complete the community database
Turn on Help complete the community database to report which of your books the community database is missing. Once a day, the server sends AudioSilo Meta the Audible ASINs of your books that the community database doesn't know. The community can then add those books.
The server sends only the ASINs, with no titles, file paths, server name or anything about listeners. AudioSilo Meta doesn't store your IP address with them. Its privacy page has the details.
Good to know:
- It sends only over HTTPS.
- With a local copy, nothing is sent until the copy is ready.
- A server in demo mode never sends a report.
- An ASIN isn't sent again for a month.
A line under the switch shows the last report and the next scheduled check. Switching it on runs a check straight away, unless one ran in the last day or the service asked for a quiet week. A report that stopped part way says how many ASINs it sent. The server tries the rest again the next day.
Keeping a local copy
The Source card chooses where lookups are answered:
- Ask the metadata service for each book (the default). Each lookup goes online, to the Service address.
- Keep a local copy. The server downloads the whole community database and answers lookups, matching and chapter checks from it. Fewer requests leave your server.
A local copy takes about 1.8 GB of disk, plus about 2.5 GB free while it updates. It downloads about 450 MB a day, from GitHub. Choose it if you want fewer online lookups and have the space.
How it behaves:
- It applies after a restart. Health > System shows the download's progress.
- Until the copy is ready, or if it fails, lookups go online, so listeners don't lose anything.
- A book the copy doesn't know is not looked up online.
- Cover images still come from their hosts.
- The copy isn't in your backups. It can always be downloaded again.
- Switching back to Ask the metadata service for each book deletes the copy at the next start.
Transcoding
Transcoding shows whether the server found ffmpeg and ffprobe. Nothing here can be changed in the console.
- ffmpeg converts formats a browser can't play while someone listens, and makes the small copies the Apple Watch and Wear OS apps download. Without it, some books won't play in a browser and watches get no copies.
- ffprobe reads lengths, chapters and codecs during a scan, for the files AudioSilo can't read itself. See ffmpeg and ffprobe.
To use other copies than the ones the server finds, start it with the
--ffmpeg and --ffprobe options (see the
configuration reference).
Converted copies are kept in the data folder under cache/. They are capped in
size, safe to delete and need no backup.
Household
These settings control household members: kids and grown-ups people add from the player, with no invite from you.
- People can add household members - on by default. Off stops new members being added. Members already added keep working.
- Members per person - 6 by default (1 to 50). Lowering it never removes anyone.
To stop one person adding members, see Household members.
Demo mode
The Demo mode card runs a public demo from this server (see Demo):
- Enable demo mode - hands out throwaway accounts at
/web/demo. - Guests can listen to - the library guests get. Use public-domain books, never your own collection.
- Most guests at once -
0means no limit; empty means 200. - Remove idle guests after - like
30mor24h; empty means 24 hours.
Modules

Modules are optional features. Each one is off until you turn on its Enable switch, which takes effect at once.
Some modules need a Bridge. Their card says whether your Bridge is ready, and links to Bridge settings if it isn't. You can turn a module on before then. Listeners see it once the Bridge is ready.
- Podcasts - follows shows by feed URL and downloads their episodes. Needs a Bridge. With it on, listeners can also search podcast directories and import OPML. See Podcasts.
- Contributions - sends your book corrections, and the characters and recaps your Bridge generates, to the community database. Needs a Bridge signed in to GitHub. See Contribute from your server.
- Audible - shows the books in your Audible accounts and backs up the ones you choose into your library. Needs a Bridge. See Audible.
Turning a module off keeps what it already made (shows, files, accounts).
About and updates

Server > About shows your version and whether a newer one exists. Check now asks straight away.
When an update is available, the card shows the release notes and how to update:
- Docker - pull the new image and recreate the container
(
docker compose pull, thendocker compose up -d). Your data folder stays as it is. - The program on its own - download the new version from the release page. Replace the program and start it with the same data folder (see Install without Docker).
The server never installs an update. You always update it yourself. Before you update, see Before an upgrade.
The first start after updating to 2.7.0 reads every book with MP3 files once more, so the scan at that start takes longer than usual and the scan report counts those books as updated. It does this to measure the real length of MP3 files whose length used to be estimated. A few books may then show a slightly different length.
A console tab left open while the server updates says AudioSilo was updated. Press Reload to open the new console.

The About card below lists the server's details, such as how it is installed, its data folder and the database size.
What the update check sends
The update check asks GitHub about the latest release, at most once a day and when you press Check now. It sends only your server's version. GitHub sees your address, as with any request. Nothing about your libraries, books or people is sent. Turn off Check for new versions in General to stop it.
Logs

Server > Logs shows what the server has been doing since it started: scans, missing folders, warnings and errors. Filter by Warnings or Errors, or search. Live tail keeps the view updated.
The page holds only the newest lines since the last restart. The full log is
wherever the server's output goes, such as docker compose logs. Passwords,
tokens and other secrets are never shown.
Audit log

Server > Audit log lists what admins changed, newest first: who, what and when, with the details. It also lists what people did with their household members. Filter by Area or Who, or search.
It records changes to accounts, invites, devices, access, progress, libraries, books, settings, backups and notifications. An Audible backup action names the account it was for. Sign-ins and listening are in Activity, and scans in Health > Jobs.
The log never holds a password or other secret, and no IP addresses. Entries are kept for a year.