
Hi,
Has anyone managed to turn off TLS 1.0/1.1 without changing the docker-compose.yml file? I've been trying and trying but either the effect didn't kick in or it locks up the whole Traefik.
So far, what I gathered is that you need to have an external config file and then have Traefik pick it up by specifying a file provider in the override file.
I have another node.js server with Traefik fronting it an it's quite easy to achieve that:
- just include the yml in a certain directory -include "traefik.http.routers.api.tls.options=default" in the labels for the service
I am uploading both the additional config and the docker-compose file for that API server.
I am just hoping I can somehow achieve the very same thing using docker-compose.override
Some references: https://www.smarthomebeginner.com/traefik-docker-compose-guide-2022/


The Traefik container in Appwrite is a bog-standard, unmodified Traefik container. There's no reason why an argument which works somewhere else shouldn't work here.

I will point out the Traefik version in your example is 2.10, whereas Appwrite v1.4.13 uses 2.9 and v1.5 uses 2.11, in case that makes any difference
Recommended threads
- Attribute creation stuck at processing f...
Hey Appwrite community! 👋 I'm running into a persistent issue with my self-hosted Appwrite installation (v1.6.1) where programmatically creating attributes fo...
- Could not open input file: /usr/src/code...
I updated my selfhosted instance to `1.6.2` and the new service (`appwrite-task-stats-resources`) failed to start. The only log message I see is: ``` Could not ...
- 401 - Project is not accessible in this ...
This is on the app write console https://screen.aryanwadhera.tech/7YTVhLTf
