Reverse proxy documentation does not support Traefik v2.x

[patryk-tech]

Hey! Thanks for this project, I am currently trying to deploy it on a server. While doing so, I have noticed that the configuration instructions for Traefik only provide the configuration for Traefik <= v1.7, as they use [[acme.domains]].

In Traefik v2+, SANs should be defined under routers, in the dynamic configuration, or under entrypoints, in the static config.

Examples from the traefik docs below...

---

Dynamic configuration examples using routers

TOML

## Dynamic configuration
[http.routers]
  [http.routers.routerbar]
    rule = "Host(`snitest.com`) && Path(`/bar`)"
    [http.routers.routerbar.tls]
      certResolver = "bar"
      [[http.routers.routerbar.tls.domains]]
        main = "snitest.com"
        sans = ["*.snitest.com"]

YAML

## Dynamic configuration
http:
  routers:
    routerbar:
      rule: "Host(`snitest.com`) && Path(`/bar`)"
      tls:
        certResolver: "bar"
        domains:
          - main: "snitest.com"
            sans:
              - "*.snitest.com"

Docker Labels

  - "traefik.http.routers.router1.tls.domains[0].main=foobar"
  - "traefik.http.routers.router1.tls.domains[0].sans=foobar, foobar"
  - "traefik.http.routers.router1.tls.domains[1].main=foobar"
  - "traefik.http.routers.router1.tls.domains[1].sans=foobar, foobar"

• https://docs.traefik.io/routing/routers/#domains
• https://docs.traefik.io/reference/dynamic-configuration/docker/

---

Static configuration using entrypoints

TOML file

[entryPoints]
  [entryPoints.EntryPoint0]
    address = "foobar"
    [entryPoints.EntryPoint0.http]
      [entryPoints.EntryPoint0.http.tls]
        [[entryPoints.EntryPoint0.http.tls.domains]]
          main = "foobar"
          sans = ["foobar", "foobar"]

YAML file

entryPoints:
  EntryPoint0:
    address: foobar
    http:
      tls:
        domains:
        - main: foobar
          sans:
          - foobar
          - foobar

• https://docs.traefik.io/reference/static-configuration/file/

[Nebukadneza]

Hi There,

The Mailu-Project is currently in a bit of a bind! We are short on man-power, and we need to judge if it is possible for us to put in some work on this issue.

To help with that, we are currently trying to find out which issues are actively keeping users from using Mailu, which issues have someone who want to work on them — and which issues may be less important. These a less important ones could be discarded for the time being, until the project is in a more stable and regular state once again.

In order for us to better assess this, it would be helpful if you could put a reaction on this post (use the 😃 icon to the top-right).

• 👍️ if you need this to be able to use Mailu. Ideally, you’d also be able to test this on your installation, and provide feedback …
• 🎉 if you find it a nice bonus, but no deal-breaker
• 🚀 if you want to work on it yourself!
  We want to keep this voting open for 2 weeks from now, so please help out!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Diman0]

@patryk-tech are you willing to send a PR to update the documentation with these updated instructions?

The contributing workflow can be found here: https://mailu.io/master/contributors/workflow.html
How to set up your DEV environment here: https://mailu.io/master/contributors/environment.html
And finally instructions for testing the documentation here: https://mailu.io/master/contributors/environment.html#documentation

[patryk-tech]

Hey!

Sure, Hacktoberfest guilted me into giving it a try.