[1.4.0.2] header X-Accel-Mapping missing

[Dryusdan]

Hi
After lot of problem for migration (forgot make persistance data for pack folder ><) I display mastodon logs and console show the same error :
X-Accel-Mapping header missing
But, how to configure this ? Because I don't use passenger for nginx (just proxy_pass)

Any idea ?

[OccultWarlock]

I have the same issue with Caddy

[beatrix-bitrot]

I don't use nginx or docker and have this issue, would be nice to know what's going on here.

[Dryusdan]

I remove docker tag to correspond with your problem :)

[dereckson]

So, this issue indeed isn't dependant of Docker, but it's a feature of nginx and rails.

References:

• https://mattbrictson.com/accelerated-rails-downloads
• https://www.nginx.com/resources/wiki/start/topics/examples/x-accel/ explains the X-Accel feature from nginx point of view

[Gargron]

Do you have RAILS_SERVE_STATIC_FILES set in your environment?

[OccultWarlock]

I do

…

Sent from my iPad

On May 26, 2017, at 8:03 AM, Eugen Rochko ***@***.***> wrote: Do you have RAILS_SERVE_STATIC_FILES set in your environment? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[Gargron]

It's a thing that happens when Puma/Rails serves static files (it is recommended to serve static files directly through nginx, because it is way faster, but it may not be possible if, for example, you're running a precompiled Docker image instead of having checked out source code available). I have not used this feature, but here is documentation on it: https://www.nginx.com/resources/wiki/start/topics/examples/x-accel/

As far as I understand this message in the logs is non-breaking. Everything still works, right? Except serving files is slower than it could be directly through nginx.

[OccultWarlock]

I use Caddy, not Nginx - so I just need to figure out how to convert the nginx config for that over to Caddy haha. But other than that, no, it doesn't break anything - just spams terminal 🙃

…

Sent from my iPad

On May 26, 2017, at 8:09 AM, Eugen Rochko ***@***.***> wrote: It's a thing that happens when Puma/Rails serves static files (it is recommended to serve static files directly through nginx, because it is way faster, but it may not be possible if, for example, you're running a precompiled Docker image instead of having checked out source code available). I have not used this feature, but here is documentation on it: https://www.nginx.com/resources/wiki/start/topics/examples/x-accel/ As far as I understand this message in the logs is non-breaking. Everything still works, right? Except serving files is slower than it could be directly through nginx. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[Gargron]

https://caddyserver.com/docs/internal

[OccultWarlock]

Thanks 😊 So would it be... internal /mastodon/public/

…

Sent from my iPad

On May 26, 2017, at 8:34 AM, Eugen Rochko ***@***.***> wrote: https://caddyserver.com/docs/internal — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[OccultWarlock]

You Follow up, I turned RAILS_SERVE_STATIC_FILES off, I added internal /mastodon/public To my caddyfile. Everything seems to still load currently, but I'm still getting this web_1 | X-Accel-Mapping header missing web_1 | X-Accel-Mapping header missing web_1 | X-Accel-Mapping header missing web_1 | X-Accel-Mapping header missing web_1 | X-Accel-Mapping header missing web_1 | X-Accel-Mapping header missing web_1 | X-Accel-Mapping header missing web_1 | X-Accel-Mapping header missing web_1 | X-Accel-Mapping header missing web_1 | X-Accel-Mapping header missing web_1 | X-Accel-Mapping header missing web_1 | X-Accel-Mapping header missing

…

Sent from my iPad

On May 26, 2017, at 8:50 AM, Glen Nofsinger ***@***.***> wrote: Thanks 😊 So would it be... internal /mastodon/public/ Sent from my iPad > On May 26, 2017, at 8:34 AM, Eugen Rochko ***@***.***> wrote: > > https://caddyserver.com/docs/internal > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub, or mute the thread. >

[Gargron]

All I can find is this?

[OccultWarlock]

Not sure what this has to do with Caddy 🤷🏼‍♂️ I'm really not too concerned about this though, as everything seems to work properly regardless of getting spammed with the error message lol. As far as I'm concerned- this can be closed

…

Sent from my iPhone

On May 26, 2017, at 9:41 AM, Eugen Rochko ***@***.***> wrote: All I can find is this? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[Gargron]

Well basically you might have to pass another header to Puma, but I have no idea. And yeah.