225redstick
-
Posts
18 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by 225redstick
-
-
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.?
-
On 3/11/2019 at 5:50 AM, SpaceInvaderOne said:
Yep that will be because there is no config file that uses that subdomain. Just edit a config file to direct to whichever container you want to access from outside.
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
-
getting this on my domain and subdomain (cnames 😞
do i need to edit config files next???
-
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!
-
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
-
I think i figured it out for now, somehow bonding and bridging were on "yes" and seemed to be preventing the new router from connecting and configuring eth0. Thanks for suggestions and help and a little bit of trial and error
I was worried my jump drive and/or network card were shot.
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.7 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 XXXXXXXXXXXXXX prefixlen 64 scopeid 0x20<link>
ether XXXXXXXXXXXXXX txqueuelen 1000 (Ethernet)
RX packets 1645 bytes 267297 (261.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 957 bytes 750155 (732.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xdfb00000-dfb20000 -
bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST> mtu 1500
inet6 XXXXXXXXXXXXX prefixlen 64 scopeid 0x20<link>
ether XXXXXXXXXXXXX txqueuelen 1000 (Ethernet)
RX packets 954 bytes 130622 (127.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 749 bytes 802552 (783.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.7 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 XXXXXXXXXXXXX prefixlen 64 scopeid 0x20<link>
ether XXXXXXXXXXXXX txqueuelen 1000 (Ethernet)
RX packets 773 bytes 83939 (81.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 308 bytes 771747 (753.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
ether XXXXXXXXXXXXX txqueuelen 1000 (Ethernet)
RX packets 954 bytes 130622 (127.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 749 bytes 802552 (783.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xdfb00000-dfb20000eth1: flags=6147<UP,BROADCAST,SLAVE,MULTICAST> mtu 1500
ether XXXXXXXXXXXXX txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xdf900000-df920000lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 2 bytes 140 (140.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2 bytes 140 (140.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 -
-
the other thing i tried earlier in an attempt to return to the default DHCP configuration was to pull the usb unraid boot drive and to delete the boot/config/network.cfg and boot/config/network-riles.cfg files.
-
root@unRAID:~# ifconfig br0
br0: error fetching interface information: Device not found -
"Your router leased 192.168.1.5 to br0 not to eth0" i do remember trying to reserve that ip in router settings for DHCP unraid initial assignment? no reservation in router settings is showing up since I reset the router.
"Do you have bridging enabled for eth0 in Settings --> Network"? yes it was turned on, i dont remember doing that but maybe for an earlier docker install. i just tried turning it off.
-
dosent show ip here like it use to:
eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
ether XXXXXXXXXXXX txqueuelen 1000 (Ethernet)
RX packets 2318 bytes 1020947 (997.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1831 bytes 1402158 (1.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xdfb00000-dfb20000 -
#ifconfig eth0
unraid eth0: flags=4416<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
I was worried my jump drive and/or network card were shot. 
** VIDEO GUIDE ** How to Setup and Configure a Reverse Proxy on unRAID with LetsEncrypt & NGINX
in Docker Containers
Posted
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?