Skip to content

fix: tell traefik which network to reach opencloud through - #411

Merged
AlexAndBear merged 3 commits into
mainfrom
fix/imagor-traefik-network
Oct 27, 2026
Merged

AlexAndBear merged 3 commits into
mainfrom
fix/imagor-traefik-network

Conversation

@AlexAndBear

@AlexAndBear AlexAndBear commented Oct 27, 2026 •

Copy link
Copy Markdown
Member

With the imagor module, opencloud is in two networks: opencloud-net and the internal imagor-net. Traefik is only in opencloud-net, and without traefik.docker.network it picks one of the container's IPs at random. When it picks the imagor-net IP, every request times out (504 Gateway Timeout ... dial tcp 172.20.0.3:9200: i/o timeout), so after a restart opencloud is reachable only sometimes. We hit this on the demo server after enabling imagor.

The label now sits on the opencloud service in traefik/opencloud.yml, so any module that puts opencloud into another network is covered too. ${COMPOSE_PROJECT_NAME}_opencloud-net resolves to the actual network name, checked with docker compose config with and without imagor.

Follow-up to #407.

@AlexAndBear AlexAndBear self-assigned this Oct 27, 2026
@AlexAndBear
AlexAndBear requested a review from dschmidt October 27, 2026 16:12
@AlexAndBear
AlexAndBear requested a review from kulmann October 27, 2026 16:13
@AlexAndBear AlexAndBear changed the title fix: tell traefik which network to reach opencloud through with imagor fix: tell traefik which network to reach opencloud through Oct 27, 2026
@AlexAndBear
AlexAndBear merged commit 91911a5 into main Oct 27, 2026
@AlexAndBear
AlexAndBear deleted the fix/imagor-traefik-network branch October 27, 2026 16:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants