We designed taiga-docker so the TLS termination is managed outside Taiga. SSL/TLS or the load balancer for instance, are decisions company wise. We know that different companies have different infrastructures so these decisions are left to each installation.
For this reason, taiga-docker exposes a port to a non-priviledged port in the host and let the company manage it. As a technical note, taiga-docker has an nginx gateway but it’s not meant to listen at 80/443, it’s a mean to hide some of the complexity of the services. So, you shouldn’t be counting on this nginx to configure the TLS termination.
Now, the recommended way is explained in the official documentation, in the section “Configure the Proxy”. The example is made with nginx, because it’s a very popular proxy server, and it has integration with LE, as you can see in their official documentation, but you could use Caddy server as well, which has a very good Let’s Encrypt integration.
the uncomplicated firewall should work for this scenario; it’s probably something around your configuration.
You could also check on your cloud provider as they typically have options to close ports from external access.
That said, this is not Taiga related, and I believe this forum is not the best place to find help regarding your issue.