1. Home
  2. Bugs

Clicking attachment would result nginx 500 Internal Server Error

By @melanopsis2018-08-09 16:55:34.057Z2018-08-09 23:19:59.507Z

Hi @KajMagnus, after the last deployment (on premise, v0.6.9-WIP-3-75eef8fa4), we are no longer able to open/save attachments. Following the attachment link would throw an internal server error.

Here's what I see in the console (domain name edited)

Error calling /-/pubsub/subscribe/1-100?reqNr=1: {"xhr":{}}, details:  slim-bundle.min.js:10:269972
	c/< https://domain.com/-/assets/266/slim-bundle.min.js:10:269972

The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol.

nginx error log entry

2018/08/09 10:25:34 [error] 12#12: *2604 lua entry thread aborted: runtime error: access_by_lua(server-locations.conf:162):2: http2 requests not supported yet
stack traceback:
coroutine 0:
        [C]: in function 'capture'
        access_by_lua(server-locations.conf:162):2: in function <access_by_lua(server-locations.conf:162):1>, client:, server: _, request: "GET /-/u/uzwt435xvo/4/w/6a/7rtdl45lvs57sexqwlvv75hpui5fxx.pdf HTTP/2.0", host: "domain.com", referrer: "https://domain.com/-21/topic"

  • 5 replies
  1. M
    @melanopsis2018-08-09 23:46:14.035Z

    The issue was partially on my side with the nginx configuration. I enable HTTP2 in the config and the recent changes in talkyard somehow triggered the nginx error. Removing http2 from the configuration fixed the issue.

    1. KajMagnus @KajMagnus2018-08-10 16:59:13.095Z

      Thanks for posting the error, and for the follow-up message & explanation. Good to know that HTTP2 currently causes these problems. I now documented this in the installation readme file: added "Do not enable HTTP2, currently doesn't work with Nginx + the Lua module" as a post installation "step".

    2. M@melanopsis marked this topic as Planned 2018-08-09 23:45:09.129Z.
    3. M@melanopsis marked this topic as Started 2018-08-09 23:45:10.257Z.
    4. M@melanopsis marked this topic as Done 2018-08-09 23:45:13.128Z.