Anymore? Are you saying it’s a regression since a previous release, and you have steps to reproduce vs show it’s working in an older release? Then I think a bug report on GitHub is appropriate
(sorry not using AWS ELB myself, so can’t really help with the specifics)
Sorry, I forgot to mention that I am also using AWS ELB (Elastic Load Balancer, I think not EBS?), so the HTTPS resolves at that layer, and everything behind the load balancer is just plain HTTP.
I tried various Nginx configurations (basically, listening on port 80, forwarding to port 3000), similar to the link you shared.
Most of the configuration examples that I read involve listening on port 80; and then redirecting to port 443; with port 443 being the actual one configured with SSL. That would work on a single server setup and SSL being resolved at the server level.
So, yes, I do have the same issue, of needing to enforce HTTPS, but have SSL terminate on the load balancer.
Would it be possible to add some sort of setting to Metabase to allow enforcing an automatic redirect to the configured “SITE URL” setting in Settings > General? Other software like WordPress does this.
I would be okay with an automatic redirect, or a checkbox setting that I could turn on or off.