Jump to content


  • Posts

  • Joined

  • Last visited


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

225redstick's Achievements


Noob (1/14)



  1. I see these, but not sure what do do with them. Do i copy/move them to each app folder or copy the text of each and put them all in the letsencrypt default config file?
  2. Or do you have a good example letsencrypt default config file to share that i could use as a template for my subdomains pointing to radarr, sonarr, plex etc.?
  3. I would love a future video explaining editing out configs to point to subdomains, I still find that confusing as my goal is to limit my ports that are exposed. Do i edit/replace the default config file, this is the part I'm struggling with, how to set this up. Thanks again
  4. getting this on my domain and subdomain (cnames 😞 do i need to edit config files next???
  5. Thanks, for some reason it was still not completing the validation. I got validations to work by following this: If you get a fail message, Let's Encrypt can't access your server. This could be from the router blocking it or the ISP blocking it. You can go back to the dashboard, click on Let's Encrypt → Edit. Change validation method to DNS and put “cloudflare” under “DNS-plugin” but don't hit apply yet. You need to give it access to your DNS records on cloudflare. To do this, SSH into the unraid server, go to /mnt/user/appdata/letsencrypt/dns-conf, and find cloudflare.ini. Edit the file “nano cloudflare.ini” and put your email and cloudflare global API key on the appropriate lines. Save the file. Note that now that this file contains sensitive information you need to lock down the permissions. Run sudo chmod 600 cloudflar.ini (this command didn't seem to work) to make sure only the owner can access this file. Now go back to the Unraid GUI and hit apply to validate with the DNS method. Check the logs of the container, if all went well the validation will work, certificates will be issued and the server will be ready. You should now be able to go to https://domain:8443/ and see the default welcome page for NGINX. (got this instead: error 1016) In the top corner of the browser you should see a green lock next to the URL to indicate that your connection is encrypted. (did see this, so I think I'm making progress) So, for my domain i have the "A" record (cloudflare) set to my WAN address of my router. is this correct? Back to trying to make this work. I will watch more videos and hopefully just have to edit a few things to point everything in the right direction. This is all new to me, but i enjoy trying to figure new things out...besides the frustrating parts of course. Cheers!
  6. Newbie questions #1, I previously added SSL, HTTPS in unraid settings. Using this guide do i remove those settings/changes for this letsencrypt tutorial? Question #2, I previously set some things up with duckdns and my previous router and dockers and they were working fine, now i have changed to a new pfsense box and want to use cloudflare with my own domain name, does duckdns still have a role to play? Sorry for basic questions, just trying to figure all this out. Big thanks for any help/knowledge
  • Create New...