stencila/hub

Download snapshot returns 500 Internal Server Error

fred-atherden opened this issue · 4 comments

nokome commented

Thanks for reporting this @FAtherden-eLife

  • This bug has been fixed in 118d1c0, and deployed in v4.24.3

  • It was caused by the internal location @account-content not being in the appropriate Nginx server block

  • The error first appeared in Nginx logs at 2020/12/07 00:49:04 UTC [error] 7#7: *1754 could not find named location "@account-content" while reading response header from upstream... just after the deployment of v4.24.0

  • The @account-content location had been in the wrong server block for some time but it seems that location had not actually been used until this commit 90cf983

  • We were not alerted of this error until this issue was raised. There was already a mechanism in place to report Nginx 502 and 504 errors to Sentry. This has now been expanded to include all 500 errors.

nokome commented

I have also created a related issue here: #898

nokome commented

Unfortunately there seems to be some sort of regression here such that now the archives are being served but not images. Will re-add the original (now duplicate) @account-content location as an attempt at a quick fix.

nokome commented

Hot fix to router worked but will hold of pushing the fix to master until tomorrow morning following more testing.