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

[Bug]: Enable gzip compression and Strip Prefixes settings are not applied to docker-compose project #2105

Open
ro-bit-admin opened this issue May 1, 2024 · 7 comments
Labels
🐞 Confirmed Bug Verified issues that have been reproduced by the team.

Comments

@ro-bit-admin
Copy link

Description

Traefik labels for gzip and strip-prefix middlewares are present docker-compose.yml even though they are unchecked in the Advanced settings tab.

Minimal Reproduction (if possible, example repository)

image
image
image

Exception or Error

No response

Version

v4.0.0-beta.271

@andrasbacsai andrasbacsai self-assigned this May 1, 2024
@andrasbacsai andrasbacsai added the 🐛 Bug Reported issues that need to be reproduced by the team. label May 1, 2024 — with Linear
@ro-bit-admin
Copy link
Author

Hi @andrasbacsai.

Any update on this issue so far?

@peaklabs-dev peaklabs-dev added the 🐞 Confirmed Bug Verified issues that have been reproduced by the team. label Oct 23, 2024
@peaklabs-dev peaklabs-dev added this to the v4.0.0 Stable Release milestone Oct 23, 2024
@peaklabs-dev
Copy link
Member

Developer Note (for confirmed bugs).
Reproduction steps:

  1. Simply add a docker compose project via git.
  2. Check the compose file.

-> Now I think the labels are never applied if you enable or disabled gzip or strip-prefix, there are no labels applied.

@peaklabs-dev peaklabs-dev removed the 🐛 Bug Reported issues that need to be reproduced by the team. label Oct 24, 2024
@steve-noel
Copy link

Hi @peaklabs-dev @andrasbacsai ,

Do you guys have any update on this?

Thanks

@yuanzhixiang
Copy link

I’ve spent the entire afternoon troubleshooting why my WebSocket connection wasn’t receiving any responses, only to discover that the issue is caused by gzip compression. Unfortunately, there’s no way to disable gzip compression when deploying through Coolify, which leaves me with no choice but to abandon this platform. This limitation is extremely frustrating and frankly quite disappointing.

@yuanzhixiang
Copy link

I’m encountering the issue of automatic port detection errors again. My container has two web ports, 6003 and 8080. In the console, I set 6003 as the exposed port, and the Traefik load balancer is also set to 6003. However, once deployed, the proxy redirects to 8080 instead. Can you please stick to managing the deployment framework without changing the network settings arbitrarily? Currently, there isn’t even an option to manually correct the network configuration. This is incredibly frustrating. If there are so many bugs, then at least give users the ability to manually override settings. Don’t hide a silent refresh somewhere that changes configurations to settings inconsistent with what’s displayed. This approach is extremely frustrating.

@louisheal
Copy link

I was trying to use SSE (Server-Sent Events) with an app deployed on Coolify, to do that I needed to disable gzip compression, however the button does not work.
I managed to find a workaround, here it is for anyone who is struggling with this too:

  • Open the resource you would like to disable gzip on
  • Select Configuration -> General and scroll down until you see Network
  • Untick "Readonly labels"
  • Remove the following lines:
    • traefik.http.middlewares.gzip.compress=true
    • traefik.http.routers.https-xyz.middlewares=gzip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 Confirmed Bug Verified issues that have been reproduced by the team.
Projects
None yet
Development

No branches or pull requests

6 participants