500 errors when being crawled - how to verify?

Support
,
1

Hi all,

I am currently investigating issues with our Gatsby based site that when crawled, is returning 500 errors with pre-rendering enabled.

Although we do not use SSR/DSG, I am told we still need pre-rendering, so cannot disable it.

01JWDR09RYMMWX8WBZCHW14DFK
01JWDR0A1EMRX94YEDBZ95T2BP
01JWDR07SP9C0EG3RCPZY864A6

Is anyone able to verify that it’s the cause of the 500 errors before we proceed with upgrading etc?

Without any error logs, I cannot verify that it’s not an issue with the site, so want to rule that out first.

Thanks

2

@inspired If you’re talking about Netlify’s prerendering, see the answer/discussion in this thread:

3

Thanks @nathanmartin

I was hoping to get confirmation from Netlify using the provided request IDs to make sure there wasn’t something else causing this.

As we are currently using the free account, we have no way of reviewing anything but build logs.

Whilst I’m confident it is just related to the prerendering, we need to rule out any potential issues that could be resolved on our end before having to upgrade and implement an external prerendering service.

Appreciate your help

4

@inspired That’s fine, I just know how they usually respond, (which you’ll see in the linked thread), and had provided that info to save you time/effort.

As they barely support the service, you might find they’re a bit reluctant to spend time providing support regarding it.

However I definitely don’t speak for them, perhaps you’ll get lucky.

Also, just to confirm, are you suggesting you don’t have access to Function Logs?
https://docs.netlify.com/functions/logs/#access-function-logs

5

Hi @nathanmartin

Thanks for getting back to me so quickly.

I get that impression from the response to my support request.

That being said, I have seen some instances where support has asked for the request id and have been able to investigate via the forums.

When looking into this, a lot of places mentioned checking the function logs but I only have a function log for a function located in the /functions folder.

From what I understand, there should be another log for Gatsby that handles the http requests but I can’t find it.

6

Out of interest @nathanmartin, are you aware if the internal prerender service that Netlify provide is connected with the plan you are on?

For example, the prerender on the Free/Starter account has less resources than that on Pro etc?

7

I don’t believe that to be the case, and I don’t expect it to be related to your issue.

As I understand it the Prerendering just sometimes results in 500 errors.
If you search you’ll find many threads raising it, here’s a few:
https://answers.netlify.com/t/netlify-pre-rendering-and-5xx-errors/64329
https://answers.netlify.com/t/sporadic-http-500-errors/143383
https://answers.netlify.com/t/google-wont-index-my-site-due-to-netlify-server-errors/118534

You’ll be able to find more if you search yourself.

That said if you are on a ‘Pro’ plan you can use External Services.

8

I double checked the three request IDs you provided and can confirm those are related to prerendering.

I’d recommend checking out this support guide for troubleshooting tips:

It’s important to note that the Netlify’s prerendering is in Beta and we don’t recommend it for mission critical sites.

If you’re interested in trying prerendering with an external service, this is possible on a Pro plan. We recommend the following third-party services: