Error 500 Cannot read properties of null (reading 'data')

Developing with Prismic
1

Hello,
I am building a project using Nuxt3 and Prismic. Everything was working until I changed the content of one of my keytext on the homepage. Nuxt is suddenly no longer able to fetch data from my Prismic repo from any of my pages. My website is on a Ubuntu server and it stopped working at the same moment than locally. I tried deleting cookies and watched for any Nuxt related problems but I dont think so.

500
Cannot read properties of null (reading 'data')

at renderComponentSubTree (D:\web-development\projects-2023\portfolio-v4\node_modules\@vue\server-renderer\dist\server-renderer.cjs.js:254:17)
at D:\web-development\projects-2023\portfolio-v4\node_modules\@vue\server-renderer\dist\server-renderer.cjs.js:185:29
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async unrollBuffer (D:\web-development\projects-2023\portfolio-v4\node_modules\@vue\server-renderer\dist\server-renderer.cjs.js:409:24)
at async unrollBuffer (D:\web-development\projects-2023\portfolio-v4\node_modules\@vue\server-renderer\dist\server-renderer.cjs.js:415:24)
at async unrollBuffer (D:\web-development\projects-2023\portfolio-v4\node_modules\@vue\server-renderer\dist\server-renderer.cjs.js:415:24)
at async unrollBuffer (D:\web-development\projects-2023\portfolio-v4\node_modules\@vue\server-renderer\dist\server-renderer.cjs.js:415:24)
at async unrollBuffer (D:\web-development\projects-2023\portfolio-v4\node_modules\@vue\server-renderer\dist\server-renderer.cjs.js:415:24)
at async unrollBuffer (D:\web-development\projects-2023\portfolio-v4\node_modules\@vue\server-renderer\dist\server-renderer.cjs.js:415:24)

Thank you in advance !

2

Seems like it is now working again !
I did nothing except creating empty new Prismic repository to test if it was related to my nuxt project.

3

It suddenly stopped working and behaves like the repo is not accessible.

We can run some specific queries like tags, but if we try to get the document then got errors.
Did you've made any updates to getting documents by query?
In the beginning, there were 500 internal server errors. After 403 erros with requesting token (what is not our case, we are not using tokens). And in the end 404.

6

I cannot query my repo.
On the web query (graphql) page, first I was getting internal_server_error and now I'm getting just open and closed quotes (""). On api web query I get error written in the result section.

From backend I get

status: 404,
statusText: 'Not Found'
headers: Headers {
        [Symbol(map)]: [Object: null prototype] {
          'content-type': [ 'application/json' ],
          'content-length': [ '0' ],
          connection: [ 'close' ],
          date: [ 'Tue, 31 Jan 2023 15:11:04 GMT' ],
          'x-amzn-requestid': [ '...' ],
          'referrer-policy': [
            'origin-when-cross-origin, strict-origin-when-cross-origin'
          ],
          'x-permitted-cross-domain-policies': [ 'master-only' ],
          'x-xss-protection': [ '1; mode=block' ],
          'x-frame-options': [ 'DENY' ],
          'x-amzn-remapped-connection': [ 'keep-alive' ],
          'x-amz-apigw-id': [ 'fnRdVHtEIAMF40A=' ],
          'x-amzn-remapped-server': [ 'nginx' ],
          'x-content-type-options': [ 'nosniff' ],
          'x-amzn-trace-id': [ 'Root=...' ],
          'x-prismic-duration': [ '206206529' ],
          'x-amzn-remapped-date': [ 'Tue, 31 Jan 2023 15:11:04 GMT' ],
          'access-control-allow-origin': [ '*' ],
          'x-cache': [ 'Error from cloudfront' ],
          via: [
            '...'
          ],
          'x-amz-cf-pop': [ 'VIE50-C2' ],
          'x-amz-cf-id': [
            '...'
          ]
        }
      },
      counter: 0
    }
  },
  statusCode: 404,
  bodyText: ''

In the web graphql api I just got

TypeError: Cannot read properties of undefined (reading 'refs')
    at https://wio-assets.s3.amazonaws.com/javascripts/graphiql.min.js:1:2256

I just want to mention that the query is basic

query {
  allProduct_familys {
    edges {
      node {
        _meta {
          id
        }
      }
    }
  }
}
7

Hello everyone, We have seen an increased error rate with the Public Content API. Our team investigated the issue and implemented the solution. Things are back to normal. We’ll follow up with the post-incident report shortly. Thanks.

2 Likes