Selfhosted

46265 readers

241 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: 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!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

help with generating ssl for freedns in nginx (lemmy.world)

submitted 2 weeks ago by basic_user@lemmy.world to c/selfhosted@lemmy.world

3 comments fedilink hide all child comments

Hi,

I've been following this guide to set up some basic selfhosted services (video) https://www.youtube.com/watch?v=qlcVx-k-02E (text) https://notthebe.ee/blog/easy-ssl-in-homelab-dns01/

I've managed to get things working, but DuckDNS (duckdns.org) seems to be unresponsive most of the time. I then tried to register my DNS at FreeDNS (freedns.afraid.org), but the generation of a ssl certificate in Nginx fails. I get the following error message in Nginx:

CommandError: Saving debug log to /tmp/letsencrypt- 
log/letsencrypt.log
Some challenges have failed.
Ask for help or search for solutions at 
https://community.letsencrypt.org/. See the logfile /tmp/letsencrypt- 
log/letsencrypt.log or re-run Certbot with -v for more details.

at /app/lib/utils.js:16:13
at ChildProcess.exithandler (node:child_process:430:5)
at ChildProcess.emit (node:events:518:28)
at maybeClose (node:internal/child_process:1104:16)
at ChildProcess._handle.onexit (node:internal/child_process:304:5)

The domain I chose is <my_subdomain>.privatedns.org.

Does anyone know how I can get Nginx to succeed in generating the ssl certificate so I don't have to start deploying ssl generation myself?

If I have to do it myself any useful resources will be appreciated.

Thanks :)

top 3 comments

sorted by: hot top controversial new old

[–] truthfultemporarily@feddit.org 3 points 2 weeks ago

What is in the debug log?

[–] non_burglar@lemmy.world 2 points 2 weeks ago* (last edited 2 weeks ago)

Do you have port 80 to nginx open? Certbot dry run will give you some diagnostics, but that is the most common issue (port 80 being closed).

I also run LE on nginx and afraid DNS.

[–] irmadlad@lemmy.world 1 points 2 weeks ago

I have tried on numerous occasions to get freedns.afraid.org to work for me. I would be interested in how you got it going when you do get it all worked out.