504 Gateway timeout error

Follow

Andra Kidwell

April 21, 2017 20:29

Hello,

I'm working on the United States Holocaust Memorial Museum collection. One of the seeds, http://efilms.ushmm.org/ (Ephemeral Films Project) doesn't load the contents of the page. After looking through the latest test crawl report, it seems that all the URLs captured, nothing was blocked or queued. When I click to view the URL in test Wayback, an error appears: "504 Gateway timeout. The Server didn't respond in time."

I went back and double checked how the page captured in our last production crawl, and the same thing happened. We captured all the URLs, but the page doesn't load the contents. The same error appears. I also tried the page in proxy mode and that error appears again. I welcome any help and insight you have. I'm not sure what to try next.

Thank you!
Andra

0

• Official comment

  

  Jillian Lohndorf April 21, 2017 20:31

  Hi Andra,

  Our engineers have pushed a fix for this issue. It turns out that 80% of the site's content was coming from a single line of JavaScript, and the time it took to load was longer than our default replay settings. We have increased the default loading time from 30 seconds to 2 minutes, which should reduce the likelihood of this occurring. If you save this crawl, you should see the fix apply to other crawls of this seed as well.

  If you see this error message in the future, whether it’s on a seed, a sub-page, or throughout an entire site, it’s worthwhile checking in with us so we can investigate the cause and its resolution.

  Best,
  Jillian

  Comment actions Permalink
• 

  Andra Kidwell April 21, 2017 20:46

  Hi Jillian,

  Thank you for your quick work! That seems odd to place that much on one line of JS. I’m glad the engineers were able to figure something out for us. I’ll save the test crawl and let you know how it goes.

  Thanks,
  Andra

  0

  Comment actions Permalink

Please sign in to leave a comment.