As previously mentioned start9 uses multicastDNS so that you can find it on your local network.
The start9 setup recommends installing the start9 certificate in your browsers. This is a good idea if you are intending to continue with the application in “production”. start9 has a relatively simple guide on how to achieve that.
mDNS from start9 will broadcast an address for your instance so that you can connect on https://adjective-noun.local/login. (adjective-noun is their nomenclature for generating a domain name for your local network.) This then gives you access all the subsequent containers that you install.
Umbrel is a similar product for easy container installation. It has a more comprehensive list of potential applications. It also uses mDNS.
Unfortunately it is not possible to run two mDNS servers on the same network (as I discovered last night). Turning off my Umbrel instance this morning has allowed me to get local access to start9 today.
I put this learning experience down to what Mr Duffy my year 12 math’s teacher would call “Traps for young players.”
If you want to become a start9 guru BTCSessions has a comprehensive playlist which draws on tubes from a variety of sources. He starts off with a 2 hour tutorial which hopefully covers all the major points. (I have not watched it however.)
One of the tubes in the playlist does a critique of Umbrel. It’s from the CEO of Start9. His take home message is, “Friends don’t let friends install umbrel”.
