I’m currently running a Nextcloud instance in docker, using the “multiple containers” method, but I recently discovered that the reccomended method to run it is using this “All In One” image I previously didn’t know about, and so I wanted to try to migrate to that setup (also in order to have easily also the office and whiteboard features that atm I don’t have on my instance + have easier Backup-restore process)

The problem is that on my server I’m using traefik as a reverse proxy to expose services to the internet, and it is working on a specific docker network (called traefik_net) where also every container that should be exposed is connected, and from the official documentation of Nextcloud AIO I really don’t understand how am I supposed to configure it to work in a setup like mine (mainly because the mastercontainer creates all the containers it needs on a network called nextcloud_aio and I didn’t find a way to change that and where to set the proper traefik lables)

Anyone that is running AIO behind a traefik reverse proxy maybe can help me to understand?

  • shaked_coffeeOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    5 hours ago

    Thank you! Idk how but I didn’t noticed the paragraph in the docs saying that labels condition is not supported. I’ll try with the file config and see if this way I can make it work. The only thing I’m still missing is the IP of the Apache container: shouldn’t it be an IP on the traefik_net network where also the traefik container runs? And if so how can I specify to the mastercontainer to create the Apache container on that network with a specific IP address?

    • wedge_film@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      2
      ·
      4 hours ago

      The cleanest way would be to do something described here, in the expanded section “On the same server in a Docker container”. I don’t know your docker setup though. You can however port forward the apache port and expose it on the machine IP, that way you can point the file config to the machine IP. This is the setup you would use if traefik was on a different machine than nextcloud (or any other service), but it will also work in your case. It has a big upside, if you decide to migrate your setup you can just spin up traefik on another machine and copy-paste the dynamic config file with minimal downtime (you would only need to adjust trusted proxy on the nextcloud side, if it’s in use).