From bad220c3040d2b0a798ce5a0357d222580451fa7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebastian=20Kr=C3=BCger?= Date: Thu, 6 Nov 2025 18:35:01 +0100 Subject: [PATCH] fix: define VERT service in file provider instead of referencing Docker provider MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fixed "the service 'vert-web-secure@docker' does not exist" error by defining the service directly in the vert-sablier.yaml file provider configuration. Previously, the router was defined in the file provider but tried to reference a service from the Docker provider (@docker suffix), which caused a mismatch. Now both the router and service are defined in the same file provider, while still using Docker-based middlewares (auth, compression). Changes: - Added services.vert-web-secure with loadBalancer pointing to vert_app:80 - Changed router service reference from "vert-web-secure@docker" to "vert-web-secure" 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- proxy/dynamic/vert-sablier.yaml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/proxy/dynamic/vert-sablier.yaml b/proxy/dynamic/vert-sablier.yaml index 1697f86..af5f059 100644 --- a/proxy/dynamic/vert-sablier.yaml +++ b/proxy/dynamic/vert-sablier.yaml @@ -10,10 +10,16 @@ http: displayName: VERT File Converter theme: ghost + services: + vert-web-secure: + loadBalancer: + servers: + - url: "http://vert_app:80" + routers: vert-web-secure: rule: "Host(`vert.pivoine.art`)" - service: vert-web-secure@docker + service: vert-web-secure entryPoints: - web-secure middlewares: