Docker migration to HassIO - letsEncrypt and the Supervisor

Hey guys,
Ive just rebuilt my HA machine and used the opportunity to migrate to HassIO.

I have HassIO running in Docker with other images, one being the LetsEncypt with Nginx (now Linuxserver/SWAG ) that I used and loved in my old build.

However this means that none of the supervisor add ins will start in HassIO, for example Nodered will fail to start, complaining about a cert file / HTTPS which make sense cause that part is managed by Letsencrypt.

I understand (Think) there is a add in called lets encrypt that fixes this? It somehow manages to share the cert files with everything else but I cannot get it to work, either in HTTP mode or DNS mode it complains about port 80. I even moved my DNS to Cloud fire but no dice.

I also understand I can turn off HTTPS and fix it but I really don’t want to do that, and im not even sure how.

How do I go about getting this working?

NodeRed Error

[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing…
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] nginx.sh: executing…
[02:30:31] FATAL:
[02:30:31] FATAL: SSL has been enabled using the ‘ssl’ option,
[02:30:31] FATAL: this requires a SSL certificate file which is
[02:30:31] FATAL: configured using the ‘certfile’ option in the
[02:30:31] FATAL: add-on configuration.
[02:30:31] FATAL:
[02:30:31] FATAL: Unfortunately, the file specified in the
[02:30:31] FATAL: ‘certfile’ option does not exists.
[02:30:31] FATAL:
[02:30:31] FATAL: Please ensure the certificate file exists and
[02:30:31] FATAL: is placed in the ‘/ssl/’ directory.
[02:30:31] FATAL:
[02:30:31] FATAL: In case you don’t have SSL yet, consider getting
[02:30:31] FATAL: a SSL certificate or setting the ‘ssl’ option
[02:30:31] FATAL: to ‘false’ in case you are not planning on using
[02:30:31] FATAL: SSL with this add-on.
[02:30:31] FATAL:
[02:30:31] FATAL: Check the add-on manual for more information.
[02:30:31] FATAL: