Subject: Issues I hit upgrading from 7.1.0 → 7.2.0 — sharing in case it helps

[rkraken]

I just upgraded from 7.1.0 to 7.2.0 following the standard upgrade guide and ran into several issues. Posting here in case others hit the same things.

1. The collaboration service no longer runs as a separate container
   After the upgrade I had an orphan collaboration container left over from the old architecture. It caused an error on docker compose up. I cleaned it up with:

docker compose up -d --remove-orphans

I also had a wopiserver.* domain configured in my reverse proxy that is no longer needed — WOPI is now handled inside the main OpenCloud process.

2. docker compose up fail error: "service tika has neither an image nor a build context specified"
   This is because docker-compose.yml now references tika but it wasn't in my COMPOSE_FILE in .env since I'd never enabled it. I added search/tika.yml to COMPOSE_FILE to resolve it. It seems that this was previously optional, but is now expected by default.

3. My remote reverse proxy stopped working after the upgrade (affects users with proxy on a different host)
   My reverse proxy runs on a separate VPS and connects to my opencloud host over VPN. After the upgrade, my opencloud page returned error 502. I traced it to entries in the external-proxy/ compose files — the ports: mappings are bound to 127.0.0.1 (localhost only), making them unreachable from a remote host. I fixed it by changing them manually:

# external-proxy/opencloud.yml
ports:
  - "0.0.0.0:9200:9200"

# external-proxy/collabora.yml
ports:
  - "0.0.0.0:9980:9980"

The collabora.yml port issue might have been uncovered due to the architectural change #1. I believe the opencloud.yml port issue could be a bug as it was contradictory to another line in the file (PROXY_HTTP_ADDR: "0.0.0.0:9200")