How to Report a Bug — Template & Guidelines

[admin]

How to Report a Bug​

Quality bug reports are essential for improving Panelica. Please follow these guidelines to help us identify and fix issues quickly.

Bug Report Template​

Please include the following information in your report:

[b]Summary:[/b]
(One sentence describing the issue)

[b]Panelica Version:[/b]
(Check Panel Settings or run: panelica version)

[b]OS Version (Ubuntu/Debian):[/b]
(Run: cat /etc/os-release | grep PRETTY_NAME)

[b]Steps to Reproduce:[/b]
1. Go to ...
2. Click ...
3. Enter ...
4. Observe ...

[b]Expected Behavior:[/b]
(What should happen)

[b]Actual Behavior:[/b]
(What actually happens)

[b]Error Messages / Logs:[/b]
(From /opt/panelica/var/logs/backend/backend.log
 or browser console errors)

[b]Screenshots:[/b]
(Attach if applicable)

What Makes a Great Bug Report​

• Reproducible — Include exact steps anyone can follow
• Specific — One bug per thread, not multiple issues combined
• Detailed — Version numbers, OS details, and relevant log snippets
• Clean — Remove passwords, API keys, and sensitive data from logs before posting

Where to Report​

• Domain/DNS bugs → Mention in your report, but post here
• Email bugs → Post here with mail log excerpts
• Migration bugs → Post in the relevant Migration sub-forum
• Security vulnerabilities → Post here with [Security] in the title

Bug Status​

Our team will respond with a status:

• Confirmed — Bug verified
• In Progress — Fix being developed
• Fixed — Fix released (version noted)
• Cannot Reproduce — More information needed

Why Your Reports Matter​

Every quality bug report directly improves Panelica. You are not just reporting a problem — you are contributing to the stability and reliability of the platform for everyone. Detailed, reproducible reports are the most valuable contributions a community member can make.

Thank you for helping make Panelica better!