Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reverse-proxy configuration for Dozzle : chunked_transfer_encoding off or on ? #3524

Closed
1 task done
omasseau opened this issue Jan 8, 2025 · 2 comments
Closed
1 task done
Labels
bug Something isn't working

Comments

@omasseau
Copy link

omasseau commented Jan 8, 2025

πŸ” Check for existing issues

  • Completed

How is Dozzle deployed?

Standalone Deployment

πŸ“¦ Dozzle version

8.10.1

βœ… Command used to run Dozzle

πŸ› Describe the bug / provide steps to reproduce it

Not really a bug, but a question about configuration of a reverse-proxy, so that we can be sure that the reverse-proxy is not the cause of some strange behaviours.

In the documentation FAQ (https://dozzle.dev/guide/faq#i-installed-dozzle-but-logs-are-slow-or-they-never-load-what-do-i-do) you say to add these directives to disable proxy buffering in nginx :

        proxy_buffering             off;
        proxy_cache                 off;

But here https://dozzle.dev/guide/changing-base I see you also added the chunked_transfer_encoding off; directive :

    chunked_transfer_encoding off;
    proxy_buffering off;
    proxy_cache off;

So it is a bit confusing if chunked_transfer_encoding off; should be set or not to have Dozzle work correctly behing a reverse-proxy (as I understand chuncked transfer encoding is generally useful for SSE).

Thanks a lot ;)

πŸ’» Environment

πŸ“Έ If applicable, add screenshots to help explain your bug

No response

πŸ“œ If applicable, attach your Dozzle logs. You many need to enable debug mode. See https://dozzle.dev/guide/debugging.

No response

@omasseau omasseau added the bug Something isn't working label Jan 8, 2025
@amir20
Copy link
Owner

amir20 commented Jan 8, 2025

Personally, I don't think you need any of them because Dozzle sends X-Accel-Buffering: no which should disable all buffering.

What are you seeing? Is it not working out of the box?

Also, should I enable discussions? Seems like a lot of people just have questions that are not issues. :)

@amir20 amir20 closed this as not planned Won't fix, can't repro, duplicate, stale Jan 8, 2025
@omasseau
Copy link
Author

omasseau commented Jan 13, 2025

Personally, I don't think you need any of them because Dozzle sends X-Accel-Buffering: no which should disable all buffering.

What are you seeing? Is it not working out of the box?

Also, should I enable discussions? Seems like a lot of people just have questions that are not issues. :)

OK thanks for the answer.
We suspect our web host to have forced buffering on its reverse-proxy (even with X-Accel-Buffering header sent) and need to provide him infos on the necessary configuration on its side specifically for dozzle endpoint. I wanted to be sure to provide him the right infos.

We will try with just proxy_buffering off; then and not add chunked_transfer_encoding off ;)

Indeed it would be great to enable Discussions :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants