diff --git a/.github/ISSUE_TEMPLATE/Bug_report.md b/.github/ISSUE_TEMPLATE/Bug_report.md index de564e58..2071195d 100644 --- a/.github/ISSUE_TEMPLATE/Bug_report.md +++ b/.github/ISSUE_TEMPLATE/Bug_report.md @@ -3,28 +3,63 @@ name: Bug report about: Report a bug for this project --- + -**README and remove me** -For community support and other discussion, you are welcome to visit and stay with us @ Freenode, #mailcow -Answering can take a few seconds up to many hours, please be patient. -Commercial support, including a ticket system, can be found @ https://www.servercow.de/mailcow#support - we are also available via Telegram. \o/ +**Prior to placing the issue, please check following:** *(fill out each checkbox with a `X` once done)* +- [ ] I understand that not following below instructions might result in immediate closing and deletion of my issue. +- [ ] I have understood that answers are voluntary and community-driven, and not commercial support. +- [ ] I have verified that my issue has not been already answered in the past. I also checked previous [issues](https://github.com/mailcow/mailcow-dockerized/issues). -**Describe the bug, try to make it reproducible** -A clear and concise description of what the bug is. How can it be reproduced? -If applicable, add screenshots to help explain your problem. Very useful for bugs in mailcow UI. +--- -**System information and quick debugging** -General logs: -- Please take a look at the [documentation](https://mailcow.github.io/mailcow-dockerized-docs/debug-logs/). +**Description of the bug**: What kind of issue have you *exactly* come across? + + +My issue is... + +**Reproduction of said bug**: How *exactly* do you reproduce the bug? + + +1. I go to... +2. And then to... +3. But once I do... + +__I have tried or I do...__ *(fill out each checkbox with a `X` if applicable)* +- [ ] In case of WebUI issue, I have tried clearing the browser cache and the issue persists. +- [ ] I do run mailcow on a Synology, QNAP or any other sort of NAS. + +**System information** + Further information (where applicable): - - Your OS (is Apparmor or SELinux active?) - - Your virtualization technology (KVM/QEMU, Xen, VMware, VirtualBox etc.) - - Your server/VM specifications (Memory, CPU Cores) - - Don't try to run mailcow on a Synology or QNAP NAS, do you? - - Docker and Docker Compose versions - - Output of `git diff origin/master`, any other changes to the code? + +| Question | Answer | +| --- | --- | +| My operating system | I_DO_REPLY_HERE | +| Is Apparmor, SELinux or similar active? | I_DO_REPLY_HERE | +| Virtualization technlogy (KVM, VMware, Xen, etc) | I_DO_REPLY_HERE | +| Server/VM specifications (Memory, CPU Cores) | I_DO_REPLY_HERE | +| Docker Version (`docker version`) | I_DO_REPLY_HERE | +| Docker-Compose Version (`docker-compose version`) | I_DO_REPLY_HERE | +| Reverse proxy (custom solution) | I_DO_REPLY_HERE | + +Further notes: + - Output of `git diff origin/master`, any other changes to the code? If so, please post them. - All third-party firewalls and custom iptables rules are unsupported. Please check the Docker docs about how to use Docker with your own ruleset. Nevertheless, iptabels output can help _us_ to help _you_: `iptables -L -vn`, `ip6tables -L -vn`, `iptables -L -vn -t nat` and `ip6tables -L -vn -t nat ` - - Reverse proxy? If you think this problem is related to your reverse proxy, please post your configuration. - - Browser (if it's a Web UI issue) - please clean your browser cache and try again, problem persists? - Check `docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @172.22.1.254` (set the IP accordingly, if you changed the internal mailcow network) and `docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @1.1.1.1` - output? Timeout? + + General logs: +- Please take a look at the [official documentation](https://mailcow.github.io/mailcow-dockerized-docs/debug-logs/).