31
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Sep 2025
31 points (100.0% liked)
Selfhosted
62781 readers
816 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:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
Pretty much, add the new domain to certbot, then create a new server directive with the new name and certificate paths. I would probably just copy and paste the existing one for your current domain, then just change the domain. SNI will then select the right certificate for you.
You can set certbot to create a single certificate with both domains, but tbh the above is just simpler to setup and maintain.