Getting to ShinyProxy landing page but can't connect to apps

Hello!

I am trying to deploy my python shiny app on an EC2 but am running into trouble actually launching my app from ShinyProxy. I have nginx set up as a reverse proxy and I am able to get to the shinyproxy landing page when I navigate to my domain but when I click my app I get the error :

Unable to connect
Firefox can’t establish a connection to the server at 127.0.0.1:3838.

I’m pretty new to this so if I am missing something obvious let me know. Thanks!

My application.yml:

proxy:
  title: Open Analytics Shiny Proxy
  logo-url: https://www.openanalytics.eu/shinyproxy/logo.png
  landing-page: /
  heartbeat-rate: 10000
  heartbeat-timeout: 60000
  port: 3838
  bind-address: 127.0.0.1 # Added the bind-address directive
  container-log-path: /var/log/shinyproxy
  docker:
    port-range-start: 20000
  specs:
    - id: quipi
      display-name: QuIPI
      container-image: quipi
      port: 3838
    - id: 01_hello
      display-name: Hello Application
      description: Application which demonstrates the basics of a Shiny app
      container-cmd: [ "R", "-e", "shinyproxy::run_01_hello()" ]
      container-image: openanalytics/shinyproxy-demo
server:
  forward-headers-strategy: native
  secure-cookies: true

logging:
  file:
    name: shinyproxy.log

My nginx config:

server {
  listen                80;
  # Enter ourdomain.com or subdomain.ourdomain.com
  server_name           quipi.org;
  rewrite     ^(.*)     https://$server_name$1 permanent;
}

server {
  listen                443 ssl;
  # Enter ourdomain.com or subdomain.ourdomain.com
  server_name           quipi.org;
  access_log            /var/log/nginx/shinyproxy.access.log;
  error_log             /var/log/nginx/shinyproxy.error.log error;

  ssl_protocols TLSv1 TLSv1.1 TLSv1.2;

  # Diffie-Hellman key
  ssl_dhparam /etc/ssl/certs/dhparam.pem;

  # OCSP stapling
  ssl_stapling on;
  ssl_stapling_verify on;

  # Enter the paths to our ssl certificate and key file created in the previous subsection
  ssl_certificate       /etc/letsencrypt/live/quipi.org/fullchain.pem;
  ssl_certificate_key   /etc/letsencrypt/live/quipi.org/privkey.pem;
  ssl_trusted_certificate /etc/letsencrypt/live/quipi.org/chain.pem;

  ssl_session_timeout 1d;
  ssl_session_cache shared:MozSSL:10m;  # About 40000 sessions
  ssl_session_tickets off;

  location / {
      proxy_pass          http://127.0.0.1:3838/;

      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection "upgrade";
      proxy_read_timeout 600s;

      proxy_redirect    off;
      proxy_set_header  Host              $http_host;
      proxy_set_header  X-Real-IP         $remote_addr;
      proxy_set_header  X-Forwarded-For   $proxy_add_x_forwarded_for;
      proxy_set_header  X-Forwarded-Proto $scheme;
    }

}