Nginx reverse proxy woes

Get Help
6

@AccurateHamilton

Post “Diagnostic Info” from Admin > Troubleshooting.

I don’t understand how Metabase is accessible on port 3000, so you must have been doing something that you’re not listing. Or you are using NAT/firewall redirect too. It’s hard to tell.

And I don’t understand your Nginx error log, and then you say “…failing in the translation…”, but your config is now not using sub-path. Did you remember to restart Nginx after changing the config?

I would highly recommend that you visit a Nginx forum, since they can provide much better help. There’s a million small tweaks and changes you can make, but it’s not really specific to running Metabase.

But this will make Metabase available on https://my.server.com/

server {
  server_name my.server.com;
  listen 80;
  listen [::]:80;
  return 301 https://my.server.com$request_uri;
}

server {
  server_name my.server.com;

  listen 443 ssl http2;
  listen [::]:443 ssl http2;
  include snippets/self-signed.conf;
  include snippets/ssl-params.conf;
  include snippets/general.conf;

  location / {
    proxy_pass http://127.0.0.1:3000/;
  }
}