💾 Archived View for ew.srht.site › en › 2020 › 20201224-hosting-at-home.gmi captured on 2024-08-31 at 11:41:23. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2024-06-16)
-=-=-=-=-=-=-
At home I have a tiny system running permanently. It serves various services for the home network like time/ntp, names/dns, ip addresses/dhcp, ipv4 masquerading, apt package cache, nginx/nextcloud, nginx/cgit and the like.
It was my plan to host this gemini site and possibly a html-ized copy via an onion service. The onion service takes care of /finding/ my system: no need to register for a fixed ip address, no need to poke holes in the firewall either.
All good then? Maybe. Maybe not.
This post by Alex Schröder
gemini://alexschroeder.ch/page/2020-12-22_Crawling
and also threads on the mailing list
reminded me, that there is unfortunately more to be done, to protect this small system. In the age of abundant home offices one would like to avoid any risk of the line being abused or blocked for whatever reason. Or as I wrote to someone else:
I still(!) do not have a hosted instance somewhere, because I'm just not interested to defend this poor thing against the rough and not nice internet world. I can access my own stuff via an [hidden] onion service, however, I'm not convinced that publishing it would be a good idea.
I have set up a /hidden/ onion service to be able to reach home from abroad. Needless to say that hotel wireless is configured in pretty strange ways to prevent TOR traffic, ssh and vpn connections and the like. I need this like twice a year, but there is always something.
https://2019.www.torproject.org/docs/tor-onion-service.html.en
I am very well aware that hosting my little site at gemini.circumlunar.space is putting the above burden on someone else, solderpunk in this case. So thank you very much!