T
tamerax

  • Jun 19, 2023
  • Joined Feb 16, 2021
  • 2 discussions
  • 8 posts
  • 1 best answer
  • Post posted... wait what? You got the answer!
  • DerLinkman
    ah there we go. Had to run remove what looked like 2 versions of docker-compose and then tried and failed a few more times but finally standalone script install instructions loaded everything up properly.

    Thank you very much for your help!

  • DerLinkman
    like the docker-compose.yml from before? Yes I deleted it and then did the git command and got the new version.

    • DerLinkman
      I tried that and that I think it updated

      root@mail:/opt/mailcow-dockerized# git checkout origin/master docker-compose.yml
      Updated 1 path from cd297314

      But it gave me the same error as above when I ran the update script. 🙁

    • I fixed this by running apt install docker-compose but now I get this error:

      ERROR: The Compose file ‘./docker-compose.yml’ is invalid because:
      services.nginx-mailcow.ports contains an invalid type, it should be a number, or an object
      services.nginx-mailcow.ports contains an invalid type, it should be a number, or an object

      Oh no, something went wrong. Please check the error message above.

      • mayk

        I used the command and it returned blank.
        Guess that means its not in my path?

      • I am trying to update my installation and this is what I am getting:

        root@mail:/opt/mailcow-dockerized# ./update.sh
        Checking internet connection… OK
        Detecting which build your mailcow runs on…
        You are receiving stable updates (master).
        To change that run the update.sh Script one time with the –nightly parameter to switch to nightly builds.
        Checking for newer update script…
        Updated 0 paths from cd297314
        Are you sure you want to update mailcow: dockerized? All containers will be stopped. [y/N] y
        Great! Native IPv6 NAT is active.
        Validating docker-compose stack configuration…
        ./update.sh: line 755: docker-compose: command not found
        Oh no, something went wrong. Please check the error message above.

        I have Docker Compose version v2.12.2 installed. Running Ubuntu 22.04.1 LTS .

        Very confused. Any help would be appreciated?

        • DerLinkman
          ah there we go. Had to run remove what looked like 2 versions of docker-compose and then tried and failed a few more times but finally standalone script install instructions loaded everything up properly.

          Thank you very much for your help!

      • Good morning
        Since I turned Watchdog on, I get almost 50 emails a day about banned ip notifications. I read in an older Github post there is a way to turn this off and it was going to be a switch in the UI but I haven’t found it yet.
        I also read I can control the ban time and how to block an IP range entirely through the UI and I am not sure where I would find this. Is it in Fail2Ban?
        Thank you and sorry for are probably very newbie questions.

        • MAGIC replied to this.
        • Hello,

          tamerax Since I turned Watchdog on, I get almost 50 emails a day about banned ip notifications. I read in an older Github post there is a way to turn this off and it was going to be a switch in the UI but I haven’t found it yet.

          You can disable mails for IP bans in your mailcow.conf: https://github.com/mailcow/mailcow-dockerized/blob/master/generate_config.sh#L280

          tamerax I also read I can control the ban time and how to block an IP range entirely through the UI and I am not sure where I would find this. Is it in Fail2Ban?

          See the picture with the arrows 🙂