How to access Let's Encrypt SSL Files on Container

[ayushsharma82]

I have deployed an Nodejs Container which has 'Mosca MQTT Broker' and would like to know how can i get the SSL Key and Cert generated by Nanobox to enable SSL on broker itself.

SSL is auto generated by Let's Encrypt.

On the other hand, There is no nanobox image available for 'Mosquitto MQTT Broker' which is the core component of 'Internet of Things' Applications.

[danhunsaker]

SSL termination is handled by your load balancer, and in fact HTTPS connections will never reach your web components at all. Instead, your load balancer contacts your web component instance(s) via HTTP over port 8080, and forwards the response back over its own HTTPS connection to the user. Pulling the LE cert into the container isn't going to do much good, in other words, and is entirely unsupported.

You won't find images or engines specific to any given framework or tool, no. Nanobox provides the engine for the underlying language, and it's up to the user to determine how to set their app up within it. There are simply too many frameworks, tools, applications, and so forth to even begin supporting them all, or even just the most popular subset.

Even focusing just on MQTT brokers, there are numerous options available, and MQTT isn't even the only IoT enablement mechanism available – even if Nanobox was IoT focused (which it isn't), supporting a handful of specific ones would be entirely too much time the team could devote elsewhere to other features.

[ayushsharma82]

@danhunsaker So What can be the work around for MQTT SSL because it doesn't uses 443 port.
MQTT over SSL uses 8883 / 8833. and normal port is 1883

[ayushsharma82]

I can achieve the normal port by using -port in boxfile.yml. I know nanobox is not IoT focused. It's completely fine i can host a mqtt broker on nodejs itself. So now the main focus here is how can the load balancer apply ssl to other ports also? like 8883

web.broker:
  ports:
    - tcp:1883:1883
  start:
    node: node broker.js