How to Get Support for Crafty Controller

Updated

Crafty Controller's primary support channel is its Discord community, where volunteers provide free help to anyone running the panel. The site also points users to documentation for setup guidance. Support is aimed at users with a bit of technical knowledge and a willingness to learn — the project explicitly asks that you "bring a desire to learn" rather than expecting hands-on managed service.

Where to Find Help

Channel What it offers Best for
Discord Free support from volunteers; community of 17,052+ members Setup questions, troubleshooting, general guidance
Docs Written setup and usage guidance Step-by-step installation and configuration reference
GitLab Full source code and visibility into ongoing development Users who want to inspect code or follow development work

What to Expect From Discord Support

The Discord is run by volunteers, not a paid support desk. That shapes how you should use it:

  • Come with context. Describe your OS (Linux, Windows, or Docker), how you installed Crafty, and what you've already tried. The site's install counts — 32,991+ Linux, 13,918+ Windows, and 36,453+ Docker installs — suggest volunteers field questions across all three deployment styles, so naming yours up front helps.
  • Expect community-paced replies. There's no stated response-time guarantee; help depends on who's available.
  • Bring a learning mindset. The project frames support around users who want to understand their setup, not just have it fixed for them.

Before You Ask: Self-Serve Basics

A few facts from the project can resolve common confusion before you post:

  • Access model: Crafty runs as a self-hosted web server. By default it's reachable by devices on your local network; external access requires port forwarding. If you can't reach the panel from outside your network, that's expected behavior, not a bug.
  • Data location: Everything is stored locally on your machine — there's no cloud instance to check.
  • Security defaults: Passwords are hashed with Argon2 and the webserver defaults to an SSL-secured certificate. If you see certificate warnings, that's tied to this default SSL setup.
  • Licensing: Crafty is released under GPLv3, so the full source is publicly inspectable on GitLab if you want to verify behavior yourself.

A Practical Support Workflow

  1. Check the docs first for installation and configuration steps matching your platform (Linux scripts, Windows executable, or Docker).
  2. Reproduce and note the issue — what you did, what you expected, what happened.
  3. Search the Discord before posting; with a community this size, your question may already be answered.
  4. Post with your environment details (OS, install method, Crafty version if visible) and the steps you've tried.
  5. Follow up in the same thread rather than starting new ones, so volunteers keep the context.

Common Sticking Points

  • "I can't access Crafty remotely." Local-network access is the default; external access needs port forwarding configured on your network.
  • "Is my data being shared?" No — Crafty is 100% self-hosted with data stored locally, per the project.
  • "I'm new to servers." The project states only "a bit of technical knowledge" is needed, and the Discord is explicitly there to help people learn.

If your need is code-level verification or you want to track fixes, the GitLab repository is the place to look; for hands-on help getting running, Discord is the intended route.