FOUND A WEBSITE OR APP PROBLEM? REPORT IT HERE
Homebrew Printing is under active development. Features and layouts may change as we improve the site and app.
Help us understand what went wrong so we can reproduce it and fix the cause. This thread covers the Homebrew Printing website and Android app, including Community Models, the forum, Model Studio, Support Fin Studio, Slicer Studio, downloads, and local printer connections.
Sign in and reply below. Copy the questionnaire, fill in what you can, and leave “Not sure” for anything you do not know. You do not need technical experience or answers to every question to report a problem.
Please keep one issue per reply. Search this thread and the forum first; if the same problem is already reported, add your own device details and reproduction steps to that discussion. Describe what you observed rather than guessing at the cause.
COPY AND FILL IN THIS ISSUE REPORT
1. What were you using?
Website in a browser, or the Homebrew Printing Android app?
2. Which page, tool, or control had the problem?
Page/tool name and the button, menu, or setting involved. Include a public page link if useful; remove private information from the URL.
3. What device and software were you using?
Device model; Windows/macOS/Linux/Android/iOS version; browser name and version for the website; app version for the Android app. Were you on a phone, tablet, or computer? Portrait or landscape, if layout was affected?
4. Were you signed in or browsing as a guest?
Do not post your password or account email.
5. What were you trying to do?
Describe the result you wanted, such as loading a model, saving a profile, adding supports, slicing, downloading a file, or connecting to a printer.
6. What steps led to the problem?
Start from the page you opened and list the actions in order. Include the options you selected and the last button you pressed.
Step 1:
Step 2:
Step 3:
7. What did you expect to happen?
8. What actually happened?
For example: nothing happened, a blank preview, the wrong output, a menu behind a card, a lost setting, a failed download, or a page that kept loading.
9. What exact error or status message appeared?
Copy the wording if possible. If there was no message, say “No error shown.” Include any displayed job/reference ID if available, but no private download links or access tokens.
10. When did it happen, and how long did you wait?
Date, approximate time, and time zone. For slow or stuck actions, estimate the wait and say whether a progress indicator appeared or changed.
11. How often does it happen?
Every time, sometimes, or once? If you already tried again, how many attempts failed? Did this previously work, and did it start after an app update, browser update, or settings change?
12. What have you already tried, and what happened?
For example: reopening the page/app, refreshing, another browser/device, another file, or restoring one setting. Tell us which change helped, made no difference, or made it worse. You do not need to clear saved work or repeat a print/payment action to make a report.
13. Can you add a screenshot or a useful example?
Attach a screenshot with the affected area visible and any private information covered. A public model/forum link can help us find the example. Explain what the screenshot shows. If you cannot share the original model, include its file type, approximate size, and whether a simple public model has the same issue.
EXTRA DETAILS FOR MODEL, SUPPORT, AND SLICER ISSUES
Add whichever details apply:
• Tool/builder used and the dimensions or options you entered. For an incorrect generated part, describe the requested feature and what is missing or wrong.
• Original file type (STL/3MF/OBJ/etc.), approximate file size, dimensions, and number of objects. Was it uploaded, opened from a saved project, or sent from another studio?
• Selected printer, nozzle, filament/material, and process/profile names. Mention custom profiles and the specific settings changed from their defaults.
• Which stage failed: upload, model loading, editing, saving, generation, support creation, slicing, preview, export, download, or sending to the printer.
• Whether the preview was wrong, the exported file was wrong, or both. For slicing, say whether downloadable G-code was produced even if the preview failed.
• Any displayed mesh warnings, job ID, queue position, progress percentage, or failed step. For a layer-specific issue, include the layer number or height.
• If saved settings changed unexpectedly, say whether this happened after saving/reopening a project, exporting/importing 3MF, switching profiles, or slicing.
EXTRA DETAILS FOR LOCAL PRINTER CONNECTIONS
• Printer model and connection type: OctoPrint, Klipper/Moonraker, ESP32/ESP3D, or another supported connection.
• Whether the phone and printer were on the same local network, and whether you used HTTP or HTTPS. Include the port numbers and any reverse-proxy path; do not include the API key or a URL containing credentials.
• Which part worked or failed: connecting, opening the printer web page, camera viewing, uploading G-code, starting a print, progress, pause/resume, cancel, movement, or temperatures.
• What the app showed compared with the printer's own screen or web interface.
• For progress problems, say how the job was started: through the app, OctoPrint/Moonraker, another program, or the printer's SD card/screen. These details can explain why a controller sees a different job state.
• Whether an upload or print command was acknowledged. If you are unsure whether a print already started, check the printer before sending the command again.
KEEP PRIVATE INFORMATION PRIVATE
Forum reports are public. Do not post passwords, printer API keys, session cookies, authentication tokens, payment details, addresses, private project/download URLs, or files you do not have permission to share. Review screenshots and log excerpts before posting. We do not need your API key to understand a connection problem.
If you are comfortable using browser developer tools, a short redacted error message can help. Full console/network exports can contain secrets; do not post an unreviewed dump. Logs are optional, not a requirement for help.
For account/payment details, private files, or a suspected security/privacy vulnerability, use Email support in the website footer ([email protected]) instead of posting sensitive details here. Never send passwords or API keys there either.
WHAT MAKES A USEFUL REPORT
“Slicer is broken” leaves us guessing. “Android app, Slicer Studio: slicing finishes and G-code downloads, but the preview stays blank; this happened on two attempts with the same 3MF; here are the selected profiles, approximate file size, error text, and steps” tells us where to start.
If the problem stops happening, reply with what changed and whether the same steps now work. If we ask for more details, keep the follow-up in the same discussion so the original report and results stay together. We may need another example or a smaller reproducible file before we can identify the cause; a report is useful even when you cannot reproduce it every time.
Thank you for helping improve Homebrew Printing. Clear reports help us spend less time guessing and more time fixing the problem.
HOMEBREW / 3D PRINTING CONVERSATIONS
Report website or app problems here — issue report template
Practical 3D printing help, settings, projects, and advice from fellow makers.
Announcements · PINNED