BobCV

Solved my own problem... Turns out that when I installed the docker, I failed to notice that there was an error (I don't think that it was until about the 3rd time of reinstalling it that I noticed the error). At any rate, like Ed, I had created a unique network just the same as he had (except I named mine ProxyNet -- note the capitalization!). However, the docker installation error message stated that the network proxynet (all lower case) did not exist. I went in and removed that network and created another, but in all lower case, and the error went away... problem solved. Not sure if this should be considered a reportable "bug", but users beware! Thanks anyway!

Newbie here (actually, I've been running UnRaid for several years, but I haven't posted much to the forum)... I had started to follow spaceinvaderone's video for setting up a reverse proxy with letsencrypt. Obviously, due to the change from letsencrypt to swag, I then jumped over to his video on updating from letsencrypt to swag, except I just simply installed swag from the get go and followed the common instructions from both videos. It appears that Ed was running UnRaid 6.9.0-beta back in October of 2020, but my current version 6.9.2 only has uptime rather than a Log button to the right of the Autostart button, so no log to view here. Clicking the log from the icon menu brings up a blank log. However, the bigger issue is that clicking the Start option generates an Execution Error with an associated message of "No such container". I've searched the forum for this sort of error with no luck and I've also uninstalled and reinstalled swag but still got the error. Any suggestions?