paxton
/
mailcow
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update Bug_report.md 

Some changes.
Removed the smiley, because I'm not a happy man.
master
André Peters 2019-02-07 00:58:40 +01:00 committed by GitHub
parent 69bb77aeaf
commit d3732bde23
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 20 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

48
.github/ISSUE_TEMPLATE/Bug_report.md vendored
View File

@ -4,34 +4,26 @@ about: Report a bug for this project
--- ---
**Notice (you can delete this paragraph)** **README and remove me**
Please understand that we use GitHub as **bug tracker and for feature requests only**. For community support and other discussion, you are welcome to visit and stay with us @ Freenode, #mailcow
For general (community) support and other discussion, you are welcome to visit us @ Freenode, #mailcow Answering can take a few seconds up to many hours, please be patient.
Answering may take from a few seconds to 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/
Immediate commercial support is available via info@servercow.de
**Describe the bug** **Describe the bug, try to make it reproducible**
A clear and concise description of what the bug is. 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.
**How to reproduce Reproduce** **System information and quick debugging**
Steps to reproduce the behavior please explain how to reproduce the bug: General logs:
1. .... - Please take a look at the [documentation](https://mailcow.github.io/mailcow-dockerized-docs/debug-logs/).
2. ....
3. ....
**Expected behavior** Further information (where applicable):
A clear and concise description of what you expected to happen. - Your OS (is Apparmor or SELinux active?)
- Your virtualization technology (KVM/QEMU, Xen, VMware, VirtualBox etc.)
**Screenshots** - Don't try to run mailcow on a Synology or QNAP NAS, do you?
If applicable, add screenshots to help explain your problem. - Docker and Docker Compose versions
- Output of `git diff origin/master`, any other changes to the code?
**Logs** - 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 `
Please take a look at the [documentation](https://mailcow.github.io/mailcow-dockerized-docs/debug-logs/). - 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?
**System** - 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?
- OS: [e.g. iOS]
- Browser: [e.g. chrome, safari]
- Other clients involved:
**Additional context**
Add any other context about the problem here.