Where to Get Help When a theme.park Theme Isn't Working

Updated

Start with the theme's documentation page, then report the problem on the theme.park GitHub repository, and use the Discord community if you need live support. The site lists these three channels directly: docs for per-theme information, GitHub for issues with a theme, and Discord for live help. Before posting anywhere, confirm which installation method you used (a linuxserver.io Docker mod, a Hotio custom script, or webserver subfiltering via Nginx, Apache, Caddy, or Traefik), since that determines what a helper will ask you first.

Check the theme docs first

The documentation page is the intended first stop for information on each theme. theme.park covers 48 themed applications, and some themes include CSS addons, so the exact setup steps and options differ by app. Look up your specific app there before assuming the theme itself is broken.

A quick triage order:

  1. Confirm the theme is listed for your app and note any addons it mentions.
  2. Re-check the installation path you chose against the docs for that app.
  3. Only then move to GitHub or Discord with a specific question.

Report the issue on GitHub

The site points to the GitHub repository for theme problems: "Having issues with a theme? Let us know on Github!" This is the right channel for a reproducible bug or a theme that misbehaves after following the docs.

To make the report useful, include:

  • The app and theme name.
  • Your installation method (Docker mod, Hotio script, or webserver subfilter).
  • Your webserver if you use subfiltering (Nginx, Apache, Caddy, or Traefik).
  • What you expected versus what rendered, plus any relevant config or logs.

Get live help on Discord

For back-and-forth troubleshooting, the site offers a Discord community for live support. This suits situations where the docs don't cover your setup, such as an unusual reverse-proxy configuration or a container that won't pick up the CSS. Bring the same details you would put in a GitHub issue so the conversation starts from facts rather than guesses.

Pick the right channel

Situation Best channel
You haven't read the per-app setup steps yet Theme docs
A theme is broken or behaves unexpectedly after following the docs GitHub repository
You need real-time back-and-forth on a non-standard setup Discord community
You want to contribute a new color scheme GitHub (the site invites pull requests for community themes)

Common reasons a theme "isn't working"

  • Wrong installation method for your container. The Docker mods are built for linuxserver.io containers, while the custom scripts target select Hotio containers. Mixing them up is a frequent source of failure.
  • Subfilter not applied correctly. If you inject the CSS through a webserver, the filter must match the app's actual response; a misconfigured rule in Nginx, Apache, Caddy, or Traefik will leave the app unstyled.
  • Self-hosted CSS not reachable. theme.park offers a Docker image for self-hosting the CSS files. If you use it, the app must be able to load the CSS from that source.

Checking these three points against the docs resolves many cases before you need to ask anyone. When they don't, GitHub and Discord are the documented routes to help.