I think that problem is due to TLS termination. I have the same issue with the same configuration and I not find a solution.Ĭan you share your configuration here? Because it doesn’t sound like yours is the exactly the same, because otherwise you would not get the “bad gateway” error.

I need to find a way to get these URLs to start with https. When I try to load a document, the Nextcloud page is attempting to load resources (like javascript files). Traefik is ensuring that all traffic to the Nextcloud and Collabora instances is TLS encrypted, but those servers themselves are operating in http mode. The problem seems to be that the Nextcloud instance thinks it is http instead of https, and so I get an error when I save the Collabora URL due to this “mismatch”.

In the Nextcloud settings the URL is set to.

My current configuration (below) should be correct for Collabora itself. '_ups_example_com_app.entrypoints=https' '_ups_example_com_app-http.entrypoints=http' opt//db:/var/lib/mysqlĬontainer_name: cloud_ups_example_com_app opt/traefik/acme.json:/etc/traefik/acme.jsonĬommand: -transaction-isolation=READ-COMMITTED -binlog-format=ROW opt/traefik/config.yaml:/etc/traefik/config.yaml opt/traefik/traefik.yaml:/etc/traefik/traefik.yaml var/run/docker.sock:/var/run/docker.sock Unfortunately the body of the page is “Bad Gateway”, which usually means something is not working at the reverse proxy level for connecting ports, but I cannot figure out how to correct the configuration. The docker-compose config file below brings up both Nextcloud and Collabora servers, and I can even visit the Collabora server URL at and see a valid TLS cert in my browser. However, I am unable to get a Collabora server online. So far, the Nextcloud server itself and the certificate generation are all working smoothly. I am trying to deploy Nextcloud using docker-compose, with Traefik acting as the reverse proxy and automatic LetsEncrypt TLS certificate installer.

Err 502 openoffice