Report a Website Problem

What this feature is for

Use Report a problem when a website page or control is broken—for example, a Save button does nothing or a page displays an error.

The report becomes a public issue on GitHub, where the team tracks website problems. You do not need a GitHub account, and you can report as a guest.

For payment decisions, private account recovery, event rules, application results, or refunds, use the organizer’s private channel instead. See Get Help with Your Account or Event.

Before you start

Try the broken action once and note what happened. You do not need to repeat a payment or final booking submission to demonstrate a problem.

Have a short description ready. Check that your report will not reveal a receipt, private link, contact information, password, QR code, or private safety matter.

Send a report, step by step

Step 1: Open Report a problem

On Regosite, choose Report a problem. The reporting window opens above the page.

Check the displayed username and display/furry name. A signed-in report can include those names; an unsigned visitor can appear as Guest. Those displayed names can be published with the report.

Step 2: Write a clear short summary

In Short summary, describe the problem in one sentence.

For example: “The Save button on my profile does not respond.” Avoid putting your email, receipt reference, or private details in the title.

Step 3: Explain what went wrong

In What went wrong?, describe what you were trying to do, what you selected, and what happened.

Use Steps to reproduce for a simple sequence someone else can follow, such as opening a page, choosing an option, and pressing a button. In What did you expect?, explain the result you thought should appear. These extra fields are optional but can make a report much easier to investigate.

Step 4: Review the diagnostic details

The reporter collects recent technical information from that page—such as error messages and whether a request succeeded—to help the team find the cause. It does not automatically take a screenshot or inspect all your other tabs.

Read Diagnostic text to share under Review diagnostic details. Remove anything private or unrelated. Automatic hiding of private information can be imperfect, so your review matters.

Choose Use these diagnostics when the text is ready. Capture again gathers a fresh set; if you use it, review the new text before approving it. Editing the text also means you need to approve it again.

Step 5: Decide whether to share publicly

Read the consent beside the checkbox. It says your displayed profile names, report, and approved diagnostic text will be published in the public Furries PH issue tracker.

Select it only if you agree. If the information needs to stay private, close this window and use private support instead. You can still save your report for your own use.

Step 6: Finish the security check and send

Complete the security check when shown. Send report becomes available when the required details, diagnostic review, consent, and verification are ready.

Choose Send report once and wait for the result. Avoid closing the window while you are waiting for the submission outcome.

Step 7: Check the published issue

After success, choose View your issue on GitHub to view the report. Keep its link so you can refer to it later.

You are finished when: the reporter confirms success and gives you the issue link. A completed website report does not make a payment, application, or booking decision for you.

Save a report instead

Use Save report to download a copy of the details. Keep that file private until you have reviewed it. Saving a copy does not mean it was sent to the team.

If sending is not confirmed

Read the message before retrying. The previous attempt may still finish even when the browser did not receive confirmation.

Keep the same details and follow the reporter’s retry instructions rather than creating a new report with different text. Retry connection reconnects the reporter. If Restore last attempt is offered, it brings back the earlier details for you to review.

If you cannot finish the security check or the reporter will not reconnect, save the report and try again later. Use the appropriate private support path if the underlying issue concerns your booking or account.