Before You Begin<\/h2>\n
Before installing Scriberr, make sure your server or computer is ready. Scriberr can run on a local machine, a home server, a VPS, or a small workstation. For the smoothest experience, especially when processing longer recordings, use a machine with decent CPU performance and enough storage for uploaded media files.<\/p>\n
Recommended prerequisites:<\/strong><\/p>\n If you are using a cloud VPS, start with a modest instance and upgrade if transcription jobs take too long. If you are using your own hardware, consider where you want Scriberr to store media files so they do not accidentally fill your system drive.<\/p>\n Start by creating a dedicated folder for Scriberr. Keeping the application files in one place makes updates, backups, and troubleshooting much easier.<\/p>\n If you prefer installing it under a system location, you can use something like This directory will hold the Compose configuration, environment settings, and any folders you map for persistent storage.<\/p>\n Next, download the official Scriberr project files. The exact repository location can change over time, so it is best to copy the clone URL from the official Scriberr project page or documentation.<\/p>\n The period at the end tells Git to place the files directly into your current folder instead of creating another nested directory. After cloning, list the files:<\/p>\n Look for a Most self-hosted applications use an environment file to store settings such as ports, database credentials, upload paths, secret keys, and application URLs. If Scriberr includes an example file, copy it first:<\/p>\n Then open it in your preferred editor:<\/p>\n Review each value carefully. You may need to adjust:<\/p>\n Tip:<\/em> If you see a default password, default secret, or placeholder value, change it before exposing the app to your network or the internet.<\/p>\n Scriberr will likely need storage for uploaded media, processed text, logs, and temporary conversion files. If the Compose file already defines volumes, confirm that they point somewhere sensible. If it uses local folders, create them now:<\/p>\n Persistent storage is important because Docker containers can be recreated during updates. You do not want your transcripts disappearing just because you pulled a newer image or restarted the stack.<\/p>\n Once the configuration is ready, start the application:<\/p>\n The Check the container status:<\/p>\n If everything is healthy, you should see the Scriberr service running. If a container exits immediately, inspect the logs:<\/p>\n Common issues include incorrect environment values, missing folders, port conflicts, or insufficient permissions on mounted directories.<\/p>\n Now open Scriberr using your server address and configured port. For a local installation, this may look like:<\/p>\n For a remote server, use the server IP address:<\/p>\n If you changed the port in your environment file or Compose configuration, use that port instead. On first launch, Scriberr may ask you to create an administrator account, sign in with configured credentials, or complete a short setup screen.<\/p>\n Once inside, upload a short audio file as a test. Choose something under a few minutes so you can quickly confirm that transcription, saving, and viewing results all work as expected.<\/p>\n If you want to access Scriberr through a domain such as A reverse proxy is especially useful when Scriberr is running on a home server or VPS with multiple services. Instead of remembering ports, you use clean domain names. For public access, always enable TLS and use strong authentication.<\/p>\n Basic reverse proxy checklist:<\/strong><\/p>\n To update Scriberr, first enter the installation directory:<\/p>\n If you installed from Git, pull the latest project changes:<\/p>\n Then pull updated container images and restart:<\/p>\n Finally, check logs for errors:<\/p>\n Before major updates, back up your \n
docker compose<\/code> command<\/li>\n![\"\"](\"https:\/\/unitconversion.io\/blog\/wp-content\/uploads\/2026\/07\/computer-screen-displaying-code-and-project-files-server-terminal-docker-setup.jpg\")
\nStep 1: Create a Working Directory<\/h2>\n
mkdir -p ~\/scriberr\ncd ~\/scriberr<\/code><\/pre>\n\/opt\/scriberr<\/code> instead:<\/p>\nsudo mkdir -p \/opt\/scriberr\nsudo chown $USER:$USER \/opt\/scriberr\ncd \/opt\/scriberr<\/code><\/pre>\nStep 2: Get the Scriberr Files<\/h2>\n
git clone <official Scriberr repository URL> .\n<\/code><\/pre>\nls<\/code><\/pre>\ndocker-compose.yml<\/code>, compose.yml<\/code>, or similar file. You may also see an example environment file such as .env.example<\/code>. These files are the foundation of the installation.<\/p>\nStep 3: Configure Environment Variables<\/h2>\n
cp .env.example .env<\/code><\/pre>\nnano .env<\/code><\/pre>\n\n
Step 4: Prepare Persistent Storage<\/h2>\n
mkdir -p data uploads transcripts<\/code><\/pre>\n![\"\"](\"https:\/\/unitconversion.io\/blog\/wp-content\/uploads\/2026\/07\/a-stack-of-books-folders-audio-transcripts-storage.jpg\"){kind=spacer}
\nStep 5: Start Scriberr with Docker Compose<\/h2>\n
docker compose up -d<\/code><\/pre>\n-d<\/code> flag runs the containers in the background. Docker will pull any required images and start the services defined in the Compose file. The first run may take a few minutes, especially if large images or transcription-related dependencies need to be downloaded.<\/p>\ndocker compose ps<\/code><\/pre>\ndocker compose logs -f<\/code><\/pre>\nStep 6: Open Scriberr in Your Browser<\/h2>\n
http:\/\/localhost:8080<\/code><\/pre>\nhttp:\/\/your-server-ip:8080<\/code><\/pre>\nStep 7: Optional Reverse Proxy Setup<\/h2>\n
scriberr.example.com<\/code>, place it behind a reverse proxy such as Nginx, Caddy, or Traefik. This also makes it easier to add HTTPS.<\/p>\n\n
![\"\"](\"https:\/\/unitconversion.io\/blog\/wp-content\/uploads\/2026\/07\/assorted-icon-lot-web-browser-transcription-dashboard.jpg\"){kind=spacer}
\nStep 8: Updating Scriberr<\/h2>\n
cd ~\/scriberr<\/code><\/pre>\ngit pull<\/code><\/pre>\ndocker compose pull\ndocker compose up -d<\/code><\/pre>\ndocker compose logs --tail=100<\/code><\/pre>\n.env<\/code> file and persistent data folders. This simple habit can save hours if a configuration change or migration does not behave as expected.<\/p>\nTroubleshooting Common Problems<\/h2>\n