June 21, 20188 yr I'm trying to run Heimdall behind a Letsencrypt reverse proxy. To do this apparently I need to set up a custom network as written in this readme, and add the 2 docker containers "letsencrypt" and "heimdall" to the network in the advanced docker settings: https://github.com/linuxserver/docker-letsencrypt/blob/master/root/defaults/proxy-confs/_readme Line 28: Quote - If you are using unraid, create a custom network in command line, then go to docker service settings (under advanced) and set the option "Preserve user defined networks:" to "Yes". Then in each container setting, do one of the following: 1) Unraid 6.5.0 or earlier - (under advanced) add "--network=[networkname]" into "Extra Parameters". 2) Unraid 6.5.1 or later - in the network type dropdown, select "Custom : [networkname]". You would have to do the above for the letsencrypt container as well, so they are all on the same custom network. I created a Custom network with: docker network create web Not sure if it requires more args than just that, but I couldn't find much information on making custom networks. Changed the Network config on my Docker apps to use: [custom : web] Still seems that the Preserve User Defined Networks option is set to "No" as shown below, with no way to change it to "Yes": What's left to do here? My server's default network adapter is a bridged connection between 2 Gigabit Ethernet network adapters, if that is important to mention. Edited June 21, 20188 yr by plantsandbinary
July 19, 20187 yr I too would like this to work. Currently I have a script that I run each time I reboot the box that creates my networks. I have to do this manually though.
July 19, 20187 yr Stop the docker service - in the Docker setting, set Enable Docker to NO You'll be able to fiddle with the settings now. Set Preserve User Defined Networks to YES Start the docker service - set Enable Docker to YES Then any docker networks should now persist.
Archived
This topic is now archived and is closed to further replies.