HTTP 500, Found #835
-
|
When I configure Sablier with the blocking strategy with Traefik, the service spins up and returns HTTP 500 with body content "Found". If I then reload again, I get the service in question successfully. I suspect it has something to do with #240 theorizing that Sablier releases the block before Traefik establishes the route. provider:
name: docker
docker:
strategy: stop
server:
port: 10000
base-path: /
storage:
file:
sessions:
default-duration: 5m
logging:
level: debug
strategy:
dynamic:
show-details-by-default: true
default-theme: ghost
default-refresh-frequency: 5s
blocking:
default-timeout: 30sLabels on my meilisearch docker compose instance: labels:
- homelan.group=apps
- traefik.http.routers.meilisearch.rule=Host(`meilisearch.home.lan`)
- traefik.http.routers.meilisearch.tls=true
- sablier.enable=true
- sablier.group=meilisearch-group
- traefik.http.services.meilisearch.loadbalancer.server.port=7700
- traefik.http.routers.meilisearch.middlewares=meilisearch-sablier
- traefik.http.middlewares.meilisearch-sablier.plugin.sablier.endpoint=http://sablier:10000
- traefik.http.middlewares.meilisearch-sablier.plugin.sablier.group=meilisearch-group
- traefik.http.middlewares.meilisearch-sablier.plugin.sablier.blocking.timeout=30s
- traefik.docker.allownonrunning=trueHave I misconfigured obvious here? Dynamic strategy isn't ideal for services that aren't accessed via browsers directly, so I'd really love to get blocking strategy working. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
Can you print Sablier logs ? |
Beta Was this translation helpful? Give feedback.
I was able to interpret that and do the following:
which fixed it.