• Becker884

      Moolevel 4
    • Post #1
    • Edited

    Hi,
    I didn´t exposed Port 443 yet. (I´ve another vm with a webserver who already use 443)
    my idea would be to change 443 to 450 (or another free port), so I could expose it and use the webUI and autodiscover/autoconfig/activsync worldwide.
    question: can I change port 443 just in mailcow.conf and change my _SRV record autodiscover.tcp 0 0 450_ finished?
    or will this break different dependencies of the services in the docker-containers ?
    or will this not work with autodiscover/autoconfig/activsync ?

    Unfortunately, I don’t know enough about it to judge and I don’t want to destroy my mailcow..

    (I use let´s encrypt certs from my reverse proxy (wildcard) )

    • esackbauer

      • Community Hero
      Moolevel 381
    • Post #2
    • Edited

    Again, as I already told, you can use your already existing reverse proxy to use port 443 also for mailcow. Do yourself a favor and learn how reverse proxies work, with multiple websites.
    This is the recommended way to use mailcow.

    Have something to say?

    Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

    • Becker884

        Moolevel 4
      • Post #3
      • Edited

      I don´t understand the docs:
      docs.mailcow.email Icon IP bindings - mailcow: dockerized documentation

      docs.mailcow.email Icon docs.mailcow.email
      IP bindings - mailcow: dockerized documentation
      None
      docs.mailcow.email

      An example IPv6 2001:db8:dead:beef::123 is given. The first suffix PORT1 defines the external port, while the second suffix PORT2 routes to the corresponding port inside the container and must not be changed.
      ...
      nginx-mailcow:
      ports:
      - '[2001:db8:dead:beef::123]:80:80'
      - '[2001:db8:dead:beef::123]:443:443'

      this example IPv6 is a public IPv6 (GUA), I don´t understand this example, my GUA is changing every night.
      I think I have to put a IPv6 from the internal docker like this one: fd4d:6169:6c63:6f77::1 or maybe another.

      no matter, I found another way for me: I forgot that I can use Port 443 on IPv6 for each device.
      So I exposed Port 443 only for IPv6, works great. (ActiveSync / Autodiscover).

      My Webserver (other VM) can keep Port 443 on IPv4 + IPv6.
      It is important for me, beacuse my cars browser don´t support IPv6 :-D

      No one is typing