jwelch

In the same boat here. Did you ever find a solution?

You'll need to gather these, as shown in the link binhex provided: Gather Command execution Left click the container and select 'Edit', make any change to a value, then switch it back to what it was and click on 'Apply', then copy and paste the 'Command execution' shown to a file, ensuring to remove all reference to username and password. Go to support thread (left click icon and select 'Support') and then attach (do NOT paste) the 'Command execution' output file but do not 'Submit Reply', please move onto the next step below. Gather Supervisor log Delete any existing log file located at /config/supervisord.log, where /config is the host path for the container. Left click container and select 'Edit' then set the 'Container Variable' for DEBUG to a value of true and click 'Apply'. Wait 5 mins for it to completely finish initialising, then open the log file at /config/supervisord.log and remove all reference to username and password from the file, then save the log somewhere. Attach (do NOT paste) the log output file from Step 3 to the post and click on 'Submit Reply'. See my prior reply for reference if you like.

Ah, okay! Thanks for the quick reply! I've been running it in bridge mode when I needed to use it, then switching back to br0 to troubleshoot. I was almost certain I had it working with VPN and br0 custom network a couple weeks back, and was therefore trying to get it that way again. I like having unique IPs for each container as my password manager gets confused having multiple crews saved for web "pages" on the same (host) IP. I'm guessing there's no easy workaround or alternative for my situation besides custom DNS entries for the different ports on the same host IP? Appreciate your help!

Sorry about that! I should have read the FAQ more carefully. Here are the requested logs. Thanks! docker command ex.txt supervisord.log

Having the exact same issue on the latest version as well. Fairly new to all this. I've also checked my CIDR in the LAN_NETWORK field, along with searching forums for days, trying numerous fixes with no luck.