NetworkError when attempting to fetch resource

paul-grist · November 2, 2022, 3:40pm

For the ports setting of 127.0.0.1:58484:8484, sounds like there is a reverse proxy wrapping Grist, is that right? Can you check if it is configured to preserve the Host header? For Nginx I think this would be something like proxy_set_header Host $http_host;

For historic reasons, Grist automatically tries to adapt to the Host in a few ways:

github.com

gristlabs/grist-core/blob/eea2ef5cfb4fb4ee975a1e85414edea5394765f1/app/server/lib/requestUtils.ts#L37

      
        
            
            
/**
             * Adapt a home-server or doc-worker URL to match the hostname in the request URL. For custom
             * domains and when GRIST_SERVE_SAME_ORIGIN is set, we replace the full hostname; otherwise just
             * the base of the hostname. The changes to url are made in-place.
             *
             * For dev purposes, port is kept but possibly adjusted for TEST_HTTPS_OFFSET. Note that if port
             * is different from req's port, it is not considered same-origin for CORS purposes, but would
             * still receive cookies.
             */
            export function adaptServerUrl(url: URL, req: RequestWithOrg): void {
              const reqBaseDomain = parseSubdomain(req.hostname).base;
            
            
  if (process.env.GRIST_SERVE_SAME_ORIGIN === 'true' || req.isCustomHost) {
                url.hostname = req.hostname;
              } else if (reqBaseDomain) {
                const subdomain: string|undefined = parseSubdomain(url.hostname).org || DEFAULT_HOME_SUBDOMAIN;
                url.hostname = `${subdomain}${reqBaseDomain}`;
              }
            
            
  // In dev/test environment we can turn on a flag to adjust URLs to use https.

None of them are really appropriate for a simple self-hosting setup. I’ll look into simplifying this. I think in your setup Grist mistakenly believes it is hosted at 127.0.0.1.