this post was submitted on 29 Feb 2024
106 points (98.2% liked)

Selfhosted

38810 readers
93 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 1 year ago
MODERATORS
106
Selfhost wiki (personal) (wiki.gardiol.org)
submitted 5 months ago* (last edited 5 months ago) by [email protected] to c/[email protected]
 

I have finally got my selfhost wiki up to a satisfying shape. Its here: https://wiki.gardiol.org

Take a look i hope it can help somebody.

I am open to any suggestions about it.

Note: the most original part is the one about multi-homed routing and failbacks and advanced routing.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 5 months ago (5 children)

One of the risks associated with wildcard SSL certificates is the increased attack surface they introduce. If one subdomain becomes compromised, it opens the door for potential attackers to gain unauthorized access to all subdomains secured under the wildcard certificate. (first google link)

[–] [email protected] 1 points 5 months ago (4 children)

While this argument is valid for a larger domain, it doesn't really matter for the small selfhoster.

[–] [email protected] 2 points 5 months ago (3 children)

Using let's encrypt certbot is so easy and automated that I never bothered for wildcards anyway, so.

[–] [email protected] 2 points 5 months ago (1 children)

The advantage of wildcard certificates is that you don't have to expose each single subdomain over internet. Which is great if you want to have https on local only subdomains.

[–] [email protected] 1 points 5 months ago (1 children)

If you still use HTTP for cert verification on ACME, you are doing it wrong. Use DNS-01 only, there is no need to allow any inbound traffic to your servers. and HTTP will not give you wildcard anyway.

[–] [email protected] 2 points 5 months ago

Yes, you are right, I already use DNS validation. But it is just it is easier to request a single wildcard certificate for my domain and have all the subdomains that I use for the local services defined only in my local DNS. I cannot fully automate the certificate renewal because namecheap requires to allowlist the IP that can call its API, and my ip is dynamic. So renewing a single certificate saves me time. Also, the wildcard certificate is installed on a single machine, so it is not the I increase a lot the attack surface by not having different certificates for each virtual host.

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