Selfhosted
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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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!
view the rest of the comments
Let's Encrypt is fully automated and will issue certificates as long as you provide an email address AND have a proper, working config. Don't get stuck on that email "issue", your problems will lie somewhere else.
As always when problems arise: check the log files.
I've gone through their automatic setup and followed the youtube tutorial from Lawrence Systems. I entered all the required information for the setup correctly (apart from the email maybe). The tutor got his dashboard page hosted with https properly enabled with no additional configuration and I expected mine to work the same. I've tried to regenerate the certificates according to the official docs, but I still get the same result. I honestly don't know where else the problem could've arised. As much as I hate it, I think I'll have to go through the logs after all.
Selfhosting without checking the logs to hunt down errors? That's not going to be pretty.