Tukukkk

I tried to setup a reverse proxy with nginx, and after the changes I made, the page where I view our json data for our api (www.ourapihost.com/issues.json) is now timing out with the error

We're sorry but something went wrong. If you are the application owner check the logs for more information.

However, the logs are blank. I had to clear them because it was taking too long to cat the logfile, but when I try to refresh the page, it keeps timing out with the above error, and it's not adding anything to the log.

This is our current nginx configuration:

server {

    listen 80; #443 ssl http2;







    server_name <our server domain>;

    root /home/deployer/ft_parks/current/public;

    access_log  /var/log/nginx/wilderness-patrol.net_access.log;

#    error_log   /var/log/nginx/wilderness-patrol.net_error.log;

    client_max_body_size 4M; 

    client_body_buffer_size 128k;

    keepalive_timeout 200;



    error_page 500 502 503 504 /500.html;



    try_files $uri @app;



#    include /etc/nginx/snippets/letsencrypt-acme-challenge.conf;



  open_file_cache          max=2000 inactive=20s;

  open_file_cache_valid    60s;

  open_file_cache_min_uses 5;

  open_file_cache_errors   off;

  location @app {

    proxy_pass        http://wp_server;

    proxy_set_header  Host $http_host;

    proxy_set_header  X-Forwarded-For $proxy_add_x_forwarded_for;

    proxy_redirect    off;

  }

  error_page 500 502 503 504 /500.html;



#   location /issues {

#         add_header 'Access-Control-Allow-Origin' '*';

#         add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';

#         add_header 'Access-Control-Allow-Headers' 'User-Agent,Keep-Alive,Content-Type';

#         add_header 'Access-Control-Expose-Headers' 'Content-Length,Content-Range';

#         proxy_pass  http://<my ip>:3001/;

#     }



  location ^~ /assets/ {

    gzip_static on; 

    expires max;

    add_header Cache-Control public;

    location ~* .(jpg|jpeg|gif|png|css|js|ico|xml|svg)$ {

      access_log        off;

      log_not_found     off;

      expires           30d;

   }   

  }



  location = /500.html {

    root /home/deployer/ft_parks/current/public;

  }

}

The location /issues block that is commented out is the section I added to try and add the reverse proxy. My webpack server is running on localhost:3001.

I have read several other related posts here on stackoverflow about this issue, and have tried all of the solutions they suggested, but none of them worked for me. I feel like I'm either missing something in my location /issues block, or that I'm just simply not writing it properly. I have also already tryed using the rack-cors gem, which I couldn't get working either.

Any advice? Thanks!