this post was submitted on 14 Jul 2025
125 points (97.0% liked)

Selfhosted

49497 readers
973 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I'm not really sure how to ask this because my knowledge is pretty limited. Any basic answers or links will be much appreciated.

I have a number of self hosted services on my home PC. I'd like to be able to access them safely over the public Internet. There are a couple of reasons for this. There is an online calendar scheduling service I would like to have access to my caldav/carddav setup. I'd also like to set up Nextcloud, which seems more or less require https. I am using http connections secured through Tailscale at the moment.

I own a domain through an old Squarespace account that I would like to use. I currently have zero knowledge or understanding of how to route my self hosted services through the domain that I own, or even if that's the correct way to set it up. Is there a guide that explains step by step for beginners how to access my home setup through the domain that I own? Should I move the domain from Squarespace to another provider that is better equipped for this type of setup?

Is this a bad idea for someone without much experience in networking in general?

you are viewing a single comment's thread
view the rest of the comments
[–] littleomid@feddit.org 9 points 1 day ago* (last edited 1 day ago) (6 children)

Three steps:

  1. point the FQDN to your network (Dynamic DNS).
  2. set up reverse proxy (Nginx, etc.)
  3. set up certificates (Certbot, etc.)

Optional step 4: harden with fail2ban and a firewall.

[–] bruce965@lemmy.ml 7 points 1 day ago* (last edited 1 day ago) (5 children)

I would say this would be the proper way to do it (at least as a sysadmin), but since it's OP's first time I would simplify it to:

  1. Install CloudFlare ZeroTrust daemon on your local server;
  2. Set up reverse proxy such as Nginx (optional, the alternative is to use a different subdomain for each service, which might be easier);
  3. Point the FQDN to CloudFlare.

Let CloudFlare handle the certificates, DDoS protection, etc... Link if you'd like to give this setup a try.

[–] brian@lemmy.ca 1 points 1 day ago (2 children)

How would you go about using a different subdomain without something like a reverse proxy? Heck, in my head that's almost the only reason I use a reverse proxy

[–] bruce965@lemmy.ml 1 points 1 day ago

Yeah, I'm afraid you have to use a reverse proxy to host multiple subdomains. The CloudFlare daemon is the reverse proxy.

load more comments (1 replies)
load more comments (3 replies)
load more comments (3 replies)