Home Server GuideBuild it. Understand it. Maintain it.

Getting Started

Server Details & Passwords

Create a secure record of every address, port, username, password, API key and important setting before the server becomes complicated.

Guide difficulty ⭐⭐⭐⭐⭐ Beginner Friendly
Estimated time ⏱️ Around 10–15 minutes Keep updating the document throughout the build.

By the end of this guide you will have

  • A downloadable template for all server login details.
  • A record of application addresses and correct port numbers.
  • A place to store API keys and version numbers.
  • A change log explaining what was altered and why.

Why this matters

A home server quickly collects addresses, port numbers, usernames, passwords and API keys. These details are easy to remember while the server is new, but much harder to recover months or years later.

Store the document securely

This document contains sensitive information. Do not place it inside a public website folder, shared cloud folder or anywhere other people can access without permission.

A password manager is the safest option. An encrypted document or a text file stored inside an encrypted archive is also better than an unprotected file.

Download the server-details template

Home Server Guide includes a ready-made text file containing the sections, dummy login details and tested application port numbers shown in this guide.

Server Details Template

Download the file, save it somewhere private and replace the dummy information as you work through the build.

⬇️ Download TXT Template

Completed example

Copy this structure into your private notes and replace the dummy values as each application is installed. 

==================================================
HOME SERVER DETAILS
==================================================

Server name: homeserver
Server IP:   192.168.1.100

SSH
Address: 192.168.1.100
Username: serveradmin
Password: Example-Password-Only!

--------------------------------------------------

CasaOS
Address:  http://192.168.1.100:85
Username: serveradmin
Password: Example-Password-Only!


--------------------------------------------------

Jellyfin
Address:  http://192.168.1.100:8096
Username: mediauser
Password: Example-Password-Only!

--------------------------------------------------

Immich
Address:  http://192.168.1.100:2283
Username: photouser
Password: Example-Password-Only!

--------------------------------------------------

qBittorrent
Address:  http://192.168.1.100:8080
Username: admin
Password: Example-Password-Only!

--------------------------------------------------

Prowlarr
Address:  http://192.168.1.100:9696
Username: serveradmin
Password: Example-Password-Only!
API key:  EXAMPLE-API-KEY

--------------------------------------------------

Sonarr
Address:  http://192.168.1.100:8989
Username: serveradmin
Password: Example-Password-Only!
API key:  EXAMPLE-API-KEY

--------------------------------------------------

Radarr
Address:  http://192.168.1.100:7878
Username: serveradmin
Password: Example-Password-Only!
API key:  EXAMPLE-API-KEY

--------------------------------------------------

Readarr
Address:  http://192.168.1.100:8787
Username: serveradmin
Password: Example-Password-Only!
API key:  EXAMPLE-API-KEY

--------------------------------------------------

Nginx Proxy Manager
Address:  http://192.168.1.100:81
Username: example@example.com
Password: Example-Password-Only!

--------------------------------------------------

DuckDNS
Domain:   your-name.duckdns.org
Token:    EXAMPLE-DUCKDNS-TOKEN

--------------------------------------------------

CONTAINER VERSIONS

Gluetun:     v3.41.1
qBittorrent: v5.2.2
Prowlarr:    record tested version here
Sonarr:      record tested version here
Radarr:      record tested version here
Readarr:     record tested version here

==================================================

What should be recorded?

  • Server hostname and IP address.
  • Application names and browser addresses.
  • Port numbers.
  • Usernames and passwords.
  • API keys and tokens.
  • Folder and mount paths.
  • Docker image names and exact version tags.
  • Any setting changed from its default value.
  • The reason each non-default setting was changed.

Keep a simple change log

DATE: 14 July 2026

APPLICATION: CasaOS

CHANGE:
Port changed from 80 to 85.

REASON:
Nginx Proxy Manager requires port 80.

RESULT:
CasaOS is now opened at:
http://192.168.1.100:85

Recording the reason is just as important as recording the change. Future you may remember that a port was changed without remembering why.

Checkpoint

↑