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
- [SOLVED] Error upgrading from 1.8.1 to 1...
DO Self-hosted server failed to upgrade with this error "Error response from daemon: client version 1.52 is too new. Maximum supported API version is 1.42". U...
- MariaDB refuses to connect to appwrite
Earlier, I tried updating my Appwrite version from 18.1.x to the latest release because my Flutter package required it to function properly. I used the official...
- Custom API domain is unreachable
Earlier my custom api domain was working fine. Now it seems to be offline without a trace a few hours later. I didn't change anything, all the relevant DNS reco...