Trying to run Hasura locally with nginx in front of it, getting v1/graphql, console seems busted?

[atrauzzi]

Version Information

Server Version: v2.43.0
Console Asset Version: 1723130278163

Environment

Local on my workstation.

What is the current behaviour?

Trying to run Hasura locally with nginx in front of it, getting requests to v1/graphql in the network console.

What is the expected behaviour?

No bad requests in the network panel.

How to reproduce the issue?

Using some nginx boilerplate I keep around for doing reverse proxy of local services on *.localdev.com. In this case, hasura.localdev.com:

server {
        listen 443 ssl;
        server_name ~^hasura(\..*)\.localdev\.com$;

        location @websocket {
            proxy_pass http://hasura:8078;
        }

        location / {
            proxy_read_timeout 30s;
            proxy_http_version 1.1;
            proxy_redirect off;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "upgrade";
            proxy_set_header Host $host;
            proxy_pass http://hasura:8078;
        }
    }

Run the container via podman with standard parameters, make sure it can see postgres, etc...

You'll also need to configure DNS somehow to correctly resolve your workstation (I use dnsmasq as part of NetworkManager on Fedora).

I do this kind of setup so that I can get standard CORS behaviour.

Screenshots or Screencast

Keywords

• /v1/graphql
• Fedora
• DNS
• Local
• nginx
• podman

[loliuy]

Not only the nginx , when i use docker to deploy , same issue. The apiURL.ts file has the wrong url.