HTTPS at home, how?
There is a small difference between a server on your own hardware and one you rent. This page is about your own hardware, on your home network. If you installed on a cloud server, read Your address on a cloud server instead.
Your suite has an address that looks a bit odd:
https://home.20-175-kqmzrt.local.myownsuite.org/The numbers are your server’s own address on your network, 192.168.20.175, with dashes instead of dots; on a 192.168 network, the most common kind, the first two numbers are left off. The six letters are your server’s own: it picked them when it was installed, so no other household’s server ever has the same address, even one on the same numbers. Your server’s screen and Suite Manager always show the whole address. This page explains why, what it means for your privacy, and what to do if it stops working.
You do not need to read this to use your suite. It is here for the moment you look at that address and think hang on, what is that?
The problem it solves
Section titled “The problem it solves”Your suite is not one website. Every app you install gets its own address — photos.…, files.…, documents.… — because keeping them separate is what stops one app from being able to read another’s data. That separation is a real security boundary, not a tidiness preference.
For those addresses to work, something has to know that photos.<something> means that machine over there. On the public internet, a domain name does that job, and you buy one. On your home network, nothing does — you would have to teach your router, and most home routers cannot be taught.
So My Own Suite generates an address that already contains the answer.
It looks public. It is not.
Section titled “It looks public. It is not.”local.myownsuite.org is a real domain name, so the address looks like it points somewhere on the internet. It does not.
It resolves to 192.168.20.175 — an address that only exists inside your own home. Those ranges are reserved for private networks and are not reachable from the internet, by design and by every router in between. Type that address into a phone using mobile data and nothing will load, because there is nothing out there to load. It only works on your own network, which is the entire point.
The lock in the address bar
Section titled “The lock in the address bar”Your suite gets a certificate that every browser trusts, with nothing to buy and nothing to set up. A few minutes after the server first starts, the address switches from http:// to https:// by itself, and your apps follow. Until then everything works over plain http://, and the few apps that need a secure connection, password managers in particular, wait and become available on their own.
What the lock gives you:
- Your connection is encrypted. Someone else on your network cannot read what passes between your devices and your suite.
- Apps that need a secure connection work. Browsers hold back parts of their security features from
http://addresses, and password managers will not run without them. - No warnings. The certificate comes from Let’s Encrypt, the same free certificate authority most of the web uses.
What it does not prove is that the server is yours. The letters in your address keep it apart from every other server’s, but they are not a password: the address is in public certificate logs, and anyone who copies it can get a valid certificate for it too. To use one against you they would still need to redirect your traffic on your own network to their machine first, which they could already do against plain http://. So this is strictly better than no lock, but it is not the proof of identity that your own domain gives.
If the lock does not arrive, nothing else changes: your suite keeps working over http://, and Settings → Suite address says the certificate is on its way. Your server keeps asking for it, and the switch happens by itself when it comes.
What actually leaves your network
Section titled “What actually leaves your network”Two things, and it is worth being precise about both.
When a device on your network opens photos.20-175-kqmzrt.local.myownsuite.org, it first has to ask what address is that? That question — and only that question — goes out to a nameserver My Own Suite operates. The answer comes back: 192.168.20.175. Your device then connects to your own server directly, and everything after that stays inside your house.
What that means in practice:
- We do not log those questions. No record is kept of which suite asked, or when.
- The answer is useless to anyone else. It is a private address. Knowing it does not help anyone reach your server.
- Your files, photos, passwords and documents never touch it. The nameserver answers a naming question. It never sees, stores or relays anything you put in your suite.
- We cannot see inside your suite, and nothing about this address gives us a way in.
What is technically visible to whoever runs that nameserver is which app names get asked about — that photos. and documents. were looked up by someone. That is a property of how naming works on the internet generally, not something specific to us, and it is why the other option below exists.
The second is the certificate. A few times a year your server asks Let’s Encrypt for a fresh one. To prove it may have it, your server leaves a short-lived code with a second small service My Own Suite runs, and Let’s Encrypt checks that code. That service sees your home’s public internet address and the code, keeps neither, and is told nothing else: no email address, no account, nothing about your apps. Let’s Encrypt sees your home’s public address for the same reason, and publishes every certificate it issues in public logs, so those logs show your server’s address, letters included, and when its certificate was renewed. They say that a My Own Suite server is behind it, not whose it is or where.
If you would rather your devices asked no one
Section titled “If you would rather your devices asked no one”There is a second way in, and it is the better one if your equipment supports it.
If your router, Pi-hole or AdGuard Home can add a wildcard DNS record, point *.mos.home at your server’s address and use http://home.mos.home/ instead. Then the naming question is answered inside your house, and your suite works with no outside involvement whatsoever — even with the internet unplugged. Your server still renews the certificate for its generated address in the background, so that door keeps working too.
Both addresses work at the same time. You can start with the generated one and switch later; your server’s screen shows both.
If it stops working
Section titled “If it stops working”The address contains your server’s IP, so if that changes, the address changes, though the letters stay the same. Home routers hand out addresses on a lease and can hand out a different one after a power cut or a reboot. Give your server a fixed address in your router — usually called a DHCP reservation — and this cannot happen. It is worth doing on the day you install, not the day it breaks.
If the address has already changed, your server’s screen shows the current one. Plug in a monitor and read it there.
If the address never worked at all, your router is probably refusing it. Some routers and DNS filters — Fritz!Box, OpenWRT, pfSense, Pi-hole and AdGuard Home among them — block answers that point into your own network as a security measure. It is called DNS rebinding protection, and it is a reasonable default that happens to block this.
Two ways around it:
- Add
local.myownsuite.orgto your router’s rebinding exception list. Most routers that do this have one; it may be called an allow-list or an exception. - Or use the
*.mos.homeroute above instead, which never involves an outside answer.
It can also differ between devices on the same network: iPhones with Private Relay and Android phones with Private DNS send these questions past your router entirely, so one device can work while another does not.
Using your own domain
Section titled “Using your own domain”Whichever way you installed, you can buy a domain and use it instead. That gives you an address you chose, and a certificate that proves the server is yours.
See Use your own domain with HTTPS. Your apps are moved across for you; you do not reinstall anything. The generated address keeps working for the suite’s own settings page, so you can always get back to it.