Frequently Asked Questions
Answers to common Homarr questions about installation, customization, connectivity, support, and commercial use.
Can Homarr run on a Raspberry Pi?
Yes, when the device uses a supported linux/arm64 operating system. linux/arm/v7 is not supported. See
Prerequisites.
Can I use custom app icons?
Yes. Use a direct image URL, one of Homarr's icon sources, or upload an image. See Icons.
Can I create widgets?
Yes. Custom Widgets use server-side API requests and safe JSX. They can be written in the workbench or created with an MCP-connected agent.
Can Homarr be exposed to the internet?
Homarr supports authenticated and public deployments. Terminate HTTPS at a reverse proxy, keep Homarr updated, and grant public board access only when anonymous viewing is intended. See Board access control and Single sign-on.
Where are the logs?
Use Management → Tools → Logs for retained and live application logs. Container startup failures and older events are
available through the deployment platform, for example docker container logs homarr.
Use the browser developer console only for client-side failures. Review logs before sharing them because URLs and other deployment details may be present.
Why can Homarr not reach a service behind Gluetun?
Gluetun's firewall blocks traffic that is not explicitly allowed. Configure its
FIREWALL_OUTBOUND_SUBNETS for the relevant
LAN or Docker subnet, and use an address reachable from the Homarr container.
Where do I report a bug or request a feature?
Use the GitHub issue templates. For community support, see Get in touch.
Can Homarr be used commercially?
Yes. Homarr is licensed under the Apache License 2.0. Commercial users can support development through OpenCollective.