Some apps no longer work with nginx-proxy without exposing the apps ports to the WAN IP about cloudbox HOT 4 CLOSED

Please update your repo(s) and re-run applicable tags. A fix was pushed a few minutes ago to expose the ports manually as the entries were removed from the upstream images.

from cloudbox.

Thank you. But why would the ports need exposed at all if it was working using the internal cloudbox network between nginx-proxy and the container without ports being exposed before?

from cloudbox.

You are confusing exposed ports (Docker terminology) with port binds/published ports. The ports are still not bound/published - that is unchanged. Until a couple of days ago, the upstream Docker images included an EXPOSE entry for the default web port. nginx-proxy is cranky if there is no port explicitly exposed, even though Cloudbox does not rely on it detecting the proper port.

from cloudbox.

ahh thank you!

from cloudbox.