Share over your own domain
An https:// address of your own lets friends, family and their TVs reach your server from anywhere, with nothing to
install but the app. It takes a domain name, two forwarded ports and a small program called Caddy.
Is this the right way?
For you and the people you live with, Tailscale is simpler and safer: nothing is opened on your router. Use your own domain when the people you share with won't install Tailscale, or watch on a TV that can't.
This way puts your server's sign-in page on the internet. Finish setup first, and don't skip step 5. Several steps use the Terminal and your router's settings.
You'll need
- A server that's set up and playing at home.
- A domain name, or a name from a dynamic DNS service.
- Your router's settings page, to forward two ports.
- A home connection with a public address of its own. If the WAN address on your router's status page differs from what a "what is my IP" site shows, your provider shares one address among customers, port forwarding can't work, and Tailscale is the way.
-
Point a name at your home
Where your domain's DNS is kept, add an A record for a name such as
media.example.comwith your home's public address. Most home addresses change now and then, so turn on dynamic DNS to keep the record right: many routers have it built in, and DNS providers have small updater programs. -
Forward ports 80 and 443
In your router's settings, forward ports 80 and 443 to the server computer, and nothing else. Port 80 is only for the certificate check and the redirect to HTTPS. Never forward port 27587: that would put the server on the internet without encryption.
-
Put Caddy in front of the server
Caddy is a free web server that gets an HTTPS certificate for your name, renews it, and passes visitors on to WatchMyMedia. It runs on the server computer.
On a Mac
In Terminal, with Homebrew installed:
brew install caddyReplace the contents of the file at
$(brew --prefix)/etc/Caddyfilewith this, using your own name:media.example.com { reverse_proxy 127.0.0.1:27587 { flush_interval -1 } }Then start it, now and at every restart:
brew services start caddyflush_interval -1sends video and live updates on as they arrive, without holding them back.With Docker on Linux
The project's repository has a compose file that adds Caddy and a dynamic DNS updater beside the server. Public access with a reverse proxy in its README has the steps.
On Windows, or with another proxy
Caddy runs on Windows with the same file; this guide doesn't walk through installing it there yet. If you already run SWAG, Nginx Proxy Manager or another reverse proxy, point it at port 27587 on the server computer. Don't put the proxy's own login in front, because the TV apps can't get past it, and turn off its buffering so video isn't held back. The README has SWAG's steps.
-
Tell WatchMyMedia to trust the proxy
Until the server trusts Caddy, it can't tell who each visitor really is: everyone who comes through counts as an unknown visitor from the internet, and history shows no address for them. Make a file called
config.yamlin the server's data folder, or add these lines to the one that's there:network: trusted_proxies: [127.0.0.1, "::1"]The data folder is
~/Library/Application Support/WatchMyMediaon a Mac and%LOCALAPPDATA%\WatchMyMediaon Windows. Then choose Restart Server in the WatchMyMedia menu. On Debian, Ubuntu and Fedora the file is/etc/watchmymedia/config.yamlinstead: edit it withsudoedit /etc/watchmymedia/config.yaml, then runsudo systemctl restart watchmymedia. Those two addresses mean "a program on this computer", which is where Caddy runs. -
Protect the sign-in page
- Open Settings › Security and, under Sign-in protection, choose Turn on. It uses Cloudflare Turnstile, which is free, to check that a visitor is a person before any password is tried. The steps have you add a Turnstile widget for your name in Cloudflare's dashboard, paste its two keys, and try the check before you finish. While it's on, the phone and TV apps sign in with a code you approve in a browser instead of a password.
- Give every account a strong password, and add everyone but you as a Member.
- If you never change server settings away from home, turn off Let admins change server settings from anywhere, over HTTPS on the same page. Change server settings away from home explains it.
- Keep the server up to date.
-
Share the address
Add an account for each person, and send them the address, their name and their password. They open
https://media.example.comin a browser, or type it into the WatchMyMedia app on their phone, tablet or TV.
You're done when your phone, on mobile data with Wi-Fi off, opens your https:// address and shows the sign-in page.
Good to know
- At home, the name may not open. It works inside your home only if your router supports NAT loopback. If it doesn't, keep using the server's home address there.
- Your upload speed is the limit. Everyone watching away from home shares your home's upload. On Automatic the player lowers the quality to fit, and an admin can cap the total under Settings › Transcoding. What changes away from home has more.
-
Casting works on this address. Chrome and Edge show the Cast button on an
https://page, for a Chromecast or Google TV on the network the browser is on.
If it doesn't work
Written for WatchMyMedia 1.4.7 on November 16, 2026, from the project's README. The config.yaml lines were tried on
1.4.5; the whole path, with a real domain and router, has not been followed step by step. Step 4's Debian, Ubuntu and Fedora
lines were added on November 21, 2026, for the packages that came with 1.7.0.